How hannotify/javas-concurrency-journey-continues works
Project type and purpose
• This is a *static slide deck* for a Java conference talk, authored in Markdown and PlantUML, styled with CSS, and rendered into a single-page HTML presentation (index.html). There is no dynamic backend or database—everything is pre-built and served as static assets.
Main components
a. Content sources
• sections/\*.md – the talk’s individual slides and sections
• /outline.md – master outline of the deck
• demo/demo.md – demonstration notes
c. Styling assets
• css/\*.css – theme and presentation styles (darcula, devoxx, custom, etc.)
d. Static assets
e. Renderer & final output
f. (Implicit) Build tool
• Could be a script or Pandoc/Reveal.js invocation that:
1. Converts Markdown → HTML slides
2. Invokes PlantUML → out/puml
3. Bundles CSS & images
4. Produces index.html
Relationships and data-flow
• Authors edit .md and .puml source files
• Build pipeline step-1: run PlantUML on puml/*.puml → out/puml/*.png (or SVG)
• index.html loads CSS and image assets at runtime in the browser
• Browser renders the slide deck; no server-side logic
Architectural patterns & design principles
• *Static Site Generation*: clear separation between content, assets, and final output