file-based-routing-for-static-sites

Markdown to HTML conversion processes `.md` files into fully rendered HTML pages during the static site build. The tool uses markdown-it to parse content and highlight.js for code syntax highlighting, outputting standard HTML files.

Layout inheritance allows you to define a `layout.html` file to maintain consistent page structure across your static site. The build process applies this wrapper template to individual Markdown-generated HTML pages automatically.

The development environment supports live reloading via the `@web/dev-server` dependency and `chokidar` file watcher. Running `npm run dev` starts a local server that automatically refreshes pages when Markdown or TypeScript files change.

File-based routing for static sites automatically maps your directory structure to URLs, converting Markdown files to HTML pages. You organize content in folders, and the build tool processes the input directory to generate a navigable static output build.

Static asset handling copies static files like CSS and images directly to the output build directory. This ensures your static site generator properly bundles stylesheets and media alongside the compiled HTML pages.

File-based routing requires strict directory naming for URL generation and relies on TypeScript compilation. Complex dynamic routing or server-side rendering is not supported, as it focuses solely on generating static output builds from Markdown and HTML files.