Roadmap

Site Tree / Roadmap

This page is the map for where The Muzes Garden is now and where it is going. It tracks done, doing, and still-to-do work so the app can grow without losing the plot.

DONE

Home page exists and no longer redirects to Projects
TitleBar Home and Project routes are fixed
Find It opens clean with Clear / Reset
Find It highlights results and shows selected/top result clarity
Find It can show Navigation and Metadata source chips
Metadata seed records exist
Manual system has reusable layout components
Core manual pages are being upgraded into a unified format

DOING

Build the in-app manual / encyclopedia
Connect metadata records deeper into Find It
Separate app-section links from More Info explanation pages
Keep files split before they grow too large
Turn flat explanation pages into connected manual pages

STILL TO DO

Create deeper child manual pages for important words and features
Add relationship-aware metadata search
Improve project pages and connect projects to metadata
Build the future AI music generator architecture
Create a full navigation tree view that users can browse visually
Add manual search results into Find It
Add project-aware playback context

Current big-picture structure

The app is becoming a connected creative operating system. The current structure starts with Home, then branches into working tools and manual explanations.

Step 1

Home

Step 2

Manual

Step 3

Projects

Step 4

Metadata

Step 5

Find It

Step 6

Global Player

Step 7

AI Music Generator

Step 8

Site Tree

Future tree idea

The final version should let users click through a tree like:

Home → Metadata → Library → Record → Relationships → More Info → Related Concept → Project → Player

That same tree should help Find It explain exactly how to get from the current page to the target page.

Why this roadmap matters

The Muzes Garden is already deep enough that a roadmap is not optional. Without a clear tree, the app would turn into scattered features.

The roadmap keeps the build honest. It shows what already works, what is actively being shaped, and what should not be pretended to be done yet.

This page should eventually become both a developer map and a user map. Users should be able to see where features live, while development can use the same tree to avoid duplicating systems.