You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2026/02/09 18:53:00 UTC

[jira] [Created] (UNOMI-932) Modernize unomi.apache.org website for Unomi 3.0

Serge Huber created UNOMI-932:
---------------------------------

             Summary: Modernize unomi.apache.org website for Unomi 3.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
             Fix For: unomi-3.0.0


The current Apache Unomi website has several issues that make it difficult for new users to discover the project, understand its capabilities, and find the help they need:
 * Outdated framework and design — The site uses Bootstrap 4 and an aging visual design that doesn't reflect the maturity of a top-level Apache project. The site is not fully responsive on mobile devices.

 * Poor discoverability and navigation — Users frequently report difficulty finding documentation, community resources, and contact options. Key pages are buried or hard to reach.

 * No AI/modern positioning — The site doesn't communicate how Unomi fits into today's AI-first landscape, where CDPs serve as the data foundation for AI agents, LLMs, and real-time personalization engines.

 * Missing integrations visibility — There is no dedicated page showcasing products, platforms, and extensions built on Unomi, making it hard for potential adopters to see the ecosystem.

 * Outdated content — The tutorial page references Unomi 1.x/2.x. The testing guide contains placeholder TODOs and copy-pasted Apache Beam content. Team affiliations are stale. Several contribute pages have encoding issues.

 * No SEO or AI engine optimization — The site lacks structured data (JSON-LD), Open Graph tags, sitemaps, and AI-friendly metadata (llms.txt), limiting organic discoverability.

 * ASF compliance gaps — Video pages embed YouTube iframes directly (potential tracking concern per ASF web guidelines). Company listings are in fixed order rather than randomized.

 * Stale events and news — There is no consolidated view of recent project activity (releases, talks, articles) on the homepage.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)