-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor the site to use Docusaurus #9
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
base: main
Are you sure you want to change the base?
Conversation
Deploying openinfrastructure-github-io with
|
Latest commit: |
9489b7a
|
Status: | ✅ Deploy successful! |
Preview URL: | https://79ca467b.openinfrastructure-github-io.pages.dev |
1d293fe
to
545ad15
Compare
PROBLEM: The existing site is using out of date versions of Docsy and Hugo. We need to either upgrade those components, or use the time to switch to a different static site generator. SOLUTION: Use Docusaurus. Jeff has had a good experience using it with Holos, so let's use the opportunity to switch the site to Docusaurus. This commit refactors the existing site content to use Docusaurus with the following details: Removed the Logo blog as it really doesn't serve us well. Used undraw.co SVG graphics on the landing page. Removed "Google Partners" because evidently we aren't anymore. Setup redirects to the existing site URLs so Google won't complain. OUTCOME: Our existing site content, but on a different static site generation platform, and one that is easy for us to update.
3289211
to
6d48d71
Compare
I updated the temporary package name to the name of our repo.
NOTE: Before we merge this we would need to:
Right now I've been using https://openinfrastructure-github-io.pages.dev/ which is mapped to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want to commit yarn.lock
as part of this. Doing so should help to prevent the "everything broke when we built the site a year from now" problem that we hit with Hugo. Right?
We're using |
The previous README was the canned version using `yarn` to install, build, and deploy the site. We're using `npm` to build and deploy the site with Cloudflare, so I've updated the README to include the `npm`-specific instructions.
PROBLEM: On the autogenerated index pages (/services and /technical), the descriptions of the pages represented by the cards were being truncated. SOLUTION: Update the CSS to disable truncation. OUTCOME: Full descriptions are available on the autogenerated index pages for each referenced child pageD.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, and everything works on the preview site: https://79ca467b.openinfrastructure-github-io.pages.dev/
🚢 it
PROBLEM:
The existing site is using out of date versions of Docsy and Hugo. We need to either upgrade those components, or use the time to switch to a different static site generator.
SOLUTION:
Use Docusaurus. Jeff has had a good experience using it with Holos, so let's use the opportunity to switch the site to Docusaurus.
This commit refactors the existing site content to use Docusaurus with the following details:
OUTCOME:
Our existing site content, but on a different static site generation platform, and one that is easy for us to update.