Yuri and Miguel meeting: organizing the universe’s architecture – folders and languages – and combining how Miguel’s three projects fit into the larger universe. Today is about form and organization (functionality we’ll address later), thinking about when co will take over. Everything approved. ✅
Objectives
- Understand the current organization (folders + languages)
- Separate what is content from what is scaffolding
- Combine how the three projects fit into Miguel’s universe
- Define how the universe presents itself when co is downloaded
1. The central idea: content × form
The same idea as method organizes everything:
- Content = what is written (the texts). It’s what matters – and that’s all co will use.
- Form = translation, visuals, widgets, publication. It’s scaffolding: build the site today, but co takes over later.
Combined: keep the content clean and separate from scaffolding so the transition to co is easy. ✅
2. The three projects within Miguel’s universe (MG)
Miguel is the umbrella universe (the person, the hub). Each project is a mission = a group of people with a clear and measurable goal:
the three missions
- MSE (
MGMSE) – MS&E graduation; it’s the base for the others.- App Agro (
MGAGRO) – WhatsApp bot for agricultural management.- Alpha Scholars (
MGALPHA) – study universe (22 hours a week).
How they fit in:
Miguel (MG) — hub pessoal
├── MSE (MGMSE) — já é universo próprio
├── App Agro (MGAGRO) — seção hoje → vira universo
└── Alpha Scholars (MGALPHA) — seção hoje → vira universo
- Each project is a child sub-universe of Miguel. The MSE is already a separate universe; App Agro and Alpha Scholars live as sections within Miguel today and become their own universe when they grow (same promotion we did before).
- The MG code ties the whole tree:
MG-in the hub,MGMSE·MGAGRO·MGALPHAin each mission – one identity. - When co loads Miguel, the projects appear beside him as children; the public can subscribe.
Combined: hub + missions; each mission promotes to universe when it matures. ✅
3. Folders – organizing them
how it will look
- At the top: what matters (content + universe card + translation memory)
- Together: the scaffolding, marked as disposable
- Apart: references (drafts, comparisons)
Clean content → the transition to co is just “point to the content”. ✅
4. Languages (PT / EN)
- The PT is the original; the EN is an automatically translated copy, page by page.
- Translation has memory saved – it doesn’t retranslate unnecessarily, and co can use it later without cost.
- Switching languages is form (a button), not in the menu.
- Chosen translation model: Sonnet (see comparison). ✅
5. Board and widgets
- The tasks live in the text tables (single source of truth). The kanban is just a view of them – co has its own board that reads the same tables.
- The calendar is a true widget; co needs space to fit such widgets.
Combined: table is the source; kanban is disposable. ✅
6. When co is downloaded (first time)
The universe should present itself alone: what’s the initial page, which languages, who’s the parent and who’s the child, what’s public.
- Then the user opens co and lands on Miguel’s hub with projects to the side for subscription – without any configuration.
- To decide: is Miguel a public showcase or a more private hub? The new user path points to private hub + public projects. ⬅️ the only open question
What was decided ✅
- Content separated from scaffolding
- 3 projects = child missions of the hub; promote to universe when they grow
- Translation memory saved; default model = Sonnet
- Markdown table = single source of the board
- Miguel public (showcase) × private (hub) – close today