← ClaudeAtlas

ticket-cube-language-schoollisted

Build an experimental, multilingual landing site for language schools, courses and community learning programmes in a "ticket" visual system — a notched ticket-bar navigation with numbered links, a mouse-reactive 3D cube in the hero whose faces are the learning paths, word tickets ("Hello" / "Hallo · means Hello"), boarding-pass cards that expand like an accordion (EN ✈ DE route, level / when / cost), a timetable grid, a chat-style course finder that is explicitly not a placement test, a conditional application form, split-flap FAQ numbers, hard offset shadows, a GDPR-style cookie popup, an install-as-app dialog (PWA) and up to eight UI languages including right-to-left Arabic and Persian. Use for language schools, integration and newcomer courses, NGOs and adult-education providers, language cafés, tutoring and any multi-path course offer that must work for people who don't read the site's main language yet. Produces one HTML file plus a small assets folder; no frameworks.
smyrna-pergamum/web-design-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill smyrna-pergamum/web-design-skills
# Ticket cube language school A homepage for people who are *starting* with a language. Everything is a ticket: the nav, the words, the course cards, the questions. The reference build is `example/index.html` (**Atlasio**, a fictional language school, eight UI languages). Detailed code is in `references/components.md`; `screenshots/` shows every section on desktop and mobile. The promise to the visitor: *you can understand this page before you understand the language.* So language choice is always one tap away, every path shows level, time, place and cost in plain words, and the application is short. ## 1. Before designing 1. **List the learning paths (3–5).** For each: target language, format (in person / online), level range, days and times, place, cost and how admission works. These become cube faces and pass cards; nothing may be invented. 2. **Pick the UI languages** from the real audience, not from a wish list. The reference uses DE, EN, TR, AR, FA, UK, RU, FR. Plan right-to-left (AR, FA, HE, UR) from the start; get every translation checked by a native speaker. 3. **Collect the weekly timetable** for in-person offers (day, start, end, group). Course hours that are not fixed per group go into one "daily" band above the grid instead of fake slots. 4. **Write the finder questions** (3–4, each with 2–3 answers) and the rule that maps answers to a path. Say clearly that it is not a placement test. 5. **Decide what the form needs per path** (level for courses