Pages
Page basics
A page is a view, or screen, in your business app. It gives a person a place to see information and do a task, such as reviewing products, entering a new order, or checking a customer’s account. You create pages in Settings → Pages and give each one a name and a URL path.
Choose a URL path
A URL is the link or address that opens a page. The page name should make the purpose clear, and its URL path should usually use the same words: for example, a page named Products can use /products. Every path must start with a slash, and each page path must be unique within the organization.
Use a fixed path when one page always shows the same kind of screen, such as /products or /sales/orders. Use a colon parameter when the same page should open a particular record. For example, /products/:id is a product detail page pattern; the :id part is filled with the selected product’s ID when a person opens that product. A nested path such as /sales/orders/:order_id/items describes order items within a specific order.
Pages and entities
Pages work with the entities you define. An entity is like a structured database table, with fields as columns and records as rows. A form on a page collects values for those fields and saves them as a new or updated record. Create the entity first so the form knows what information to collect. You can then ask for a page that shows the entity’s records in a table, uses cards for key totals, adds charts for trends, or provides forms to create and edit records.
Draft pages with AI
Tauriam’s AI creates the page implementation behind the scenes in TSX (TypeScript with the page’s visual structure). You describe the screen and the work it should support in ordinary language; you do not need to write that code yourself. Be specific about the entity, which fields to show, what people need to do, and how the screen should respond. For example, ask for a products table with search, a form to add a product, and a card showing total stock. Clearer instructions give the AI better direction and usually produce a page closer to what you need.
- Use clear page names and paths that match, such as Products and
/products. - Start every URL path with
/and make each path unique. - Use colon parameters for pages that show a particular record, and give parameters meaningful names such as
:order_id. - Build the entity and fields before asking the AI for forms or tables that use them.
- After creating a page, add its URL to Navigations so people can find it in the sidebar.