projectcapsule / projectcapsule/website
Should `projectcapsule.dev` serve `main` or the latest release?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2
- Forks
- 21
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 12
Description
Proposal
Serve the latest release at projectcapsule.dev, and move main to main.projectcapsule.dev. This keeps the website on stable docs instead of unreleased main.
Mechanism: point the Netlify production branch at the latest release branch; main becomes a branch deploy on its own subdomain. The production branch is switched once per release. This could be handled automatically with an API token.
versions:
- version: v0.13 (latest)
url: https://projectcapsule.dev
- version: v0.12
url: https://release-0-12.projectcapsule.dev
- version: v0.11
url: https://release-0-11.projectcapsule.dev
- version: v0.10
url: https://release-0-10.projectcapsule.dev
- version: main
url: https://main.projectcapsule.dev
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Netlify production-branch and branch-deploy settings, then trace how release branches and the versions YAML are currently represented. Define completion as stable documentation at projectcapsule.dev, main at its subdomain, and release-specific URLs matching the proposal; the issue does not name repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100