Skip to content

docs: document GitHub Pages source setup #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
phcodesage merged 1 commit into from
Sep 12, 2026
Merged

docs: document GitHub Pages source setup #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ The `/htmx` demo shows an optional HTMX enhancement around a normal Flask form.

The demo also includes realistic application screens at `/blocks`, `/login`, `/signup`, and `/admin`. The reusable block macros live under `jinjalume/blocks/` and compose the core components into auth flows and a responsive admin console. See [docs/blocks.md](docs/blocks.md) for signatures and copy-paste examples.

The public landing page source lives in [`site/`](site/). The Pages workflow publishes it from the `main` branch; the repository's Pages setting should use **GitHub Actions** as its build source.
The public landing page source lives in [`site/`](site/). The Pages workflow publishes it from the `main` branch. Before the first deployment, a repository administrator or maintainer must open [Settings → Pages](https://github.com/phcodesage/jinjalume/settings/pages) and select **GitHub Actions** as the build source; this is a one-time repository setting that cannot be enabled by the default workflow token.

## Development

Expand Down
Loading