oxie 0.3.1__tar.gz

oxie-0.3.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2024-2026 Puyu Wang
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

oxie-0.3.1/PKG-INFO

@@ -0,0 +1,228 @@
+Metadata-Version: 2.4
+Name: oxie
+Version: 0.3.1
+Summary: A small static site/blog generator: Markdown + Jinja2 + Tailwind
+Author: Puyu Wang
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/PaulWang1905/oxie
+Project-URL: Issues, https://github.com/PaulWang1905/oxie/issues
+Keywords: static-site-generator,blog,markdown,jinja2
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Internet :: WWW/HTTP :: Site Management
+Classifier: Topic :: Text Processing :: Markup :: HTML
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: Jinja2>=3.1
+Requires-Dist: Markdown>=3.6
+Requires-Dist: pymdown-extensions>=10.0
+Requires-Dist: python-frontmatter>=1.1
+Requires-Dist: Pygments>=2.17
+Requires-Dist: pillow>=10.0
+Provides-Extra: sheets
+Requires-Dist: pandas>=2.0; extra == "sheets"
+Dynamic: license-file
+
+# oxie
+
+**oxie** is a small static site/blog generator written in Python. It converts
+Markdown into a styled, SEO-friendly static website using Jinja2 templates and
+**Tailwind CSS v4**.
+
+One package, many sites: each site supplies its own content, templates and
+`SiteConfig`, and oxie does the rest. `oxie init` gives you all three,
+pre-wired and building.
+
+## Requirements
+
+- Python 3.10+ (3.8 nominally supported but untested)
+- Node.js and npm — Tailwind CSS is a required part of the build
+
+## Quick start
+
+```bash
+pip install oxie
+
+oxie init myblog --title "My Blog" --author "Your Name"
+cd myblog
+npm install       # Tailwind CSS v4
+python build.py   # writes docs/
+```
+
+Open `docs/index.html`, and you have a working blog: home page, a sample post,
+an about page, a blog index and a category page, with compiled Tailwind
+styling and syntax highlighting.
+
+`oxie init` never overwrites an existing file unless you pass `--force`, so it
+is safe to run in a directory that already has content.
+
+## What init creates
+
+```
+source/            # content — edit this
+  index.md         # home page
+  post/*.md        # blog posts
+  page/*.md        # standalone pages
+  image/           # images, copied to docs/image
+  static/          # raw files, copied to the site root
+src/               # Jinja2 templates + meta_data.json + styles.css
+  base.html        # shared layout the others extend
+  index.html  template.html  blog_template.html  category_template.html
+docs/              # generated output (GitHub Pages friendly)
+build.py           # your site's config
+package.json       # Tailwind v4 via @tailwindcss/cli
+```
+
+`build.py` is the whole per-site program:
+
+```python
+from oxie import Site, SiteConfig
+
+config = SiteConfig(
+    collect_dirs={"source/image": "docs/image", "source/static": "docs"},
+    pygments_style="github-dark",
+    css_build_command=("npm", "run", "build:css"),
+)
+
+if __name__ == "__main__":
+    Site(config).build()
+```
+
+## Styling
+
+Tailwind v4 is configured **CSS-first** — there is no `tailwind.config.js` and
+no `postcss.config.js`. Everything lives in `src/styles.css`:
+
+```css
+@import "tailwindcss";
+@plugin "@tailwindcss/typography";
+
+@source "../src/**/*.html";
+@source "../docs/**/*.html";
+@source "../source/**/*.md";
+```
+
+Because the Jinja templates in `src/` are scanned as well as the generated
+HTML in `docs/`, classes are never purged just because CSS was built before
+HTML. Rendered Markdown is wrapped in the typography plugin's `prose` classes,
+and the bundled templates support light and dark via `dark:` variants.
+
+The templates copied into `src/` are yours — edit them freely. If you delete
+one, oxie falls back to its bundled copy, so a site always renders; set
+`use_bundled_templates=False` to make a missing template an error instead.
+
+## What a build does
+
+`Site.build()` runs, in order:
+
+1. `clean_old_files()` — removes generated HTML, the stylesheet and the image
+   directory from the output folder.
+2. `generate_html()` — Markdown → HTML for every post and page, then
+   `posts_metadata.jsonld` (Schema.org `BlogPosting` data), the per-category
+   pages, the blog index, and the home page.
+3. `render_simple_pages()` — any extra one-off template pages.
+4. `render_photography_page()` — optional; parses a `photos.md` album file.
+5. `collect_static_files()` — copies images and static files to the output.
+6. `generate_thumbnails()` — optional; gallery thumbnails via Pillow.
+7. `build_css()` — optional; runs your CSS command (e.g. `npm run build:css`).
+8. `build_pygments_css()` — optional; syntax-highlighting stylesheet.
+
+**Ordering note:** HTML is generated *before* CSS, so Tailwind sees the
+finished HTML. The bundled `styles.css` also scans `src/` and `source/`, so
+this ordering is belt-and-braces rather than load-bearing.
+
+## Configuration
+
+Every path and feature lives on `SiteConfig`:
+
+| Field | Default | Purpose |
+|---|---|---|
+| `source_dir` | `source` | Markdown content root |
+| `template_dir` | `src` | Jinja2 templates |
+| `output_dir` | `docs` | Generated site |
+| `meta_data_file` | `src/meta_data.json` | Site metadata (title, link, image, phrases…) |
+| `use_bundled_templates` | `True` | Fall back to oxie's templates for anything the site omits |
+| `markdown_extensions` / `..._configs` | pymdownx set | Markdown pipeline |
+| `collect_dirs` | `source/image`→`docs/image`, `source/static`→`docs/page` | Static asset copying |
+| `index_excluded_titles` | Terms of Service, Privacy Policy | Pages hidden from the index listing |
+| `simple_pages` | `{}` | template name → output name, rendered once |
+| `photography` / `photos_md` | `False` | Photo album page |
+| `thumbnails` / `thumbnail_dir` / `thumbnail_width` | `False` / … / `600` | Gallery thumbnails |
+| `css_build_command` | `("npm", "run", "build:css")` | Set to `None` to skip |
+| `pygments_style` | `None` | e.g. `"github-dark"` |
+
+## Content format
+
+Posts and pages use YAML frontmatter with capitalised keys:
+
+```markdown
+---
+Title:   Silver Age
+Summary: A short story about a deduplication officer.
+Authors: Puyu Wang
+Date:    2026-07-17
+Category: Story
+Tags: [Story]
+Last_modified: 2026-07-18   # optional, defaults to Date
+Image: image/cover.jpg      # optional, defaults to meta_data["image"]
+---
+
+Your markdown here.
+```
+
+`index.md` uses the Markdown `meta` extension style instead (`Key: value`
+lines at the top of the file, no `---` fences).
+
+Templates the generator expects in `template_dir`: `template.html` (posts and
+pages), `index.html`, `blog_template.html`, `category_template.html`, plus any
+you list in `simple_pages` and `photography_template.html` if enabled. `oxie
+init` writes the first four (and a shared `base.html` they extend); the
+generator falls back to its bundled copies for any you remove.
+
+Context passed to each template differs — `meta_data` reaches `template.html`
+and `index.html` but **not** `blog_template.html` or `category_template.html`,
+which receive `title`, `phrases` and their posts. The comment at the top of
+each bundled template lists exactly what it gets.
+
+### Recent updates from a Google Sheet (optional)
+
+If `meta_data.json` contains `update_spreedsheet_id`, oxie reads that public
+spreadsheet's CSV export (columns `Date` and `Content`) and passes the five
+most recent entries to the index template as `updates`. Omit the key and the
+list is simply empty — no network access is attempted.
+
+This feature requires the optional Sheets dependencies:
+
+```bash
+pip install 'oxie[sheets]'
+```
+
+## Development
+
+```bash
+uv venv && uv pip install -e '.[sheets]' --python .venv/bin/python
+.venv/bin/python -m unittest discover -s tests -v
+```
+
+The test suite runs fully offline.
+
+## Status and known issues
+
+Version 0.3.1, extracted from the generator behind
+[puyuwang.org](https://puyuwang.org). Two behaviours are carried over from
+that codebase and preserved deliberately:
+
+- Category order on the blog index comes from iterating a Python `set`, so the
+  file's contents can differ between runs. Set `PYTHONHASHSEED=0` when
+  comparing builds.
+- `IndexPage.parse()` overwrites `meta_data["title"]` with the title from
+  `index.md`, and indexes into the description string, which yields its first
+  character rather than the whole description.
+
+## Licence
+
+Apache License 2.0 — see the
+[LICENSE](https://github.com/PaulWang1905/oxie/blob/main/LICENSE).

oxie-0.3.1/README.md

@@ -0,0 +1,200 @@
+# oxie
+
+**oxie** is a small static site/blog generator written in Python. It converts
+Markdown into a styled, SEO-friendly static website using Jinja2 templates and
+**Tailwind CSS v4**.
+
+One package, many sites: each site supplies its own content, templates and
+`SiteConfig`, and oxie does the rest. `oxie init` gives you all three,
+pre-wired and building.
+
+## Requirements
+
+- Python 3.10+ (3.8 nominally supported but untested)
+- Node.js and npm — Tailwind CSS is a required part of the build
+
+## Quick start
+
+```bash
+pip install oxie
+
+oxie init myblog --title "My Blog" --author "Your Name"
+cd myblog
+npm install       # Tailwind CSS v4
+python build.py   # writes docs/
+```
+
+Open `docs/index.html`, and you have a working blog: home page, a sample post,
+an about page, a blog index and a category page, with compiled Tailwind
+styling and syntax highlighting.
+
+`oxie init` never overwrites an existing file unless you pass `--force`, so it
+is safe to run in a directory that already has content.
+
+## What init creates
+
+```
+source/            # content — edit this
+  index.md         # home page
+  post/*.md        # blog posts
+  page/*.md        # standalone pages
+  image/           # images, copied to docs/image
+  static/          # raw files, copied to the site root
+src/               # Jinja2 templates + meta_data.json + styles.css
+  base.html        # shared layout the others extend
+  index.html  template.html  blog_template.html  category_template.html
+docs/              # generated output (GitHub Pages friendly)
+build.py           # your site's config
+package.json       # Tailwind v4 via @tailwindcss/cli
+```
+
+`build.py` is the whole per-site program:
+
+```python
+from oxie import Site, SiteConfig
+
+config = SiteConfig(
+    collect_dirs={"source/image": "docs/image", "source/static": "docs"},
+    pygments_style="github-dark",
+    css_build_command=("npm", "run", "build:css"),
+)
+
+if __name__ == "__main__":
+    Site(config).build()
+```
+
+## Styling
+
+Tailwind v4 is configured **CSS-first** — there is no `tailwind.config.js` and
+no `postcss.config.js`. Everything lives in `src/styles.css`:
+
+```css
+@import "tailwindcss";
+@plugin "@tailwindcss/typography";
+
+@source "../src/**/*.html";
+@source "../docs/**/*.html";
+@source "../source/**/*.md";
+```
+
+Because the Jinja templates in `src/` are scanned as well as the generated
+HTML in `docs/`, classes are never purged just because CSS was built before
+HTML. Rendered Markdown is wrapped in the typography plugin's `prose` classes,
+and the bundled templates support light and dark via `dark:` variants.
+
+The templates copied into `src/` are yours — edit them freely. If you delete
+one, oxie falls back to its bundled copy, so a site always renders; set
+`use_bundled_templates=False` to make a missing template an error instead.
+
+## What a build does
+
+`Site.build()` runs, in order:
+
+1. `clean_old_files()` — removes generated HTML, the stylesheet and the image
+   directory from the output folder.
+2. `generate_html()` — Markdown → HTML for every post and page, then
+   `posts_metadata.jsonld` (Schema.org `BlogPosting` data), the per-category
+   pages, the blog index, and the home page.
+3. `render_simple_pages()` — any extra one-off template pages.
+4. `render_photography_page()` — optional; parses a `photos.md` album file.
+5. `collect_static_files()` — copies images and static files to the output.
+6. `generate_thumbnails()` — optional; gallery thumbnails via Pillow.
+7. `build_css()` — optional; runs your CSS command (e.g. `npm run build:css`).
+8. `build_pygments_css()` — optional; syntax-highlighting stylesheet.
+
+**Ordering note:** HTML is generated *before* CSS, so Tailwind sees the
+finished HTML. The bundled `styles.css` also scans `src/` and `source/`, so
+this ordering is belt-and-braces rather than load-bearing.
+
+## Configuration
+
+Every path and feature lives on `SiteConfig`:
+
+| Field | Default | Purpose |
+|---|---|---|
+| `source_dir` | `source` | Markdown content root |
+| `template_dir` | `src` | Jinja2 templates |
+| `output_dir` | `docs` | Generated site |
+| `meta_data_file` | `src/meta_data.json` | Site metadata (title, link, image, phrases…) |
+| `use_bundled_templates` | `True` | Fall back to oxie's templates for anything the site omits |
+| `markdown_extensions` / `..._configs` | pymdownx set | Markdown pipeline |
+| `collect_dirs` | `source/image`→`docs/image`, `source/static`→`docs/page` | Static asset copying |
+| `index_excluded_titles` | Terms of Service, Privacy Policy | Pages hidden from the index listing |
+| `simple_pages` | `{}` | template name → output name, rendered once |
+| `photography` / `photos_md` | `False` | Photo album page |
+| `thumbnails` / `thumbnail_dir` / `thumbnail_width` | `False` / … / `600` | Gallery thumbnails |
+| `css_build_command` | `("npm", "run", "build:css")` | Set to `None` to skip |
+| `pygments_style` | `None` | e.g. `"github-dark"` |
+
+## Content format
+
+Posts and pages use YAML frontmatter with capitalised keys:
+
+```markdown
+---
+Title:   Silver Age
+Summary: A short story about a deduplication officer.
+Authors: Puyu Wang
+Date:    2026-07-17
+Category: Story
+Tags: [Story]
+Last_modified: 2026-07-18   # optional, defaults to Date
+Image: image/cover.jpg      # optional, defaults to meta_data["image"]
+---
+
+Your markdown here.
+```
+
+`index.md` uses the Markdown `meta` extension style instead (`Key: value`
+lines at the top of the file, no `---` fences).
+
+Templates the generator expects in `template_dir`: `template.html` (posts and
+pages), `index.html`, `blog_template.html`, `category_template.html`, plus any
+you list in `simple_pages` and `photography_template.html` if enabled. `oxie
+init` writes the first four (and a shared `base.html` they extend); the
+generator falls back to its bundled copies for any you remove.
+
+Context passed to each template differs — `meta_data` reaches `template.html`
+and `index.html` but **not** `blog_template.html` or `category_template.html`,
+which receive `title`, `phrases` and their posts. The comment at the top of
+each bundled template lists exactly what it gets.
+
+### Recent updates from a Google Sheet (optional)
+
+If `meta_data.json` contains `update_spreedsheet_id`, oxie reads that public
+spreadsheet's CSV export (columns `Date` and `Content`) and passes the five
+most recent entries to the index template as `updates`. Omit the key and the
+list is simply empty — no network access is attempted.
+
+This feature requires the optional Sheets dependencies:
+
+```bash
+pip install 'oxie[sheets]'
+```
+
+## Development
+
+```bash
+uv venv && uv pip install -e '.[sheets]' --python .venv/bin/python
+.venv/bin/python -m unittest discover -s tests -v
+```
+
+The test suite runs fully offline.
+
+## Status and known issues
+
+Version 0.3.1, extracted from the generator behind
+[puyuwang.org](https://puyuwang.org). Two behaviours are carried over from
+that codebase and preserved deliberately:
+
+- Category order on the blog index comes from iterating a Python `set`, so the
+  file's contents can differ between runs. Set `PYTHONHASHSEED=0` when
+  comparing builds.
+- `IndexPage.parse()` overwrites `meta_data["title"]` with the title from
+  `index.md`, and indexes into the description string, which yields its first
+  character rather than the whole description.
+
+## Licence
+
+Apache License 2.0 — see the
+[LICENSE](https://github.com/PaulWang1905/oxie/blob/main/LICENSE).

oxie-0.3.1/oxie/__init__.py

@@ -0,0 +1,28 @@
+'''
+oxie — a small static site/blog generator.
+
+Converts Markdown content into a styled, SEO-friendly static website
+using Jinja2 templates. A site is described by a SiteConfig (paths and
+optional features) and built by a Site:
+
+    from oxie import Site, SiteConfig
+
+    Site(SiteConfig()).build()
+
+To start a new site from scratch, use the command line instead:
+
+    oxie init myblog --title "My Blog"
+'''
+from .config import SiteConfig
+from .content import Post, Category
+from .scaffold import init_site
+from .site import Site, BlogIndex, IndexPage, generate_posts_jsonld
+from .updates import Update, UpdateReader
+
+__version__ = "0.3.1"
+
+__all__ = [
+    "Site", "SiteConfig", "Post", "Category", "BlogIndex", "IndexPage",
+    "generate_posts_jsonld", "init_site", "Update", "UpdateReader",
+    "__version__",
+]

oxie-0.3.1/oxie/__main__.py

@@ -0,0 +1,7 @@
+'''Entry point for `python -m oxie`.'''
+import sys
+
+from .cli import main
+
+if __name__ == "__main__":
+    sys.exit(main())