> For the complete documentation index, see [llms.txt](https://www.feinfra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.feinfra.com/technical-functional-requirements/other-unsorted.md).

# Other / Unsorted

* Devices: Mobile? Web? Desktop? iPad?

## Browser Requirements

* Do we anciptiable any older browsers, slower devices, slow network connections
* SSR for slower devices, fast first render
* WebSockets - if not supported fallback

## SEO

* FB Meta tags, Google Indexable/Robots
* Favicon

## i18z/accessibility

* Do we need i18z or accessibility
* Easily account for accessibility using MUI But might need to change later when changing design
*
* Level of abstraction on top of component so that it's easy to switch between
*

## Static Page like Home

* Webflow - so that designers can update without a developer, less deploy time

## Bug tolerance:&#x20;

which areas should bugs have more QA

* Heavily test financial customer
  * Number/Support
  * Talk about the experience after customer bought something

## Hosting

* Vercel for hosting in the beginning

## Components Architecture Examples

* Advanced Masonry Scroll (google photos)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.feinfra.com/technical-functional-requirements/other-unsorted.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
