-
Notifications
You must be signed in to change notification settings - Fork 7
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
Point GitHub pages to official domain #79
Comments
Another option: we could use stacksgov.com and set up similar subdomains for the github repos, and add a main landing page explaining what Stacks Community Governance is. |
This could be covered as part of the Governance Lab initiative, more info coming in the next month. |
This is complete, the GitHub pages config for the https://pm.stacksgov.com/ For now the base domain I'm hosting the domain through my personal Cloudflare account, if it makes sense to transfer this domain to another entity I am happy to do so, the GitHub configuration only requires a few DNS records. |
I would imagine either the Foundation (cc/ @wileyj) or some other community governed account might be better? |
I'm open to this! We've talked about it in a few past meetings and there was no action, so if we know where we want the domain go I'm happy to transfer it and help with the configuration. |
Instead of https://stacksgov.github.io/resources we should use https://resources.stacks.org as the main link to the content.
It was talked about in a few meetings and in Discord with no objection, but after trying to configure the CNAME record, we learned that at this time neither the community or the foundation has access to the DNS settings for stacks.org.
Once the settings are accessible, two things are required to make this change (in this order):
The CNAME file was created and later removed since it redirected to a non-existent location. It will need to be created again when we are ready to make this transition, and following that, all links should be updated to the new location.
The text was updated successfully, but these errors were encountered: