[
https://issues.apache.org/jira/browse/GEODE-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130293#comment-18130293
]
ASF GitHub Bot commented on GEODE-10468:
----------------------------------------
harmoncoffee commented on PR #31:
URL: https://github.com/apache/geode-site/pull/31#issuecomment-6341098529
@JinwooHwang Creating a ticket to mark that as a task we should definitely
do so that we can eventually get all broken links fixed. This is a goal we want
with the website.
Also regarding main vs master. Should we migrate to using the main branch
sometime soon? This would be in line with expectations from the wider
community. I could go and update this so it does not break the ci and we can
come back and update the branches
https://github.com/github/renaming
https://sfconservancy.org/news/2020/jun/23/gitbranchname/
> Modernization of Apache Geode Website - https://geode.apache.org/
> -----------------------------------------------------------------
>
> Key: GEODE-10468
> URL: https://issues.apache.org/jira/browse/GEODE-10468
> Project: Geode
> Issue Type: Improvement
> Reporter: Jinwoo Hwang
> Assignee: Nitin Lamba
> Priority: Major
> Labels: SAS
>
> As part of our ongoing efforts to improve the user experience and visual
> appeal of the Apache Geode website, we propose a comprehensive modernization
> initiative. The current design, while functional, reflects an older aesthetic
> that may not fully resonate with today’s developer and enterprise audiences.
> This task involves updating the website’s {*}color scheme{*}, {*}layout{*},
> and {*}overall visual hierarchy{*}, along with other enhancements aimed at
> improving accessibility, responsiveness, and brand alignment.
> ----
> h3. *Scope of Work:*
> * *Color Scheme Refresh:*
> Introduce a modern, accessible palette that aligns with Apache branding while
> improving readability and visual engagement.
> * *Layout Redesign:*
> Reorganize content structure for better navigation, mobile responsiveness,
> and intuitive user flow. Consider grid-based layouts and modular components
> for scalability.
> * *Typography & Iconography:*
> Update fonts and icons to reflect a clean, contemporary style that enhances
> clarity and professionalism.
> * *Accessibility Improvements:*
> Ensure compliance with WCAG standards for contrast, keyboard navigation, and
> screen reader compatibility.
> * *Performance Optimization:*
> Review and refactor front-end assets to improve load times and responsiveness
> across devices.
> * *Content Presentation:*
> Enhance the way documentation, community links, and release notes are
> displayed to improve discoverability and engagement.
> ----
> h3. *Goals & Benefits:*
> * Improve first impressions for new users and contributors.
> * Enhance usability across devices and screen sizes.
> * Align visual identity with modern open-source standards.
> * Foster greater community engagement through a more inviting interface.
> ----
> h3. *Suggested Tools/Technologies:*
> * HTML5, CSS3 (with SCSS or Tailwind)
> * JavaScript (React or Vue if feasible)
> * Static site generators (e.g., Hugo or Jekyll)
> * Accessibility testing tools (e.g., Axe, Lighthouse)
> ----
> h3. *Dependencies & Considerations:*
> * Coordination with PMC and community for design approvals.
> * Preservation of existing content and URLs to avoid SEO disruption.
> * Version control and staging environment for iterative testing.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
