logo
0
0
WeChat Login
LeenHawk<leenhawk@leenhawk.com>
Add organizers and tutorial setup documentation; implement global styles

FPT Workshop Template

This project is an Astro + Tailwind CSS scaffold for FPT workshop pages. All on-page content is stored in Markdown or TOML so non-web teammates can edit text, tables, and links without touching HTML.

Quick Start

npm install npm run dev

The site runs at http://localhost:4321 during development. Changes to Markdown/TOML files reload automatically.

Content Files

All editable content lives under src/content/:

FilePurpose
src/content/hero/workshop.mdTitle, tagline, hosting info, event link, badge label (edit the front matter at the top)
src/content/presenters/roster.mdSection title + presenter list written as Markdown bullets
src/content/sections/abstract.mdAbstract text (Markdown body)
src/content/schedule/program.mdAgenda table written with Markdown syntax
src/content/reading/list.mdReading lists grouped by headings and bullet links
src/content/setup/checklist.mdSetup checklist with nested bullet lists

Add new pages/variants by copying these files and adjusting the file names. The slug (file name without extension) is how index.astro finds each entry.

Editing Notes

  • Hero (hero/workshop.md)
    • Edit the YAML block between the --- lines at the top for title, schedule, and links.
  • Presenters (presenters/roster.md)
    • Add or remove bullet items. Use **Name** — Affiliation to keep the styling consistent.
  • Abstract (sections/abstract.md)
    • Use regular Markdown (##, *italic*, etc.). Keep the --- front matter at the top for the section title.
  • Schedule (schedule/program.md)
    • Edit the Markdown table rows directly. <br> creates line breaks inside a cell.
  • Reading List (reading/list.md)
    • Use headings (###) to make subsections, and bullets for each reference link.
  • Setup (setup/checklist.md)
    • Nest bullets for notes and links under each bold headline.

Deploying

  1. Run npm run build to generate production files in dist/.
  2. Deploy the dist/ folder with your preferred static host (GitHub Pages, Netlify, Vercel, etc.).

Troubleshooting

  • If the build fails with “Missing workshop content”, ensure all files listed above exist and keep the required frontmatter keys.
  • Invalid TOML (missing quotes, stray commas) will stop the build. Editors such as VS Code highlight TOML syntax errors automatically.