static-site-builder 0.1.4 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4ec7765f3cc618a791a6d655fed75fe39f43a09d9c697cc71135d17160dbd27f
-  data.tar.gz: 74ace48bd713ba712607509baf63a80095cd610395be622b59c3e552336f10df
+  metadata.gz: b04601a6add58d7ee3a23a48d6456f16fd6fb09a486d1834604803b21cd2ca75
+  data.tar.gz: 717cfe27a34a388acea7a1f91a37b655040dc7ca1b97d4d6fe86c01c59d10f17
 SHA512:
-  metadata.gz: 358643b7c2cb4bd56693c18fa4f57114da85b519a1423e319a55d1b4d7ee0d3190768985225539e6c65f9eed044d96fced689d5464d39fb0db85238dbcb4e6d4
-  data.tar.gz: a8ab43edfdac947a34e0222c181037213120eb1f9dea91c924f218e974908c51491135ce475aadde6552bedd65698cf05a54e18af60b73669b6c6fe7134cb84a
+  metadata.gz: 28c976044449130ad0da918875dfdfdbc32b09126f46f4ed2516b3d72fd0107ed8f63a6891c09414f37d13acee61f1c573ed1e40ad6c81f87a49628013037fdf
+  data.tar.gz: 6ae711f3f6fb8de54c2b2ec4f9b8c3bfbd2d4b6d8848ff078f95e3c0174523e0e9542779d1b331b0541c6c8fdcca6241bfd35b16d1d31cbfae29568d262592a4

data/CHANGELOG.md

@@ -1,96 +1,29 @@
 # Changelog
 
-All notable changes to this project will be documented in this file.
+## 1.0.0 (Current) - 2025-12-13
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+First stable release of Static Site Builder.
 
-## [0.1.4] - 2025-11-22
+### Features
 
-### Added
-- Generator now automatically creates `lib/page_helpers.rb` with `PageHelpers::PAGES` structure for page metadata
-- Generator now automatically creates `config/sitemap.rb` for sitemap generation
-- `sitemap_generator` gem is now automatically included in generated Gemfiles
-- `build:sitemap` task is automatically added to generated Rakefiles
-- Sitemap generation is integrated into `build:all` task
+- Generate static HTML sites from ERB templates
+- Development server with auto-rebuild and live reload
+- Sitemap generation from pages
+- Simple and flexible - add your own JavaScript bundling and CSS processing
 
-### Changed
-- Page metadata is now managed via `PageHelpers::PAGES` hash instead of frontmatter
-- README updated to reflect `PageHelpers::PAGES` approach (frontmatter example removed)
-- ActionView requirement changed from `>= 8.0` to `~> 7.1` for Ruby 3.1 compatibility
-- Generated layouts now use `@title` and `@js_modules` instance variables instead of frontmatter
+### What Gets Generated
 
-### Fixed
-- Fixed `js_modules` variable reference in generated layouts (now uses `@js_modules`)
-- Fixed PageHelpers metadata loading to occur before page content rendering, allowing partials to access `@title`, `@description`, etc.
-- Removed all frontmatter parsing code and references
-- Updated all specs to use `PageHelpers::PAGES` instead of frontmatter
+- Clean project structure with `app/views/`, `app/javascript/`, `app/assets/stylesheets/`
+- Self-contained build code in `lib/site_builder.rb` (no runtime dependency on this gem), using ActionView for Rails-like templates/partials/helpers
+- Rakefile with build tasks (`bundle exec rake build:all`, `bundle exec rake build:html`, `bundle exec rake build:css`, `bundle exec rake build:sitemap`)
+- `build:all` cleans `dist/` first, then builds assets + HTML + CSS + sitemap
+- Development server (`bundle exec rake dev:server`) with live reload
+- Example pages and layouts
+- Sitemap configuration
 
-## [0.1.3] - 2025-11-22
+### Requirements
 
-### Added
-- Integrated ActionView 8+ for proper Rails-style partial rendering
-- Support for Rails-style render syntax: `render 'shared/header'` and `render partial: 'shared/header'`
-- Support for passing locals to partials: `render partial: 'shared/header', locals: { title: 'Hello' }`
-- Nested partial support (partials can render other partials)
-- Multiple partials on the same page now work correctly
+- Ruby 3.0+
+- Bundler
 
-### Changed
-- Replaced raw ERB implementation with ActionView::Base for template rendering
-- Render method now uses ActionView's rendering system, matching Rails behaviour exactly
-- Partials automatically receive page variables (@js_modules, importmap_json, current_page)
-- Improved error messages for missing partials (converted from ActionView format for backwards compatibility)
-- Template annotations now preserve both page and layout annotations correctly
-
-### Fixed
-- Fixed issue where nested partials (partials rendering other partials) would fail or produce incorrect output
-- Fixed issue where multiple partials on the same page would only render the last one
-- Fixed template annotations being stripped when layout annotations were added
-
-## [0.1.2] - 2025-11-22
-
-### Fixed
-- CSS directory is now always created when Tailwind handles CSS compilation, preventing 404 errors for stylesheets
-- Build process now updates files in place instead of cleaning and recreating the dist directory, preventing 404 errors during rebuilds in development mode
-- Fixed race condition where pages would return 404 when code changes triggered rebuilds
-
-## [0.1.1] - 2025-11-21
-
-### Added
-- `render` helper method for ERB templates to include partials
-- Support for rendering partials from `app/views/shared/` directory
-- Partial files should be named with `_` prefix (e.g., `_header.html.erb`)
-- Partials have access to page variables (@js_modules, etc.)
-
-### Changed
-- Improved ERB compilation to support partial rendering
-
-## [0.0.1] - 2025-11-21
-
-### Added
-- Initial release of static-site-builder gem
-- Generator for creating new static site projects
-- Builder for compiling ERB templates to static HTML
-- Support for multiple template engines (ERB, Phlex)
-- Support for multiple JavaScript bundlers (Importmap, ESBuild, Webpack, Vite, None)
-- Support for multiple CSS frameworks (TailwindCSS, shadcn/ui, Plain CSS)
-- Support for multiple JavaScript frameworks (Stimulus, React, Vue, Alpine.js, Vanilla)
-- Page metadata via `PageHelpers::PAGES` hash
-- Layout support with nested layouts
-- Importmap JSON generation
-- Asset copying (JavaScript, CSS, vendor files, static files)
-- Comprehensive test suite
-- YARD documentation
-- CI/CD setup (GitHub Actions)
-
-### Changed
-- Vendor JavaScript files are automatically copied directly from `node_modules` to `dist/assets/javascripts/` during build
-- Removed requirement for `vendor/javascript/` folder - vendor files are copied automatically based on importmap configuration
-- Generator no longer creates vendor files during project generation
-
-### Fixed
-- Added warning messages when vendor files cannot be found in `node_modules`
-- Updated base64 dependency comments to clarify requirement for Ruby 3.4+
-
-[0.0.1]: https://github.com/Ancez/static-site-builder/releases/tag/v0.0.1
 

data/README.md

@@ -1,15 +1,28 @@
 # Static Site Builder
 
-A Ruby-based generator and builder for creating static HTML sites with working JavaScript. **No backend required** - just compile your templates to static HTML and deploy anywhere.
+> **⚠️ Active Development**: This project is currently in active development.
 
-## Main Objective
+A Ruby-based generator and builder for creating static HTML sites with working JavaScript. **No backend required** - just compile your ERB files to static HTML and deploy anywhere.
+
+📖 **Learn more**: [Demo](https://lukaszczapiewski.com) | [Project Overview](https://lukaszczapiewski.com/projects/static-site-builder) | [Getting Started Guide](https://lukaszczapiewski.com/blog/getting-started-with-static-site-builders)
+
+## Why This Exists
+
+Generates standalone static sites from ERB templates, with a working dev server, file watching, and live reload. Generated projects are **self-contained**: the build code lives in the generated repo (`lib/site_builder.rb`).
+
+## Why Choose This Over Other Approaches
+
+**Better SEO & Search Rankings**: Unlike Single Page Applications (SPAs) that rely on client-side JS rendering, static HTML is immediately crawlable by search engines. Your content is fully indexed from the first request, leading to better search rankings and significantly faster page loads.
 
-Generate static HTML pages with JavaScript files that work. Choose your own stack:
+**Simplicity Over Complexity**: No need for complex JavaScript frameworks, hydration, or server-side rendering setups. Create .html.erb files that compile to clean, static HTML. Add JavaScript only where you need interactivity, not as a requirement for rendering.
 
-- **Template Engine**: ERB or Phlex
-- **JavaScript Bundler**: Importmap, ESBuild, Webpack, Vite, or none
-- **CSS Framework**: TailwindCSS, shadcn/ui, or plain CSS
-- **JavaScript Framework**: Stimulus, React, Vue, Alpine.js, or vanilla JS
+**Developer Experience**: Work with familiar Rails patterns (layouts, pages, partials) without a full Rails application, allowing you to host it for free directly on Cloudflare CDNs and other static hosting services.
+
+**Version Control & Mobile Editing**: Your entire site is code in a Git repository. Track changes, collaborate, and edit from anywhere - even your phone with tools like Cursor Agents. No database migrations or CMS interfaces needed. Lightning fast.
+
+## Main Objective
+
+Generate static HTML pages using ERB files. Simple and flexible - add your own JavaScript bundling and CSS processing as needed.
 
 ## Installation
 
@@ -37,10 +50,9 @@ bundle install
 ruby bin/generate my-site
 ```
 
-You'll be prompted to choose your stack using an interactive menu with arrow key navigation. Generated sites use:
-- `static-site-builder` gem for compilation
-- Standard gems (importmap-rails, phlex-rails, etc.) for functionality
-- npm packages for JS bundlers and frameworks
+Generated sites use:
+- ERB templates for HTML generation
+- local build code in `lib/site_builder.rb` (no runtime dependency on this gem)
 
 ## What Gets Generated
 
@@ -48,231 +60,130 @@ A clean project structure that depends on gems:
 
 ```
 my-site/
-├── Gemfile              # Dependencies (static-site-builder, sitemap_generator, etc.)
-├── package.json         # JS dependencies (if needed)
-├── Rakefile            # Build tasks (includes sitemap generation)
+├── Gemfile              # Dependencies (rake, webrick, sitemap_generator, etc.)
+├── Rakefile            # Build tasks (assets, HTML, CSS, sitemap, dev server)
 ├── config/
-│   ├── importmap.rb    # Importmap config (if using importmap)
 │   └── sitemap.rb      # Sitemap generation config
 ├── app/
 │   ├── views/
 │   │   ├── layouts/
 │   │   ├── pages/
-│   │   └── components/     # Reusable components/partials
 │   ├── javascript/
 │   └── assets/
+│       └── stylesheets/
 └── lib/
-    ├── site_builder.rb   # Compiles your site
-    └── page_helpers.rb   # Page metadata (title, description, etc.)
+    └── site_builder.rb   # Compiles your site
 ```
 
 ## How It Works
 
-1. **Generator** (`static-site-generator`) - Creates the project structure
-2. **Builder Gem** (`static-site-builder`) - Handles ERB/Phlex compilation
-3. **Standard Gems** - importmap-rails, phlex-rails, etc. for functionality
-4. **Build Tools** - Rake tasks that use the builder gem
+1. **Generator** (`static-site-builder new ...`) - Creates the project structure
+2. **Generated build code** (`lib/site_builder.rb`) - Compiles pages/layouts and provides WebSocket live reload
+3. **Build tools** (`Rakefile`) - Defines `build:*` tasks and `dev:server`
+4. **Your tools** - Add Tailwind, bundlers, etc, and wire them via `package.json` scripts
 
 ## Features
 
 - 🎯 **Static HTML output** - No server-side rendering needed
-- 🔧 **Flexible stack** - Choose what works for you
-- 📦 **Gem-based** - Uses existing Ruby gems, not custom code
+- 🔧 **Simple & flexible** - ERB files, add your own tools
+- 📦 **Self-contained generated sites** - No runtime dependency on this gem
 - 🚀 **Fast builds** - Compile once, deploy everywhere
-- 🎨 **Component support** - ERB or Phlex components
-- 📱 **Modern JS** - ES modules, importmaps, or bundlers
-
-## Supported Stacks
-
-### Template Engines
-- **ERB** - Ruby's embedded Ruby templates
-- **Phlex** - Ruby component library (via phlex-rails gem)
+- 🔄 **Live reload** - Rebuild and refresh on changes in development
 
-### JavaScript Bundlers
-- **Importmap** - No bundling, use ES modules directly (via importmap-rails gem)
-- **ESBuild** - Fast JavaScript bundler
-- **Webpack** - Powerful bundler with plugins
-- **Vite** - Next-generation frontend tooling
-- **None** - Vanilla JavaScript, no bundling
-
-### CSS Frameworks
-- **TailwindCSS** - Utility-first CSS framework
-- **shadcn/ui** - Re-usable components built with Tailwind
-- **Plain CSS** - Write your own styles
-
-### JavaScript Frameworks
-- **Stimulus** - Modest JavaScript framework
-- **React** - Popular UI library
-- **Vue** - Progressive JavaScript framework
-- **Alpine.js** - Minimal framework for HTML
-- **Vanilla JS** - No framework
-
-## Building Powerful Websites
-
-### Using ERB Templates
-
-Create pages in `app/views/pages/`:
-
-```erb
-<h1><%= @title %></h1>
-<p><%= @description %></p>
-```
-
-Page metadata is automatically configured in `lib/page_helpers.rb` (generated automatically):
-
-```ruby
-module PageHelpers
-  PAGES = {
-    '/' => {
-      title: 'My Page',
-      description: 'A great page',
-      url: 'https://example.com',
-      image: 'https://example.com/image.jpg',
-      priority: 1.0,
-      changefreq: 'weekly'
-    }
-  }.freeze
-end
-```
+## Templates
 
-The builder automatically loads metadata from `PageHelpers::PAGES` and sets `@title`, `@description`, `@url`, and `@image` instance variables for use in your templates. This metadata is also used by the `sitemap_generator` gem for generating sitemaps.
+Generated sites use **ActionView** for Rails-like templates, helpers, layouts, and partials.
 
-Use layouts in `app/views/layouts/application.html.erb`:
+Create a layout in `app/views/layouts/application.html.erb`:
 
 ```erb
 <!DOCTYPE html>
-<html>
+<html lang="en">
 <head>
-  <title><%= @title || "My Site" %></title>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <link rel="stylesheet" href="/assets/stylesheets/application.css">
 </head>
 <body>
-  <%= yield %>
+  <main>
+    <%= yield %>
+  </main>
+
+  <% if content_for?(:javascript) %>
+    <%= yield(:javascript) %>
+  <% end %>
 </body>
 </html>
 ```
 
-### Using Phlex Components
-
-Create reusable components in `app/views/components/`:
-
-```ruby
-class Button < Phlex::HTML
-  def initialize(text:, href:, variant: "primary")
-    @text = text
-    @href = href
-    @variant = variant
-  end
-
-  def template
-    a(href: @href, class: "btn btn-#{@variant}") { @text }
-  end
-end
-```
-
-Use in pages:
+`yield` outputs the page content. Use `content_for(:javascript)` to push scripts into the layout.
 
-```ruby
-class HomePage < Phlex::HTML
-  def template
-    div do
-      h1 { "Welcome" }
-      render Button.new(text: "Get Started", href: "/about")
-    end
-  end
-end
-```
-
-### JavaScript with Importmap
+### Partials
 
-No bundling needed - use ES modules directly:
+Partials work like Rails, including `locals:`:
 
-```javascript
-// app/javascript/application.js
-import { Application } from "@hotwired/stimulus"
-import HelloController from "./controllers/hello_controller"
-
-window.Stimulus = Application.start()
-Stimulus.register("hello", HelloController)
+```erb
+<%= render partial: 'shared/header', locals: { title: 'Home' } %>
 ```
 
-### JavaScript with Bundlers
-
-Use ESBuild, Webpack, or Vite for modern tooling:
+### Adding JavaScript
 
-```javascript
-// app/javascript/index.js
-import React from 'react'
-import { createRoot } from 'react-dom/client'
+Include JavaScript files in your pages:
 
-function App() {
-  return <h1>Hello from React!</h1>
-}
-
-const root = createRoot(document.getElementById('app'))
-root.render(<App />)
+```erb
+<% content_for(:javascript) do %>
+  <script src="/assets/javascripts/application.js"></script>
+<% end %>
 ```
 
-### CSS with TailwindCSS
-
-Use utility classes directly in templates:
+If you add a `package.json` with a `scripts.build`, `rake build:assets` will run `npm run build`. If you do not, it copies `app/javascript/` into `dist/assets/javascripts/`.
 
-```erb
-<div class="container mx-auto px-4">
-  <h1 class="text-4xl font-bold text-gray-900">Hello World</h1>
-</div>
-```
+Set up your own bundler if needed and output to `dist/assets/javascripts/`. See setup guides:
+- [ESBuild](guides/setup-esbuild.md)
+- [Webpack](https://webpack.js.org/) - see webpack documentation
+- [Vite](https://github.com/ElMassimo/vite_ruby) - see vite-plugin-ruby
 
-### CSS with shadcn/ui
+### Adding CSS
 
-Install components and use them in your templates:
+Write CSS in `app/assets/stylesheets/application.css`. Use any CSS tool you prefer:
 
-```bash
-npx shadcn-ui@latest add button
-```
+- [Tailwind CSS](guides/setup-tailwind.md)
+- PostCSS, Sass, Less, or any other CSS processor - just compile your CSS files to `dist/assets/stylesheets/` before building HTML.
 
 ### Generating Sitemaps
 
 Sitemap generation is automatically configured when you generate a new site. The `sitemap_generator` gem is included in the Gemfile, and `config/sitemap.rb` is automatically created.
 
-The sitemap is generated from your `PageHelpers::PAGES` metadata during `rake build:all`. Update `config/sitemap.rb` to set your domain:
+The sitemap is automatically generated from all pages in `app/views/pages/` during `rake build:all`. Update `config/sitemap.rb` to set your domain:
 
 ```ruby
 SitemapGenerator::Sitemap.default_host = 'https://yourdomain.com'
 ```
 
-The sitemap will be generated in `dist/sitemaps/sitemap.xml.gz` during the build process.
+You can customize priority, changefreq, and lastmod in `config/sitemap.rb`. The sitemap will be generated in `dist/sitemaps/sitemap.xml.gz` during the build process.
 
 ## Examples
 
-### ERB + Importmap + Stimulus + TailwindCSS
+### Basic ERB Site
 ```bash
 static-site-builder new my-site
-# Choose: ERB, Importmap, TailwindCSS, Stimulus
 ```
 
-### Phlex + ESBuild + React + shadcn
-```bash
-static-site-builder new my-site
-# Choose: Phlex, ESBuild, shadcn/ui, React
-```
+## Notable Projects
 
-## Requirements
+Sites built with Static Site Builder:
 
-### For Importmap Projects
+- **[lukaszczapiewski.com](https://lukaszczapiewski.com)** - Personal portfolio and blog
 
-When using **Importmap** as your JavaScript bundler:
+**Your website?** Built with Static Site Builder? [Submit a PR](https://github.com/Ancez/static-site-builder) to add it here!
 
-1. **Install npm dependencies**:
-   ```bash
-   npm install
-   ```
+## Requirements
 
-2. **Build your site** - vendor files are automatically copied from `node_modules` to `dist/assets/javascripts/` during the build:
-   ```bash
-   rake build:all
-   ```
+- Ruby 3.0+
+- Bundler
 
-The build process automatically copies required vendor JavaScript files directly from `node_modules` to `dist/assets/javascripts/` based on your importmap configuration. No intermediate `vendor/javascript/` folder is needed.
+Optional (if you want to use Tailwind CSS or JavaScript bundlers):
+- Node.js and npm
 
 ## Development
 
@@ -283,7 +194,6 @@ After generating a site, you can run it locally with auto-rebuild and live reloa
 ```bash
 cd my-site
 bundle install
-npm install  # Required for importmap projects and JS frameworks
 
 # Start development server (auto-rebuilds on file changes)
 rake dev:server
@@ -316,142 +226,12 @@ rake build:html
 
 The `dist/` directory contains your complete static site and can be deployed to any static hosting provider.
 
-### Cloudflare Pages
-
-1. **Connect your repository** to Cloudflare Pages in the Cloudflare dashboard
-
-2. **Build settings**:
-   - **Build command**: `bundle install && npm install && bundle exec rake build:all`
-   - **Build output directory**: `dist`
-   - **Root directory**: (leave empty or set to repository root)
-
-3. **Environment variables** (if needed):
-   - `RUBY_VERSION`: Set to your Ruby version (e.g., `3.4`)
-   - `NODE_VERSION`: Set to your Node.js version (e.g., `24`)
-
-4. **Deploy**: Cloudflare Pages will automatically build and deploy on every push to your main branch
-
-**Note**: Cloudflare Pages supports Ruby and Node.js builds. Ensure your `Gemfile` and `package.json` are properly configured.
-
-### Vercel
-
-1. **Install Vercel CLI** (optional):
-   ```bash
-   npm i -g vercel
-   ```
-
-2. **Deploy**:
-   ```bash
-   # Build locally first
-   bundle install && npm install && bundle exec rake build:all
-   
-   # Deploy
-   vercel --prod
-   ```
-
-   Or connect your repository in the Vercel dashboard with these settings:
-   - **Build Command**: `bundle install && npm install && bundle exec rake build:all`
-   - **Output Directory**: `dist`
-   - **Install Command**: `bundle install && npm install`
-
-3. **Configuration file** (optional `vercel.json`):
-   ```json
-   {
-     "buildCommand": "bundle install && npm install && bundle exec rake build:all",
-     "outputDirectory": "dist",
-     "installCommand": "bundle install && npm install"
-   }
-   ```
-
-### Netlify
-
-1. **Create `netlify.toml`** in your project root:
-   ```toml
-   [build]
-     command = "bundle install && npm install && bundle exec rake build:all"
-     publish = "dist"
-   
-   [build.environment]
-     RUBY_VERSION = "3.4"
-     NODE_VERSION = "24"
-   ```
-
-2. **Deploy**:
-   - Connect your repository in Netlify dashboard
-   - Netlify will automatically detect `netlify.toml` and use those settings
-   - Or use Netlify CLI: `netlify deploy --prod`
-
-### GitHub Pages
-
-1. **Using GitHub Actions** (recommended):
-
-   Create `.github/workflows/deploy.yml`:
-   ```yaml
-   name: Deploy to GitHub Pages
-   
-   on:
-     push:
-       branches: [ main ]
-   
-   jobs:
-     deploy:
-       runs-on: ubuntu-latest
-       steps:
-         - uses: actions/checkout@v4
-         
-         - name: Set up Ruby
-           uses: ruby/setup-ruby@v1
-           with:
-             ruby-version: 3.4
-             bundler-cache: true
-         
-         - name: Set up Node.js
-           uses: actions/setup-node@v4
-           with:
-             node-version: '24'
-             cache: 'npm'
-         
-         - name: Install dependencies
-           run: |
-             bundle install
-             npm install
-         
-        - name: Build site
-          run: bundle exec rake build:all
-          # Note: Vendor files will be automatically copied from node_modules during build
-         
-         - name: Deploy to GitHub Pages
-           uses: peaceiris/actions-gh-pages@v4
-           with:
-             github_token: ${{ secrets.GITHUB_TOKEN }}
-             publish_dir: ./dist
-   ```
-
-2. **Enable GitHub Pages** in your repository settings:
-   - Go to Settings → Pages
-   - Source: GitHub Actions
-
-### Other Static Hosts
-
-For any static hosting provider (AWS S3, Azure Static Web Apps, etc.):
-
-1. **Build locally**:
-   ```bash
-   bundle install
-   npm install
-   bundle exec rake build:all
-   ```
-
-2. **Upload `dist/` directory** to your hosting provider
-
-3. **Configure** your host to serve from the `dist` directory
-
-### CI/CD Considerations
-
-- **Vendor files**: Vendor files are automatically copied from `node_modules` to `dist/` during build - no vendor folder needed
-- **Dependencies**: Both Ruby (`Gemfile`) and Node.js (`package.json`) dependencies are needed for the build
-- **Build order**: Install dependencies → Build assets → Build HTML
-- **Ruby/Node versions**: Specify versions in your CI/CD configuration to ensure consistent builds
+See deployment guides for specific platforms:
+- [Cloudflare Pages](guides/deployment-cloudflare.md)
+- [Vercel](guides/deployment-vercel.md)
+- [Netlify](guides/deployment-netlify.md)
+- [GitHub Pages](guides/deployment-github-pages.md)
+- [Other Static Hosts](guides/deployment-other.md)
 
 ### Generator Development
 
@@ -500,10 +280,8 @@ This generator follows the Rails pattern:
 ## Contributing
 
 Contributions welcome! Especially:
-- New template engine support
-- New bundler integrations
-- New CSS framework setups
 - Documentation improvements
+- New features and improvements
 
 ## License