Development Workflow
Repositories
| Repository | URL | Purpose |
|---|---|---|
| id86-gp-theme | github.com/donnyaw/id86-gp-theme | Child theme source, CSS, JS, PHP |
| ID86-instant-documentation | github.com/donnyaw/ID86-instant-documentation | Reference content Markdown and sync tooling |
| brain-donnyaw-cf-pages | github.com/donnyaw/brain-donnyaw-cf-pages | This operational documentation |
| wp-ops | github.com/donnyaw/wp-ops | WordPress automation scripts and operations |
Theme Change Process
The full deploy sequence — local edits, php -l, git diff --check, ./deploy.sh, cache purging, and origin verification — lives in Theme Deployment. This page covers only the release discipline around it.
- Make changes only in child-theme files (never in GeneratePress parent).
- Stage only intended files.
- Write a concise commit message using conventional commits format.
- Push:
git push origin main
Git Safety Rules
- Never commit SMTP passwords, Reoon API keys, Cloudflare tokens, or private SSH keys.
- Do not commit
.envfiles or credential paths. - Check for secrets before staging:
git diff --cached | grep -i 'password\|secret\|key\|token'— if anything shows, unstage and fix. - Do not revert unrelated worktree changes.
- Do not amend or force-push unless explicitly requested by the user.
- Keep GeneratePress Element changes documented here because they live in the database, not in version control.
Commit Message Style
Use conventional commits:
feat: add email subscription bar above footer with Reoon verification
fix: correct mobile hero alignment for quick topics
docs(id86): publish site implementation guide
refactor: consolidate search palette renderer
perf: disable Perfmatters on front page for instant search
Deployment Tagging
When publishing documentation, use date-based tags:
git tag "id86.net-$(date +%Y%m%d-%H%M%S)"