Skip to content

post: Great Docs (Ten Great Things We Added to Great Docs)#238

Open
rich-iannone wants to merge 6 commits into
mainfrom
post-great-docs-ten-releases
Open

post: Great Docs (Ten Great Things We Added to Great Docs)#238
rich-iannone wants to merge 6 commits into
mainfrom
post-great-docs-ten-releases

Conversation

@rich-iannone
Copy link
Copy Markdown
Member

@rich-iannone rich-iannone commented May 11, 2026

Adds the "Ten Great Things We Added to Great Docs" blog post at content/blog/great-docs-ten-things/. The post surveys ten features shipped across ten releases of Great Docs (v0.1 through v0.10.0), one highlight per release, tracing the project's evolution from a fairly simple docs generator into a more comprehensive platform for Python package documentation.

The post covers auto-discovery, SEO and proofreading, documentation linting, internationalization, keyboard navigation, page tags and status badges, scale-to-fit, versioned documentation, color swatches, and table previews/explorer. It includes several screenshots demonstrating features in context, links to some relevant User Guide pages, and a closing invitation for readers to submit feature ideas. Reading time is around 10 minutes.

Test plan

  • Post renders correctly on the Netlify preview (hero image, all nine screenshots, code chunks)
  • Post appears at the top of /blog/ with the correct title, thumbnail, and description
  • The software: great-docs tag in frontmatter resolves to the Great Docs software page
  • All external links resolve (Great Docs site, User Guide pages, PyPI, GitHub issues)
  • validate-blog-posts.py CI check passes

TODO (later PR)

  • Add great-docs software entry with description and logo

@github-actions
Copy link
Copy Markdown

Publishing checklist

  • Get a review — request at least one reviewer on this PR
  • Check your post — once the deploy preview is ready, a comment will appear with direct links to your post
  • Check the blog listing — confirm your post appears with the correct title, image, and description
  • Merge — once everything looks good and you have an approving review, merge to main

@netlify
Copy link
Copy Markdown

netlify Bot commented May 11, 2026

Deploy Preview for posit-open-source canceled.

Name Link
🔨 Latest commit 79914bd
🔍 Latest deploy log https://app.netlify.com/projects/posit-open-source/deploys/6a01f16f4a66ee0008a3899d

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 11, 2026

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 11, 2026

@github-actions
Copy link
Copy Markdown

Blog YAML Checks

✅ All 1 posts passed.

@rich-iannone rich-iannone requested a review from t-kalinowski May 11, 2026 15:20
@rich-iannone rich-iannone marked this pull request as ready for review May 11, 2026 15:26
Copy link
Copy Markdown
Member

@t-kalinowski t-kalinowski left a comment

Choose a reason for hiding this comment

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

Looks great!


The practical consequence is that you don't have to enumerate your exports by hand. If you add a new class or function to your package, the next build picks it up. If you remove something, it disappears from the site. The configuration file exists so you can reorder sections, add display names, or exclude internal symbols, but the default is complete and correct without any having to do any manual intervention.

I suppose this was the design decision that everything else built on: if Great Docs can figure something out automatically, it should, and configuration should be for expressing preferences rather than providing information that we could have inferred.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
I suppose this was the design decision that everything else built on: if Great Docs can figure something out automatically, it should, and configuration should be for expressing preferences rather than providing information that we could have inferred.
This was the design decision that everything else built on: if Great Docs can figure something out automatically, it should, and configuration should be for expressing preferences rather than providing information that we could have inferred.

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.

2 participants