> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/app-builder-amas/2025-app-builder-amas/jan-8-2025-portals-features-design-updates-and-future-plans.md). # Jan 8, 2025: Portals, Features, Design Updates, and Future Plans ### **Join live!** Join us live biweekly on Wednesdays at 1:30 pm EST! Download the calendar invite below. {% file src="/files/wWxd5Fby40Ps3x20LdsB" %} {% embed url="" %} ## App Builder AMA video recording ### Contents of the recording: πŸ•’ Intro and Agenda - Kicking off the session with an overview of the agenda. πŸ“‹ Forms Portal - Showcasing a table of accessible forms with search and filter options. πŸ§‘β€πŸ’» End User Portal - Highlighting tools for onboarding, ticket management, and more for end users. πŸ“Š Operational Analytics Portal - Demonstrating operational insights with ticket and inventory reporting. πŸš€ Upcoming Features - Introducing imports, exports, cloning, and syncing for improved app building. 🎨 UI/UX Updates - Exploring updates to navigation, workflows, and app builder visuals. βš™οΈ Infrastructure Updates - Enhancements for faster provisioning and greater app stability. πŸ—ΊοΈ Roadmap Highlights - Discussing upcoming priorities, like app crates and synced custom components. ✍️ Design Demo - A deep dive into proposed UI changes and feature enhancements. ❓ Q\&A Session - Addressing questions on workflows, themes, and customizations. πŸ–ΌοΈ HTML Container Question - Exploring customizations with HTML containers in the app builder. πŸ”„ Workflow Triggering Question - Solutions for triggering workflows dynamically from grids. 🎭 Future Aspirations - Previewing plans for themes and advanced styling options. πŸ“¬ Wrap-Up - Closing the session with a call for feedback and survey participation.
HOW TO GET HELP: * πŸ’¬ Chat (Discord): [https://discord.gg/rewst​​](https://discord.gg/rewst%E2%80%8B%E2%80%8B) * Private #{{ msp }} channel * \#the-kewp * 🎫 Submit Tickets to: * πŸ“ Feature Request + Integration Requests: **CLUCK UNIVERSITY – REWST TRAINING:** * πŸ‘¨β€πŸ« Live Instructor-Led Training: * 🏁 Rewst Foundations Training: * ▢️ On-demand Videos: **DOCS:** * πŸ₯š Rewst Docs: * ⛩️ Jinja Docs: * ⛏️ App Builder Docs: **KEY LINKS:** * πŸ“ Feature Request + Integration Requests:
--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rewst.help/updates/app-builder-amas/2025-app-builder-amas/jan-8-2025-portals-features-design-updates-and-future-plans.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 `build a script that syncs our docs to a CMS` 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.