chore: purge iamgmb refs, add v3/architecture changelog

This commit is contained in:
root
2026-08-10 14:06:52 -04:00
parent 0bc671b965
commit edfd0f0b40
3 changed files with 49 additions and 36 deletions
+12 -12
View File
@@ -1,7 +1,7 @@
# VerdictTank Style Guide — Proposals & Mockups
Last updated: Aug 7, 2026
Applies to: All proposal pages (proposals.iamgmb.com) and all mockup pages (mockup.iamgmb.com/verdicttank/)
Last updated: Aug 10, 2026
Applies to: All proposal pages (proposals.itpropartner.com) and all mockup pages (mockups.itpropartner.com/verdicttank/)
---
@@ -11,13 +11,13 @@ Every project gets exactly two proposal URLs:
| Version | Description | URL Pattern | Behavior |
|---|---|---|---|
| **v1** | Original submission — frozen, never edited | `proposals.iamgmb.com/<project-slug>` | Yellow "SUPERSEDED" banner. Footer links to v2 + verdict. |
| **v2** | Post-pipeline rewrite — incorporates all review feedback | `proposals.iamgmb.com/<project-slug>-v2` or rebranded slug | Active proposal. Footer links to v1 + verdict + itself (bolded). |
| **v1** | Original submission — frozen, never edited | `proposals.itpropartner.com/<project-slug>` | Yellow "SUPERSEDED" banner. Footer links to v2 + verdict. |
| **v2** | Post-pipeline rewrite — incorporates all review feedback | `proposals.itpropartner.com/<project-slug>-v2` or rebranded slug | Active proposal. Footer links to v1 + verdict + itself (bolded). |
**Rules:**
- v1 is immutable after submission. Do not edit it — only add the superseded banner.
- v2 is created fresh after the pipeline runs. It is a full rewrite, not a diff.
- The pipeline verdict itself lives at `mockup.iamgmb.com/<project>/critical-review.html`.
- The pipeline verdict itself lives at `mockups.itpropartner.com/<project>/critical-review.html`.
---
@@ -29,9 +29,9 @@ Every proposal and every mockup page MUST have exactly this footer (updating the
<footer>
<p><strong>PROJECT NAME</strong> — a product of IT Pro Partner</p>
<p style="margin-top:0.5rem;">
<a href="https://proposals.iamgmb.com/PROJECT-V1-SLUG">Original Proposal (v1)</a> ·
<a href="https://mockup.iamgmb.com/PROJECT/critical-review.html">Pipeline Verdict</a> ·
<a href="https://proposals.iamgmb.com/PROJECT-V2-SLUG" style="font-weight:700;">Post-Review Proposal (v2)</a> ·
<a href="https://proposals.itpropartner.com/PROJECT-V1-SLUG">Original Proposal (v1)</a> ·
<a href="https://mockups.itpropartner.com/PROJECT/critical-review.html">Pipeline Verdict</a> ·
<a href="https://proposals.itpropartner.com/PROJECT-V2-SLUG" style="font-weight:700;">Post-Review Proposal (v2)</a> ·
<a href="https://itpropartner.com">IT Pro Partner</a>
</p>
</footer>
@@ -167,7 +167,7 @@ Footer divider: border-top: 1px solid var(--border)
```html
<div class="superseded-banner">
⚠ SUPERSEDED — This is the original proposal (v1) as submitted.
<a href="https://proposals.iamgmb.com/PROJECT-V2-SLUG">Read the post-review proposal (v2) →</a>
<a href="https://proposals.itpropartner.com/PROJECT-V2-SLUG">Read the post-review proposal (v2) →</a>
</div>
```
@@ -224,14 +224,14 @@ function toggleTheme() {
When starting a new proposal project:
- [ ] Create v1 proposal at `proposals.iamgmb.com/<slug>`
- [ ] Create v1 proposal at `proposals.itpropartner.com/<slug>`
- [ ] Submit v1 through the VerdictTank pipeline
- [ ] Save verdict as `mockup.iamgmb.com/<project>/critical-review.html`
- [ ] Save verdict as `mockups.itpropartner.com/<project>/critical-review.html`
- [ ] Create v2 proposal incorporating all pipeline feedback
- [ ] Add superseded banner to v1, linking to v2
- [ ] Apply standard footer to v1, v2, and ALL mockup pages
- [ ] Bold the "current" version link in each footer
- [ ] Create landing mockup at `mockup.iamgmb.com/<project>/`
- [ ] Create landing mockup at `mockups.itpropartner.com/<project>/`
- [ ] Ensure light/dark theme toggle on mockup
- [ ] Push all changes to Gitea
- [ ] 644 permissions on all web-facing files