#379 Landing page and per-audience pages, behind LANDING_PAGE
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#379
- issue
- state:closed
A server can show a **landing page** at `/` and a page **for each audience**, instead of opening on the timeline browser — so an operator (timescale.info) can point educators, researchers and others at a page written for them. **Switch.** `LANDING_PAGE=1` (off by default, so other servers don't change). On: `/` is the landing page and the timeline browser moves to `/explore` (`/explore` also works when off, and its existing addresses, searches and pages keep working). Off: `/` stays the timeline browser. **Audience pages.** `/for/educators`, `/for/researchers`, `/for/investigators`, `/for/operations` (logs and incidents), `/for/writers` (stories and canons), `/for/developers` (API and self-hosting). Each: a one-line promise in that audience's words; two or three example timelines; the matching explainer video, if configured; what you can do, as a few concrete tasks; and what that audience needs to trust (educators: free, no account needed to read, accounts 13+, self-hostable; investigators: sources, date precision, history and audit). **Landing page.** A hero ("Any span of time, on one exact line"), audience cards linking to those pages, a few featured public timelines, and Explore / Sign up. **Content without code.** The copy comes from Markdown in the repository (overridable by the operator), and each page's example timelines and video from settings, e.g. `LANDING_EXAMPLES_EDUCATORS=athan/halloween,athan/usmc`, `LANDING_VIDEO_EDUCATORS= `. Missing or private examples are skipped. **Search.** The pages are in the sitemap when the landing page is on, with titles, descriptions, canonical links and structured data; they work without JavaScript, in light and dark, and at phone width. Tests for the switch (both settings), each page, the sitemap, and that `/explore` keeps the browser's behaviour. https://github.com/openchronology/timeline-app/issues/379
Related
- #380 Landing page and per-audience pages, behind LANDING_PAGE (#379)
- #381 The privacy policy covers YouTube videos played on the landing pages
- #382 Light and dark themes across the whole site and the editor
- #383 Light and dark themes across the site, the editor and the timeline
- #536 Fix "Invalid sign-in return location" for Google and GitHub sign-in
- Merge pull request #380 from openchronology/feature/379-landing-pages
- A landing page and pages for each audience, behind LANDING_PAGE (#379)
- The privacy policy covers YouTube videos played on the landing pages
- Light and dark themes across the site, the editor and the timeline stage
Open #379 Landing page and per-audience pages, behind LANDING_PAGE in the timeline