gacela-project/gacela-project.com/ship-it

Shipping

main is production: a merge deploys, with no staging and no manual gate. Verify before the merge.

1. Mechanical check

npm run check

It runs what CI runs: typecheck, vitest run, build, lint:links. On failure, read the output; do not rerun hoping it passes.

2. Look at the site

npm run preview, then open the changed page, the home page and one docs page, in light and dark, desktop and narrow. Hard refresh. Look at the site, not the diff.

3. What tooling misses

• Content. Verify docs code samples against ../gacela/src; the framework is the source of truth.
• URLs. A changed URL needs a redirect in site.config.ts.
• Weight. If you added assets, scripts or fonts, compare dist/ sizes with the previous build.
• No JavaScript. Disable it and reload; first paint must be correct.

4. Commit and PR

Commits are small and single-purpose; content and presentation go in separate commits. Format:

<area>: <what changed, imperative, lowercase>
 
<why, if not obvious from the diff>

Areas: docs, design, forge, ci, content, chore.

The PR says what changed, why and what you verified. Add screenshots of both themes when they answer the reviewer's first question.

5. After the merge

Watch the deploy workflow finish, then load the production URL and confirm the change is live.

Broken production

Revert first: git revert the merge commit, push to main, let the deploy roll back. Investigate afterwards.