Build & Test Docs Site with CI & HTML Proofer
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 41
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
I'm a big advocate for static docs sites and Hugo in particular (I'm a contributor). I see that this docs site is built with Hugo but not on CI.
I propose that this site gets built on CircleCI, this way PRs can be checked automatically before merging. There's a tool that I've used with Hugo and Jekyll-based websites called HTML Proofer that can test the generated static site for errors. My favorite usecase for it is to check for broken links though it can also check your HTML structure as well to make sure that well formed HTML pages are being generated.
A few examples of how this works:
Feliciano.Tech/config - my personal site, built with Hugo and tested with HTML Proofer
CircleCI Docs/config - CircleCI's documentation website, built with Jekyll and tested with HTML Proofer
Patheon Docs/config - Docs site for Pantheon Hosting, though they're using Gatsby instead of Hugo
I can get a PR going if this sounds good. Just wanted to ask/discuss first.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how this Hugo documentation site is currently built and whether the repository already has CI configuration. Review the referenced .circleci/config.yml examples, then determine how the generated site can be checked with HTML Proofer. Done means pull requests build the site automatically and report generated-site or broken-link errors before merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hugo
- Domain
- build-system, ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100