[
https://issues.apache.org/jira/browse/UNOMI-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-932:
------------------------------
Fix Version/s: unomi-site-3.1.0
(was: unomi-3.1.0)
> unomi.apache.org: Unomi 3 major release story (homepage, Blog, 3.1.0)
> ---------------------------------------------------------------------
>
> Key: UNOMI-932
> URL: https://issues.apache.org/jira/browse/UNOMI-932
> Project: Apache Unomi
> Issue Type: Improvement
> Components: unomi-site
> Affects Versions: unomi-3.0.0
> Reporter: Serge Huber
> Assignee: Serge Huber
> Priority: Major
> Fix For: unomi-site-3.1.0
>
>
> h2. Summary
> Track website work for [https://unomi.apache.org/] so Apache Unomi 3 is
> presented as one major release (3.0 foundation + 3.1 product leap), with
> current stable *3.1.0* after GA.
> *Component:* unomi-site
> *Working branch:* {{UNOMI-932-unomi3-major-release-story}} on
> [https://github.com/apache/unomi-site]
> ----
> h2. Phase A — Website modernization (DONE)
> Landed on {{master}} via PR [#40|#40]. Addresses the original modernization
> goals:
> * Bootstrap 5 + design system, responsive layout
> * Discoverability / navigation improvements
> * AI/CDP positioning, integrations page, SEO (JSON-LD, Open Graph, sitemap,
> llms.txt)
> * ASF compliance (self-hosted assets / CSP, randomized ecosystem order, video
> privacy)
> * Content cleanup (tutorials, contribute, team, news/events)
> * Follow-ups: PR [#42|#42] trademark/footer; branch-protection ruleset
> Original problem statement (for history): outdated Bootstrap 4 design, poor
> nav, missing AI/integrations story, stale content, weak SEO/AEO, ASF
> compliance gaps, stale news.
> ----
> h2. Phase B — Unomi 3 major release story (IN PROGRESS)
> Ship homepage + Blog + download messaging for Unomi 3 / 3.1.0 GA.
> h3. Scope
> * *Homepage:* lead with *Apache Unomi 3* (not a narrow "3.1 features" frame);
> pin download / Docker to *3.1.0* at GA
> * *Blog (or News) section:* Unomi 3 series (intro, platform, multi-tenancy,
> OpenSearch/ops, migrating/V2 compat, contributors, unit-test harness, short
> 3.1.0 GA note)
> * *Diagrams:* animated SVG + Mermaid (match existing site patterns: brand
> tokens, {{mermaid: true}}, {{<pre class="mermaid">}}) — journey, API
> stability/V2 compat, unit harness vs ITs, multi-tenancy
> * *Proof points:* test vs impl investment; OpenAPI *119/119* path retention +
> V2 compatibility mode; unit harness ({{InMemoryPersistenceServiceImpl}})
> * *Community:* ASF-safe credits — Serge Huber (*Inoyu*) spotlight; Jérôme /
> Jonathan / François (*Jahia*); no vendor co-ownership of the product hero
> * *Download / get-started / structured data:* refresh version strings and
> featureList (OpenSearch supported, etc.)
> h3. Out of scope for this ticket (unless needed)
> * Manual AsciiDoc PlantUML changes (product doc) — separate if required
> * Ecosystem vendor landing pages beyond credit/Integrations norms
> ----
> h2. Acceptance (Phase B)
> * Homepage + key pages tell the Unomi 3 major story with regenerated stats at
> 3.1.0 GA
> * Blog posts published (or Blog index with first posts)
> * Diagrams live on homepage and key posts
> * Download / Docker / "current stable" consistent with 3.1.0
> * ASF trademark / no "Unomi 3 by <vendor>" language
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
