How cpps-unesp/site-cpps works
Project type and purpose
• This is a JAMstack‐style, static website for an academic research center.
• Built with Astro (SSG), TypeScript, Tailwind CSS + DaisyUI, MDX for content, Pagefind for client-side search, and GitHub Actions for CI/CD.
File structure
• Top-level “src/” holds the UI code and content:
• components/ (Astro UI components)
• content/ (MDX files for docs, team members, news)
• i18n/ (locales JSON + route translations)
• layouts/ (page templates)
• pages/ (Astro page entry points by language)
• public/ holds static assets (images, scripts).
• Config files: astro.config.mjs, tailwind.config.js, tsconfig.json.
• CI/CD: .github/workflows/deploy.yml.
Extract architecture notes from README
• Content pipeline: MDX → Astro → static HTML/CSS/JS.
• Internationalization (3 locales) integrated at routing and content level.
• Client search via Pagefind (build-time indexing + client library).
• Theming handled by DaisyUI + custom themeSwitcher.js.
• Deployment yields a “dist/” folder of pure static assets.