> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/design/user-interface.md). # User Interface Overview of the Design app features for building admin apps, screens, menus, options, translations, icons, and styles in Rierino. With Rierino, it is possible to design different admin UI apps for different business domains and use cases, by defining following main elements: * **App:** Each app defines a set of user screens and navigation menus, typically mapping to user profiles and roles * **UI:** Each UI represents a data entry user screen, where generic widgets and listers allow manipulation of data of any kind * **Option:** Each option represents the list and properties of options listed in drop-down widgets * **Translation:** Contains translations for all common and business domain specific labels * **Icon:** Contains all SVG icon definitions used across the platform * **Style:** Allows configuration of custom CSS for styling and changing color theme {% embed url="" %} In addition to these elements, design application also includes "component" screen for defining list of editors and filters available within the platform, which is typically not modified unless new custom editors are developed. While it is possible to extend the scope of apps and user screens with new component and page development for highly specialized business requirements, Rierino is shipped with elements which address most business needs. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rierino.com/design/user-interface.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.