1 Repository Context: publications

1.1 Purpose

  • Quarto-powered hub for neuromorphic computing, AI, and machine-learning publications.
  • Houses research-grade papers (HTML + PDF) and supporting blog posts (including notebook-style explorations).
  • GitHub Pages serves the rendered website via the Quarto CLI and GitHub Actions.

1.2 Key Locations

  • _quarto.yml — Project/website configuration (navbar, theme, metadata cascade).
  • index.qmd — Home page showing the latest entries from blog/.
  • about.qmd — Project mission statement.
  • papers/ — Research manuscripts; shared format defaults in _metadata.yml.
  • blog/ — Posts and notebooks; filenames follow YYYY-MM-DD-title.qmd or .ipynb.
  • .github/workflows/publish.yml — GitHub Pages deployment pipeline (renders site and PDFs).

1.3 Content Workflow

  1. Author new material in the appropriate folder (papers/ or blog/).
  2. Ensure front matter includes at least title and date; add categories for listings.
  3. Run quarto render locally to check output; PDFs generated via TinyTeX when needed.
  4. Commit changes and push to main; the GitHub Actions workflow redeploys _site/.

1.4 Deployment Notes

  • _quarto.yml should reference the correct canonical URLs for the GitHub Pages site.
  • GitHub Pages should be configured to use the “GitHub Actions” source.
  • Workflow installs Quarto and TinyTeX on CI; keep the repository lean to avoid long installs.

1.5 Prerequisites for Local Work

  • Quarto CLI installed (https://quarto.org/docs/get-started/).
  • LaTeX engine (TinyTeX recommended: quarto install tool tinytex) for PDF builds.
  • Optional: Jupyter kernels for executing notebooks; disable execution (execute.enabled: false) when stubs are checked in.

1.6 Miscellaneous

  • Site metadata targets neuromorphic computing; adjust titles/tags as scope expands.
  • Avoid committing large datasets or artifacts; host externally if needed.
  • Listings rely on file hierarchy; blog automatically surfaces any files stored beneath it.