-
Notifications
You must be signed in to change notification settings - Fork 113
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
[Tracking] Upgrade Docsy #123
Comments
Sounds good to me, thanks! |
Looks like this issue is completed ✅, is this correct @chalin? Thanks so much for upgrading the website! |
Hi @leonardpahlke - no, this is far from complete. What has been accomplished is to Reintroduce Docsy as a submodule #160, which is an essential first step, but Docsy has not be upgraded yet. Such an upgrade is a nontrivial undertaking given the numerous style and layout overrides that exist. I'm unsure if/when I'll have the time to look into this; it might not be until 24Q2. As I've mentioned elsewhere, it might be easier to start from the latest Docsy (0.8.0 as of the time of writing) and (re-)create the site style from this fresh new base. If there are any frontend designers willing to tackle that, I'd be willing to contribute my Docsy knowledge. |
Thanks for the insights @chalin ! |
Why upgrade Docsy?
The main reason is that the Bootstrap (BS) version used by this repo's Docsy theme (which dates back to 2020!), reached end-of-life last year, and so BS will not be receiving any more upgrades, not even security patches. Also, Docsy has receiving a lot of enhancements and fixes since 2020 -- in particular it no longer has recursive submodule dependencies!
Why this repo?
A number of TAG and other websites share the version of Docsy used in this repo. After discussion with @cjyabraham and @nate-double-u, we agreed that this repo might be a good candidate for exploring the Docsy upgrade. As I mentioned above, the local Docsy files are from Nov 2020, and have custom changes applied on top of that. It would be much better if an official release of Docsy was used instead, and if we moved any customization into repo-specific files (which is the recommended way of using Docsy).
Benefits
If / once the Docsy upgrade happens, this repo might be used to inspire & inform a CNCF website-starter template.
Impact?
My goal is to explore the Docsy upgrade in a way that is the least disruptive as possible, in particular, that the website will continue to auto-publish based on submitted content, and that there will be no other changes to the site's content or appearance1.
Comments?
Comment here if you have any questions or concerns. You can also reach out via the CNCF #techdocs channel.
/cc @caniszczyk @cjyabraham @nate-double-u @leonardpahlke
Prep & site rework
*.md
,*/*.md
, and website/content #169Tasks
Related
Footnotes
No change in appearance to anyone who isn't a fontend designer. Some minor changes in appearance are to be expected, since Bootstrap and FontAwesome have changed since 2020, with impacts on glyphs, font sizes, spacing, etc. ↩
The text was updated successfully, but these errors were encountered: