Project Tags – Pre‑deployment Phase (Creative Journalism × Geo‑targeted Humour × AI Infrastructure)
Use these tags to label commits, issues, wiki pages and deployment artefacts in the initial pre‑deployment phase, with explicit “leverage” intent for underperforming agents, elements and HR dinosaurs.[elxw.fa.em3.oraclecloud]

---

1. Narrative and tone tags

• #AutumnLeaf – Seasonal, gentle refactoring: small, visible changes that signal transition without shock.
• #LowMaintenanceSweetheart – Deliberate minimalism: low‑ops, low‑drama, low‑surprise infrastructure.
• #CreativeJournalism – Story‑first documentation: short, readable, slightly irreverent write‑ups that double as internal comms and external PR.
• #GeoTargetedHumour – Location‑aware jokes and examples (e.g. Edinburgh, South Gran Canaria) used to humanise policy and nudge behaviour.

These four tags frame the style of work: calm, funny, local, and deliberately boring in a good way.

---

2. Infrastructure and compute tags

• #Titan – Mid‑scale compute and tooling: codegen, testing, CI/CD, and AI‑assisted refactors that run on “Titan‑class” resources.
• #Colossus – Heavy‑lift experiments: large‑scale analysis, A/B testing of guidance, and surge simulations that need Colossus‑level capacity.
• #KnowledgeBase – Structured, versioned repository of guidance, ethics notes, data schemas and decision logs.
• #Wiki – Human‑editable layer: discussion pages, meeting notes, and “living protocol” docs that feed into the KnowledgeBase.

Use #Titan for routine automation and #Colossus when you explicitly model strategic surges (e.g. assessment periods, policy announcements).[elxw.fa.em3.oraclecloud]

---

3. Deployment surface tags

• #WordPress – WordPress theme / plugin work: templates, blocks, custom post types, and editorial workflows.
• #Drupal – Drupal theme / module work: content types, views, permissions, and role‑based access aligned to School/University structures.
• #PWA – Progressive Web App work: manifest, service worker, offline caching, install prompts and mobile‑first UX.

Each deployment target should carry at least one of these tags plus a narrative tag (e.g. #WordPress #LowMaintenanceSweetheart).

---

4. Values and standards tags

• #Accessibility – WCAG, ARIA, language level, colour contrast, keyboard navigation, and plain‑English summaries.
• #OpenStandards – JSON APIs, open formats, interoperability between WordPress, Drupal and PWA, and avoidance of proprietary lock‑in.
• #DigitalHumanities – Explicit framing of the project as DH work: critical reflection on AI, translation tools, community and landscape.[elxw.fa.em3.oraclecloud]

These tags ensure that even “funny” or “lightweight” work remains ethically and technically serious.

---

5. Example tag combinations (pre‑deployment)

Use compound tags to signal intent and leverage:

• #AutumnLeaf #WordPress #Accessibility – Small, visible UI tweaks in the WordPress theme that improve accessibility.
• #LowMaintenanceSweetheart #PWA #OpenStandards – Minimal PWA shell with clean, standard APIs and offline guidance.
• #CreativeJournalism #Wiki #DigitalHumanities – Short, story‑style wiki pages explaining the project’s DH angle and ethical stance.
• #GeoTargetedHumour #Drupal #KnowledgeBase – Humorous, location‑aware examples in Drupal content types that feed into the structured KnowledgeBase.
• #Titan #WordPress #LowMaintenanceSweetheart – AI‑assisted refactors of the WordPress theme to reduce complexity and ops load.
• #Colossus #PWA #CreativeJournalism – Large‑scale simulation of traffic surges and narrative interventions on the PWA front‑end.

You can formalise these as a small “tag policy” in your wiki: every pre‑deployment task gets 2–4 tags, at least one narrative, one infra/compute, and one surface or values tag. This makes it easy to filter by “funny but serious”, “heavy compute”, or “low‑maintenance” work and gives you a clear, lightly satirical but functional taxonomy for the project.[elxw.fa.em3.oraclecloud]