Web & Email
Domain Provider
Section titled “Domain Provider”We use internet.bs as our domain provider. It is configured to use Cloudflare as the authoritative nameserver (dig sustainablecapitolhill.org ns) for the sustainablecapitolhill.org domain. All DNS records live in Cloudflare. Login information is here.
We also own the chtl.org domain. All requests are handled by short.io, and are mostly redirects to specific pages in our sustainablecapitolhill.org site.
Cloudflare DNS
Section titled “Cloudflare DNS”We use Cloudflare as a DNS resolver, because they provide much better bot protection than the host for our website, sustainablecapitolhill.org. Login information is here.
Summary of Records
Section titled “Summary of Records”This may not be comprehensive. Use dig if you need specifics ;)
- A records for @ and www forward traffic to AWS, which hosts our Wordpress site. They use Cloudflare’s proxy service for caching and protection. Specifically, we have rules configured to issue a CAPTCHA-style challenge to anyone whose request matches one from which we frequently get bots that overload our web service. This does not prevent them from using our site, as long as they solve the CAPTCHA (and is often “invisible” to real users).
- MX records send email traffic to Google Workspace.
- DMARC, DKIM, and SPF records help with email security.
Wordpress Site (sustainablecapitolhill.org)
Section titled “Wordpress Site (sustainablecapitolhill.org)”Anyone with an SCH account can login to our main website by clicking “Login with Google” at https://sustainablecapitolhill.org/wp-admin. You will be granted “Author”-level access by default; check with the Marketing Committee if you need more access.
Wordpress is hosted on Cloudways. If you need to manage the web hosting, login using the account in the passwords sheet.
This wiki is constructed from a Google Docs folder in the Tool Library shared drive. It is implemented as a Astro Starlight website with a script that scrapes the folder, downloads each file as Markdown, and puts them into the correct directories.
The repository is stored on GitHub. A GitHub workflow automatically updates the wiki based on the folder every ~10 minutes, or you can also trigger the workflow manually here.