jamstack 1.1.0__tar.gz → 2.0.0rc1__tar.gz

jamstack-2.0.0rc1/.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*.{md,py,txt}]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

jamstack-2.0.0rc1/.github/workflows/ci.yml

@@ -0,0 +1,59 @@
+name: CI
+
+on:
+  push:
+    branches: [stable, "2.0"]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - run: pip install ruff
+      - run: ruff check .
+      - run: ruff format --check .
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: pytest --cov --cov-report=term-missing
+
+  commits:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - run: pip install commitizen
+      - run: cz check --rev-range origin/${{ github.base_ref }}..HEAD
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - run: pip install -e ".[dev]"
+      - run: zensical build --strict

jamstack-2.0.0rc1/.github/workflows/release.yml

@@ -0,0 +1,42 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - run: pip install -e ".[dev]" build
+      - run: ruff check .
+      - run: ruff format --check .
+      - run: pytest
+      - name: Check version matches tag
+        run: |
+          python -c "import jamstack, os; assert jamstack.__version__ == os.environ['GITHUB_REF_NAME'].lstrip('v'), jamstack.__version__"
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

jamstack-2.0.0rc1/.gitignore

@@ -0,0 +1,134 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+.idea/
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+/dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# Local tooling
+.venv/
+.ruff_cache/
+site/

jamstack-2.0.0rc1/.pre-commit-config.yaml

@@ -0,0 +1,19 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-toml
+      - id: check-yaml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.17.4
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/commitizen-tools/commitizen
+    rev: v4.19.3
+    hooks:
+      - id: commitizen
+        stages: [commit-msg]

jamstack-2.0.0rc1/CHANGELOG.md

@@ -0,0 +1,62 @@
+# Changelog
+
+All notable changes to this project are documented in this file. Entries before
+2.0 were written by hand; later entries are generated from Conventional Commits.
+
+## 2.0.0rc1 (2026-11-07)
+
+### Breaking
+
+- The 1.x engine is gone: projects built with `settings.py`, `static.py` and the
+  html5up themes must migrate to `site.toml` and `content/`. See `docs/migration.md`.
+
+### Feat
+
+- **themes**: render a 404 page from the active theme
+- **feed**: generate sitemap.xml and an Atom feed
+- **serve**: rebuild the site when sources change
+- **serve**: serve the built site over HTTP
+- **themes**: add theme manifests and a reading-first blog theme
+- **build**: render sites with the bundled minimal theme
+- **content**: parse front matter and resolve page URLs
+- **config**: load and validate site.toml
+
+### Fix
+
+- **serve**: keep watching after a failed rebuild
+- **serve**: flush status messages in redirected output
+
+## 1.1.0
+
+* Bulk refactors and code documentation
+* New commands for `static.py` files
+    * `--serve` for livewatch changes
+    * `--watch` for watch specific files and folders.
+    * `--port` especiffy serve port
+
+## 1.0.0
+
+* Back to namespace method for write templates names
+    * Example: `html5up/massively` instead of just `massively`
+* Template assets are not included in the library to minimize the size of the library, they were moved to
+  a [separate repository](https://github.com/jamstackpy/jamstack-templates).
+
+## 0.1.0
+
+* Improve **Plain** template
+* Add new templates (massively, phantom)
+* When creating a project, instead of writing the template like this: **html5up/massively**, you can use the name
+  directly, i.e. **massively**
+* The assets of each template are now included in the library
+
+## 0.0.4
+
+* Add README.md info
+
+## 0.0.3
+
+* Add plain template
+
+## 0.0.1
+
+* Initial release

jamstack-2.0.0rc1/CONTRIBUTING.md

@@ -0,0 +1,74 @@
+# Contributing
+
+## Development setup
+
+```bash
+git clone git@github.com:jamstackpy/jamstack.git
+cd jamstack
+git switch 2.0
+python -m venv .venv
+. .venv/bin/activate
+pip install -e ".[dev]"
+pre-commit install --hook-type pre-commit --hook-type commit-msg
+```
+
+Run the checks before opening a pull request:
+
+```bash
+ruff check .
+ruff format --check .
+pytest
+```
+
+## Commits
+
+Commits follow [Conventional Commits](https://www.conventionalcommits.org/) in
+English:
+
+```
+feat(cli): add a --drafts flag to build
+fix(content): reject dates without a year
+docs: explain local theme overrides
+```
+
+One commit is one reviewable intention. Do not mix unrelated changes under a
+message that only describes one of them, and do not leave intermediate commits
+that fail the tests. Mechanical changes (renames, formatting, dependency
+bumps) go in their own commit.
+
+Write a body when the change needs context: bullet points, in English,
+explaining what and why. `commitizen` validates the message through the
+`commit-msg` hook installed above.
+
+## Pull requests
+
+- Target the `2.0` branch.
+- Include a test for new behaviour; bug fixes should include the case that
+  reproduces the bug.
+- Keep user-facing strings and documentation in English.
+- Do not rewrite pushed history.
+
+## Releasing
+
+Publishing runs on tags through GitHub Actions and PyPI trusted publishing,
+with no API tokens stored anywhere.
+
+One-time setup:
+
+1. On PyPI, open the `jamstack` project → Publishing → add a GitHub publisher
+   with owner `jamstackpy`, repository `jamstack`, workflow `release.yml`, and
+   environment `pypi`.
+2. On GitHub, create an environment named `pypi` in the repository settings.
+
+For the first 2.0 release, the version in `src/jamstack/__about__.py` is
+`2.0.0.dev0`. Set it to `2.0.0`, regenerate the changelog, and tag:
+
+```bash
+cz changelog
+git commit -am "chore(release): 2.0.0"
+git tag v2.0.0
+git push origin 2.0 v2.0.0
+```
+
+Later releases use `cz bump`, which updates the version, rewrites
+`CHANGELOG.md`, commits, and creates the tag in one step.