Thanks for moving this discussion of website modernization along, Jinwoo.
Could you say a little more about how the work you're proposing relates to the
work Patrick has already coordinated [^1]? His renovation to the Geode project
website [^2] was (last time I checked) rather far along, and it incorporated
many updates and enhancements that I believe are also part and parcel of what
you're proposing in your PR (re-establishing the project on a modern website
generator, etc.). I know I was personally able to help address issues related
to branding, re-write page copy, code new page styles, propose a new site
content architecture, etc. I just need to know whether I should expect to be
porting the work in these commits [^3] to a new working branch so it does not
get lost.
Thanks,
Bryan
-----
[^1]: https://lists.apache.org/thread/69fwz35sxpsw1c2hp3t4hgsn38h4sxhd
[^2]: https://github.com/harmoncoffee/geode-site/tree/GEODE-10468
[^3]: https://github.com/harmoncoffee/geode-site/commits/GEODE-10468/
On 2026-09-13 3:44 PM, Jinwoo Hwang via dev wrote:
> Hello Apache Geode Community,
>
> I'd like the community's review and the PMC's approval for GEODE-10650,
which moves the Apache Geode website to the build system ASF Infrastructure
currently recommends.
>
> PR: https://github.com/apache/geode-site/pull/30
>
> This is intentionally nothing fancy. Our site still runs on roughly
10-year-old tooling: a nanoc build in Docker, driven by Gradle, with a 2016
Bootstrap 3 template. Over time, updates such as the 2.0.0 release were made
by hand directly on the asf-site branch, so the source and the live site have
drifted apart. This PR brings us in line with the current ASF standard, the
Infrastructure Pelican GitHub Action. It adds no new features.
>
> What changes:
>
> -Pushes to master build and publish the site automatically; pull requests
are built as a check.
> -Pages are plain Markdown, and releases are listed in a single YAML file,
so updating the site after a release is a small PR.
> -A simple, responsive theme in the Geode logo colors, with all assets
hosted on our own site.
> -Existing URLs keep working: user guides, API docs, XML schemas and
redirects are all preserved.
>
> This is meant as a clean, maintainable foundation rather than a finished
design. Everyone is encouraged to improve it further, whether that's content,
layout, or docs. Each change is now just a Markdown or template PR.
>
> Please review the PR and reply with your feedback, or a +1 if you're
comfortable with it. I'll merge once at least one PMC member has approved and
no one has raised objections after one week.
>
>
> Best regards,
> Jinwoo Hwang (he/him/his)
> SAS® Research and Development
> http://JinwooHwang.com<http://jinwoohwang.com/>
