Dash is designed to be adapted in Stacks App. Remove sections a client should not use and keep the remaining navigation aligned with the site’s Total CMS 3 collections.
Set collection IDs first
Connect every supplied editor, list, gallery, depot, and single-object view to the intended collection. Test View before Add so existing records reveal whether the ID is correct.
Do not assume similarly named collections are interchangeable. Blog, Services, Gallery, Depot, Legal Notice, Privacy Policy, and Profile can use different data structures.
Edit the navigation
Dash allows you to duplicate pages, rename folders, add or remove menu items, and integrate your own views. When a section is removed, remove both its menu entry and any home-dashboard Add or View link that leads to it.
White-label the dashboard
Replace the supplied logo, dashboard name, wording, user-area presentation, and destination of the Website button. Keep the sign-in, profile, password-reset, and sign-out paths functional after branding changes.
Adapt layouts without breaking editors
Adjust the surrounding Foundation 6 layout while preserving Total CMS fields, forms, IDs, and editor actions. Duplicate a working editor before modifying it for a new collection.
Client-focused checklist
Show only sections the client needs.
Use the same content names as the public website.
Keep Add and View actions easy to distinguish.
Test dark mode and all responsive ranges.
Check the mobile sidebar inside every editor.
Related: Getting started with Dash 2 and Troubleshooting publishing and updating Dash.