Version Control

aerialps.com

Git + GitHub - private repository with full commit history. Every change is documented and reversible.

cms.aerialps.com

WordPress Backups - manual backups via cPanel. Must be taken regularly to prevent data loss.

---

aerialps.com - Git + GitHub

The full codebase is in a private GitHub repository. Every change is committed with a descriptive message. In the event of a broken deployment, any previous working state can be restored immediately.

Commit type conventions

All commits must be prefixed with one of the following types:

docs:

Documentation updates.

feat:

New features.

chore:

Non-feature changes - text edits, dependency bumps, minor updates.

fix:

Bug fixes.

seo:

SEO and marketing changes.

Commits may combine types where appropriate - e.g. feat/seo: for a new page with SEO metadata.

Tip

Use git log with a specific commit hash to understand the full context of any past change. Every version has been documented in as much detail as possible.

---

cms.aerialps.com - WordPress Backups

WordPress does not use Git. Version control here means regular backups through the WordPress backup tooling in cPanel.

Danger

Backups must be taken regularly and consistently, even if it feels tedious. There is no automated recovery if the backup is stale.

What backups protect against

• Accidental post or page deletion
• Plugin conflicts breaking the admin panel
• Hosting provider failures
• Corrupted database entries

Recommendation

Take a backup before any major change - new plugin, theme update, or config edit - and on a scheduled cadence regardless of activity.