Frequently Asked Questions

General

Q: What is the acronym ASHC? A: ASHC stands for Awesome Static Hosting and CMS — a curated directory of static hosting providers and content management systems compatible with static site generators.

Q: How is ASHC maintained? A: ASHC is community-maintained. Every entry in the directory is backed by a GitHub issue for open discussion and review.

Q: Who can contribute? A: Anyone! All additions and removals are proposed through GitHub issues and reviewed by the community via a voting process.

Contributing

Q: How do I propose adding a new entry? A: Open a GitHub issue using the appropriate issue template ("Add: Hosting Provider" or "Add: CMS"). You'll need to provide the required justification bullets. See the Contributing page for the full process.

Q: How do I report a broken link or an outdated entry? A: Open a GitHub issue using the "Remove: Hosting Provider" or "Remove: CMS" template and provide evidence that the entry should be removed. See Removing from ASHC for details.

Q: What happens after I open an issue? A: The community votes using 👍/👎 reactions over a 30-day window. A maintainer then marks the issue as accepted or rejected and updates the label accordingly.

Q: Do I need to open a pull request when I propose an entry? A: Not immediately. Open an issue first. If the proposal is accepted, then open a PR to edit the appropriate TOML file (Hosting Providers.toml or Content Management Systems.toml).

The Directory

Q: What makes a good static hosting provider entry? A: The provider should be actively maintained, support deploying static sites, and be meaningfully different from existing entries in the directory.

Q: What makes a good CMS entry? A: The CMS should be actively maintained, work with static site generators, and offer something distinct from the tools already listed.

Q: Why are hosting providers and CMSs tracked separately? A: Their criteria for inclusion can differ, and keeping them separate allows the processes to evolve independently over time.