[
https://issues.apache.org/jira/browse/GEODE-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021669#comment-18021669
]
Bryan Behrenshausen edited comment on GEODE-10468 at 9/21/25 3:00 PM:
----------------------------------------------------------------------
I would like to volunteer to assist with this work. I had [a website
improvement PR|https://github.com/apache/geode-site/pull/24] merged as part of
the 1.15.2 release cycle, but it isn't yet reflected in the production version
of the site.
I enjoy assisting with copyediting and site structure/organization challenges.
I also know enough HTML and CSS to be dangerous.
My initial suggestion for improving the website development experience would be
to lower potential barriers to participating in the work. Because I am not a
software developer, I had some initial difficulty understanding how I could get
started working on the site, which [appeared to
require|https://github.com/apache/geode-site?tab=readme-ov-file#locally-generate-the-site-framework-and-review-your-changes]
a local build environment, additional dependencies, and other resources that
made the prospect of pitching in feel a bit intimidating for a novice like me.
At any rate, it certainly seemed more complicated than working on websites of
other open source projects with which I've volunteered. So in the spirit of
modernization and revitalization, this is where I would suggest we begin
working.
was (Author: JIRAUSER310851):
I would like to volunteer to assist with this work. I had [a website
improvement PR|https://github.com/apache/geode-site/pull/24] merged as part of
the 1.15.2 release cycle, but it isn't yet reflected in the production version
of the site.
I enjoy assisting with copyediting and site structure/organization challenges.
I also know enough HTML and CSS to be dangerous.
My initial suggestion for improving the website development experience would be
to lower barrier to participating the work. Because I am not a software
developer, I had some initial difficulty understanding how I could get started
working on the site, which [appeared to
require|https://github.com/apache/geode-site?tab=readme-ov-file#locally-generate-the-site-framework-and-review-your-changes]
a local build environment, additional dependencies, and other resources that
made the prospect of pitching in feel a bit intimidating for a novice like me.
At any rate, it certainly seemed more complicated than working on websites of
other open source projects with which I've volunteered. So in the spirit of
modernization and revitalization, this is where I would suggest we begin
working.
> 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
> Priority: Major
>
> 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
(v8.20.10#820010)
