Skip to content

Add documentation pages#31

Open
karamouche wants to merge 10 commits into
mainfrom
feat/mkdocs
Open

Add documentation pages#31
karamouche wants to merge 10 commits into
mainfrom
feat/mkdocs

Conversation

@karamouche

@karamouche karamouche commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

Adds Gladia-branded MkDocs documentation with GitHub Pages deploy, custom theme/styles, and reorganized docs.

Type of change

  • New language
  • Edit existing language (fix a replacement, tweak config, …)
  • New normalization step
  • Edit existing step (bug fix, behaviour change)
  • New preset version
  • Bug fix (other)
  • Refactor / docs / CI

How was this tested?

uv run mkdocs build --strict
uv run mkdocs serve

Note

Low Risk
Documentation, theme assets, and CI-only changes; no runtime normalization logic is modified.

Overview
Introduces a Gladia-branded MkDocs Material documentation site (mkdocs.yml, docs/**, overrides/, custom CSS/assets) covering getting started, concepts, usage (Python/CLI), presets, languages, generated step reference, and contributing guides.

CI/CD: Adds a docs job to ci.yml (uv sync --group docs, mkdocs build --strict) and a path-filtered docs.yml workflow that builds and deploys to GitHub Pages on main.

Tooling & links: New docs dependency group in pyproject.toml, PyPI Documentation URL, site/ in .gitignore, and generate_step_docs.py now defaults to docs/reference/steps.md. README, CONTRIBUTING.md, and AGENTS.md point at the published site and reorganized paths (contributing/guide.md).

Docs content tweaks: Norwegian (no) appears in supported-language tables; sample preset YAML no longer lists redundant normalize_whitespace steps.

Reviewed by Cursor Bugbot for commit 3467213. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • New Features
    • Launched a complete MkDocs documentation site (concepts, getting started, usage, presets, languages, step reference, and contributing) with a branded theme and light/dark styling.
    • Documentation is now automatically built with validation and published to GitHub Pages.
    • Added Norwegian (no) to the supported language list.
  • Documentation
    • Updated README and contribution materials to point to the new docs structure, updated commands, and added a CLI and Python API reference.
    • Added/updated concepts and presets guides; step reference is now fully generated under the new reference path.

@karamouche
karamouche requested a review from egenthon-cmd July 14, 2026 14:15
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The PR adds a MkDocs documentation site with new guides, references, custom styling, CI validation, and GitHub Pages deployment. It also updates documentation links, generated step-reference paths, project metadata, and contributor setup instructions.

Changes

Documentation site

Layer / File(s) Summary
MkDocs site foundation
.gitignore, mkdocs.yml, docs/stylesheets/*, overrides/*, pyproject.toml
Adds MkDocs configuration, documentation dependencies, theme customization, Gladia styling, template overrides, project documentation metadata, and site/ exclusion.
User and contributor documentation
docs/index.md, docs/getting-started.md, docs/concepts.md, docs/usage/*, docs/presets.md, docs/languages.md, docs/contributing/*, README.md
Adds landing, onboarding, concepts, API, CLI, preset, language, and contribution documentation, and updates README navigation and examples.
Generated step reference
scripts/generate_step_docs.py, docs/reference/steps.md, AGENTS.md, CONTRIBUTING.md, docs/contributing/guide.md
Moves generated step documentation to docs/reference/steps.md, adds the generated reference, and updates related contributor instructions and links.
CI validation and Pages delivery
.github/workflows/ci.yml, .github/workflows/docs.yml
Adds strict documentation validation to CI and a GitHub Pages workflow that builds, uploads, and deploys the site.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant MkDocs
  participant GitHubPages
  GitHubActions->>MkDocs: install docs dependencies and run strict build
  MkDocs-->>GitHubActions: produce site artifact
  GitHubActions->>GitHubPages: upload and deploy site artifact
Loading

Suggested reviewers: egenthon-cmd

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is related, but it is too generic to convey the main change beyond adding docs pages. Use a more specific title like "Add MkDocs documentation site and GitHub Pages deployment".
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The description matches the docs/CI template well, includes the change summary and testing, and the unused checklist sections were omitted appropriately.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/mkdocs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/stylesheets/gladia.css (1)

31-33: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Use lowercase for unquoted font family names.

Static analysis tools flag BlinkMacSystemFont, Helvetica, and Arial because standard CSS conventions prefer lowercase for unquoted font keywords to avoid case-sensitivity issues in certain parsers.

♻️ Proposed fix
-  --gladia-font-sans: "Suisse Intl", -apple-system, BlinkMacSystemFont, "Segoe UI",
-    Helvetica, Arial, sans-serif;
+  --gladia-font-sans: "Suisse Intl", -apple-system, blinkmacsystemfont, "Segoe UI",
+    helvetica, arial, sans-serif;
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/stylesheets/gladia.css` around lines 31 - 33, Update the
--gladia-font-sans font stack to use lowercase for the unquoted family names
BlinkMacSystemFont, Helvetica, and Arial, while preserving the existing font
order and quoted names.

Source: Linters/SAST tools

docs/contributing/index.md (1)

25-29: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use strict mode for the documented MkDocs validation command.

At Line 28, change uv run mkdocs build to uv run mkdocs build --strict so contributors locally validate the same broken-link and configuration constraints required by this PR.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/contributing/index.md` around lines 25 - 29, Update the documented
MkDocs validation command in the contributing instructions from “uv run mkdocs
build” to use the “--strict” option, ensuring local builds enforce the same
broken-link and configuration checks.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/docs.yml:
- Around line 17-20: Restrict workflow-level permissions to contents: read, then
add pages: write and id-token: write under the deploy job’s permissions. Leave
the build job without these elevated permissions while preserving the deploy
job’s required access.

---

Nitpick comments:
In `@docs/contributing/index.md`:
- Around line 25-29: Update the documented MkDocs validation command in the
contributing instructions from “uv run mkdocs build” to use the “--strict”
option, ensuring local builds enforce the same broken-link and configuration
checks.

In `@docs/stylesheets/gladia.css`:
- Around line 31-33: Update the --gladia-font-sans font stack to use lowercase
for the unquoted family names BlinkMacSystemFont, Helvetica, and Arial, while
preserving the existing font order and quoted names.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 617da605-67f8-4fc5-be9b-3628d10f8622

📥 Commits

Reviewing files that changed from the base of the PR and between 824db67 and 0960808.

⛔ Files ignored due to path filters (5)
  • docs/assets/favicon.svg is excluded by !**/*.svg
  • docs/assets/fonts/GeistMono-Regular.woff2 is excluded by !**/*.woff2
  • docs/assets/logo.svg is excluded by !**/*.svg
  • docs/assets/symbol.svg is excluded by !**/*.svg
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (22)
  • .github/workflows/ci.yml
  • .github/workflows/docs.yml
  • .gitignore
  • AGENTS.md
  • CONTRIBUTING.md
  • README.md
  • docs/concepts.md
  • docs/contributing/guide.md
  • docs/contributing/index.md
  • docs/getting-started.md
  • docs/index.md
  • docs/languages.md
  • docs/presets.md
  • docs/reference/steps.md
  • docs/stylesheets/gladia.css
  • docs/usage/cli.md
  • docs/usage/python.md
  • mkdocs.yml
  • overrides/main.html
  • overrides/partials/logo.html
  • pyproject.toml
  • scripts/generate_step_docs.py

Comment thread .github/workflows/docs.yml Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant