-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port Website to Docsy Go module #5496
Comments
The part of this to watch for is whether we can cleanly override the docsy theme. If that part does not go smoothly, this could be a significant amount of front-end work. |
The author that ported docsy theme to a module here 😄. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle-frozen |
/lifecycle frozen |
Operator Framework sites are built with Hugo and the Docsy theme, which was previously versioned as a git submodule. We had to go pretty far outside of the accepted best practices to get our custom theme, and it has prevented us from migrating to newer versions of docsy.
Docsy is now available as a go module plugin to hugo instead, which should be significantly easier to upgrade.
Original discussion: google/docsy#535
Porting to module docs:
We will likely run into some trouble here, since we did so much beyond-best-practice stuff to override our custom theme. If we do, the best place ask questions here https://github.com/google/docsy/discussions/
The text was updated successfully, but these errors were encountered: