docs: update iqon plan status

This commit is contained in:
Sergei Vasilev
2026-05-21 08:55:00 +03:00
parent fb235b01da
commit 70a3b997ca
+5 -5
View File
@@ -3,7 +3,7 @@
Purpose: record the current state of the IQON remediation plan after backup, hardening, redirects, contact smoke, and retention decisions. Purpose: record the current state of the IQON remediation plan after backup, hardening, redirects, contact smoke, and retention decisions.
Created: 2026-05-20 Created: 2026-05-20
Updated: 2026-05-20 Updated: 2026-05-21
## Current decisions ## Current decisions
@@ -23,6 +23,7 @@ Updated: 2026-05-20
| SEO cleanup | Done | `og:site_name=IQON`, HTTPS URL rewrite, English redirects | | SEO cleanup | Done | `og:site_name=IQON`, HTTPS URL rewrite, English redirects |
| Contacts cleanup | Done | Contact page uses `office@iqon.com` and `@infobidgebot` | | Contacts cleanup | Done | Contact page uses `office@iqon.com` and `@infobidgebot` |
| Contact form smoke | Done | Form returned `sent=ok` success script | | Contact form smoke | Done | Form returned `sent=ok` success script |
| `www` redesign QA | Done | `scripts/iqon-phase1-verify.sh https://www.iqon.com` passed after skip-link fix |
| English-only redirects | Done | Sampled 301 rules passed | | English-only redirects | Done | Sampled 301 rules passed |
| DB archive creation | Done | Remote and local `gzip -t` passed | | DB archive creation | Done | Remote and local `gzip -t` passed |
| Encrypted local backup | Done | Decrypt-to-`gzip -t` passed; key stored in Vaultwarden | | Encrypted local backup | Done | Decrypt-to-`gzip -t` passed; key stored in Vaultwarden |
@@ -38,10 +39,9 @@ Updated: 2026-05-20
## Remaining optional work ## Remaining optional work
1. Confirm inbox delivery of the contact smoke email if mailbox access is needed. 1. Decide whether to retire WordPress later by taking a static snapshot of the old design.
2. Decide whether to retire WordPress later by taking a static snapshot of the old design. 2. Periodically re-run live health checks after DNS/hosting changes.
3. Periodically re-run live health checks after DNS/hosting changes. 3. Review old WordPress plugins/admin surface if deeper security hardening is desired.
4. Review old WordPress plugins/admin surface if deeper security hardening is desired.
## Baseline health commands ## Baseline health commands