-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(docs): build docs in CI and deploy to gh pages #849
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
Conversation
| 📖 <br /> `doc` | Documentation | Links to commits by the user on this project, Wiki, or other source of documentation | ||
| 🎨 <br /> `design` | Design | Links to the logo/iconography/visual design/etc. | ||
| 💡 <br /> `example` | Examples | Links to the examples | ||
| Emoji/Type | Represents | Comments | |
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.
The linter was failing because of the missing closing table tags.
website/siteConfig.js
Outdated
| // For deploy | ||
| url: 'https://allcontributors.org', | ||
| baseUrl: '/', | ||
| url: 'https://leahwasser.com', |
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.
obviously we would update this. but you can see this live at
https://www.leahwasser.com/all-contributors
note: the docs link at the top is broken but easily fixed. Right now, it's a hard link, and I'm not sure why that entire index page is pure HTML. but easy to update and fix once we decide this is the path we want to go down.
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.
It would be worth adding a TODO comment so one of us can remember to update that when needed.
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.
@Berkmann18 rather than merging this as is, what i'd like to do here is get this running on github pages here in this repo! So the url would be all-contributors.github.io . To do that, i need access to the settings in this repo or I need someone else to set that up for us so we can get the website online again. Below is what i see when i go to settings in this repo.
Could you help with that? Either give me permissions to do it OR you could set it up if you are uncomfortable with giving me permissions (which i understand!)
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 have access now so please ignore the above!! This pr however is ready to merge WHEN everyone is happy with it!!
| type="image/png" | ||
| sizes="16x16" | ||
| href="/img/icons/favicon-16x16.png" | ||
| href="img/icons/favicon-16x16.png" |
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.
This entire page is pure html which surprised me! we probably want to consider a markdown version in the future but for now - html it is.
docs/project/contribute.md
Outdated
|
|
||
| `node -v` | ||
|
|
||
| If you don't have atleast version `.18` or higher, please install node or upgrade your current version. |
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.
If this is for the Node version, v24 should be the oldest to accept, as it's the current LTS version. v18 has been out of support for several years.
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.
Definitely. The entire docs website is out of date with a lot of deprecated dependencies. I will test this locally and then update!! Great catch!
docs/project/contribute.md
Outdated
|
|
||
| If you don't have atleast version `.18` or higher, please install node or upgrade your current version. | ||
|
|
||
| Install the newest (deprecated) version of Docusaurus: |
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.
Do they not have an undeprecated version?
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.
They do. Can you please have a look as this open issue . Essentially if we want to move the entire site to the newest version, we will need to update the structure of the documentation. This structure will impact crowdin's setup. We are 2 versions behind on these docs. SO I think because I don't have access to crowdin beyond adding translations I don't want to break translations until we know we have full admin access to platforms (or we have a plan in place to migrate translations.
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.
Update - thank you for giving me access to crowdin! we can now figure out how to sync github pages with translation content and also setup github pages 🚀 I suggest still that we get the site live as is FIRST and then we migrate to Docusaurus 3.x and update all deps at that time!!
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.
Yeah, getting it working then migrating to a later version of Docusaurus is a good plan.
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.
Ok perfect. I also saw the updates you made to the pr title. I'll read a bit more about angular / conventional commits as well.
website/siteConfig.js
Outdated
| // For deploy | ||
| url: 'https://allcontributors.org', | ||
| baseUrl: '/', | ||
| url: 'https://leahwasser.com', |
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.
It would be worth adding a TODO comment so one of us can remember to update that when needed.
website/siteConfig.js
Outdated
| baseUrl: '/all-contributors/', | ||
| projectName: 'all-contributors', | ||
| organizationName: 'all-contributors', | ||
| organizationName: 'lwasser', |
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.
Ditto about leaving a TODO (especially useful for those who have TODO extensions that highlight those comments).
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.
Definitely. Please see comment above - i proposal we get the homepage online via github pages so i'd make this all-contributors before merging if we do that! This pr will allow us to get that home page online with those changes once we setup things up in the settings of this repo.
|
Ok i've updated this so it should build on github pages and responded to all review comments. @Berkmann18 please have a look when you have a moment. |
|
Ok great - just fixed a merge conflict. This pr is ready for another review @Berkmann18 !! 🚀 |
|
Thanks for the review and approval @Berkmann18 i'll merge this and we can see how github pages goes |

closes #835
What:
Right now the all contributors.org website is down. Using GitHub Pages will allow us to deploy the website to GitHub Pages. When we have control of the domain, we can migrate the DNS to GitHub Pages. This pr is partially working. What doesn't work right now is the links to the docs page - this is because i need some input on how translations work. But I wanted folks to see that moving to GitHub Pages is straightforward and could make maintenance easier.
Why:
I just set up GitHub Pages deploy via a CI action. We will need to adjust the settings and such for this to all work correctly. Then we'd want to setup security for the domain when we have access to it so people can't steal subdomains and use them for bad things... 🙃 sadly this happens.
How:
Checklist:
Bot Usage