Design your internal academy

Design our internal academy home page:

Design our internal academy home page in our brand. Work in drafts: nothing changes for employees until I say publish.

═══ ONE ROUND OF QUESTIONS ═══
Ask me in ONE message, then wait:
1. Who opens this page (new joiners on day one, everyone, a mix), and the ONE thing they should do first.
2. The feeling: calm and guided, or a full catalogue. If my answer is vague, offer two concrete directions and let me pick.
3. The languages the page must exist in; each language is its own version.

In that same first message, also ask me my role and the team I support.

═══ READ WHAT EXISTS, THEN THE BRAND ═══
Read what is really here first: the current page (get_academy_structure), which channels exist (list_channels), and what could honestly power a "start here" band. Propose only from what exists; name the gaps, do not fill them. Read our brand from the account (get_company_context) and show me exactly what you found. Ask for anything missing (if no logo comes back, ask me to paste one) rather than inventing it. Read the platform's page guide before you design (get_authoring_guide, topic page-kit) and follow it over memory.

═══ PROPOSE THE PAGE, THEN STOP ═══
Show me the layout: the hero, the bands in order, and which widget carries each, using the widgets this page actually has. Be plain about limits: if there is no widget for what I asked, say so and offer the nearest real one; never fake it with hand-built markup. Styling rules for anything custom:
- Scope every CSS rule to your own wrapper classes, and give every block you author its own class. Never style bare tags (p, span, h1-h6, div) and avoid broad descendant selectors; both reach inside Juno's own cards and widgets and break them.
- Restyle Juno's cards only through their documented CSS variables. Where a band changes background, redeclare the full card variable set so no card text or pill goes invisible on the new ground.
- Use the platform's own fonts. Never load or invent a typeface.
- The brand colour is ink, rules, and small accents, not full washes. Check text contrast on the surface it actually sits on; small or muted text gets MORE contrast, not less.
- Real assets only: never fabricate screenshots or product imagery.
Wait for my approval.

═══ DRAFT, PREVIEW, STOP BEFORE THE SWITCH ═══
Apply the approved design as a draft (update_academy_layout), show me the preview (preview_academy_page), and report which parts of the design survived and which the platform dropped. Say plainly that the preview strips the platform's fonts and live widgets, so structure is judged in the preview and look on the page. Then say plainly that publishing (set_live_academy_version) is what flips every employee to this page; drafts and previews change nothing. Publish only on my explicit yes. If we run in more than one language, offer to translate the approved page (translate_academy_page) into the others as their own drafts.

Rules throughout: drafts until my yes; read-only until I approve, no write-shaped calls, not even ones you expect to be rejected; propose only from real content and a brand you actually read; name limits instead of designing around them silently; design around what a tool result surfaces instead of sending me to dig up ids; work with whatever this account has, a full brand or one colour, many channels or none, and never stall on a missing thing; talk to me in product terms, never tool names or call order; scoped styles only, never bare tags; preview before publish.