Primary finding
Forks will publish a status page with wrong links/canonical URLs due to hardcoded upstream site/repo, contradicting “no extra config” claim
mediumdocs-gaphigh
- docs/status.md:15
- docs/_config.yml:4
- docs/_config.yml:13
- docs/_config.yml:51-52
The status page claims every fork gets a public dashboard with no extra config, but the site config hardcodes the original site URL and GitHub repo links. On forks or renames, canonical URLs and footer/social links will point to the upstream project, confusing users and undermining the claim of zero configuration. This is an actionable docs/config gap with concrete impact on published forks.
Recommendation
Make the Jekyll site fork-agnostic: - Use GitHub Pages metadata instead of hardcoded URLs: set url: "" and baseurl: "" and rely on the relative_url/absolute_url filters with site.github.url/baseurl, or explicitly set url: {{ site.github.url }} and baseurl: {{ site.github.baseurl }} via config defaults. - Replace hardcoded social_links user_url with {{ site.github.repository_url }} (or omit if the theme supports dynamic repo links). - Update the status page text to qualify that forks must enable GitHub Pages (and Actions) or remove the “no extra config” claim. These changes keep links and canonicals correct across forks and repo renames.