September 17 Update: GitHub pages docs are online 🎉

[lwasser]

Friends, we have a working documentation site!!!

https://all-contributors.github.io/

Please check it out. I do expect you to find some broken images and links, and we have an issue:
#912

Where I'm tracking each page that I've worked on, and where anyone else can volunteer to check and fix a page or two if you'd like to pitch in on a task that is relatively quick to work on (checking links and images on a page and fixing them if they are broken).

I also created development docs here:

https://all-contributors.github.io/project/development/

that help you understand the new astro site setup and features that we are using!!

[lwasser]

So I think we now need to decide what to do with our domain allcontributors.org

The site is working again - https://allcontributors.org/docs/en/overview
But the translations are not working.

My question (that we can maybe discuss tomorrow?) is, do we want to keep and pay for the domain moving forward? I think we should only ask Jake to redirect the domain once.

So we either ask that it gets redirected to GitHub Pages or to a new Netlify account. If I add a badge to our current site, we should be able to get an open source plan on Netlify and add several maintainers to it. I don't know enough about Netlify to decide whether it's worth the additional infrastructure or not! But I also don't have an opinion either way. ❤️

[JimMadge]

My preferences is to use the allcontributors.org domain.

• Looks more professional/trustworthy
• Useful for setting up mailboxes
• The URL will remain the same even if we move hosting providers (like we are doing right now 😆)

Have we asked Jake if he would be open to transferring the domain to someone else? DNS doesn't need changing much, but it feels really fragile to not have it in our control. I'm happy to ask about that, and would be willing to manage/pay for it.

[JimMadge]

My vote would be to go with Netlify. It's not perfect but I am familiar with it and the project is already (or, at least was) set up to use it, and it has some nice features like deployment previews for PRs and dynamics redirects (for translations).

Trying to think what is blocking us here, the existing Netlify team isn't part of the open source programme or a commercial tier, so we can't add more owners/admins. So, we could do the work to be part of the open source programme on that team. I think that might be difficult because we would be giving Jake a lot of work.

Alternatively, we could set up a new team and deploy the site with the badge there. I think there isn't much loss in doing that, because I suspect the existing team is only a single person.