On 2026-09-14 10:46 AM, Jinwoo Hwang via dev wrote:
> Thank you for raising this, and especially for all the work that has
already gone into the website effort. I appreciate the time and thought that
you, Patrick, and others have invested in improving the site.
>
> My proposal is not intended to replace or compete with that work. The main
goal is simply to move us onto the architecture and publishing workflow
currently recommended by ASF Infrastructure so that we have a maintainable,
supported foundation.
>
> I view this as a practical interim solution rather than a final
destination. The intent is to give the project something simple, easy to
maintain, and aligned with current ASF recommendations while the community
continues discussing and developing a longer term vision for the website.
>
> When the current effort is ready to publish, I would very much welcome the
community's input on direction, design, content, and how best to incorporate
the work that has already been done. I certainly do not want valuable
contributions to be lost, and I think the community should help decide what
the eventual website should look like.
>
> Thank you again for bringing this up and for all of your contributions to
the project.
Thanks, Jinwoo, for this context! It's helpful.
I agree that getting the website ported to a modern, ASF-approved foundation
is paramount [^1]. The ASF has three approved templates that comply with ASF
policy for project websites [^1]. Your solution uses the Pelican-based
template; Patrick's uses the Docusaurus-based template. The work we've done
over the past few months is optimized for the Docusaurus version.
Your proposal gives me the sense that there is sufficient urgency to publish a
modern version of the Geode project website sooner rather than later. If that
is indeed the case, I would rather cast my (non-binding) vote for merging the
work we've already done on the Docusaurus-based renovation.
The new project website available in Patrick's GEODE-10468 branch [^3] is
already quite far along. In fact, I believe we have a complete site redesign
ready to launch. What's holding this back is the concomitant refresh of the
Geode project documentation.
As Patrick discusses in his most recent update [^4], the proposed renovation
relocates project documentation. The relocation breaks some of the internal
hyperlinks in that documentation (i.e., links from one page to another no
longer go where they used to go!). Patrick's goal was to fix these links
before launching the new website. However, the work has proven difficult. It
involves checking and fixing a *significant* number of broken or malformed
hyperlinks. I'm proud of the work he and I were able to do clearing up a good
chunk of those broken links. More remain.
Perhaps one solution here, then, is to review and merged what's already staged
in Patrick's working branch, broken links and all, and at least get the core
of a new site into production. By doing this, we open up the link-fixing work
to the entire community, which would help it proceed so much quicker than it
currently can.
This is the path I would vote to take. But I am interested in hearing
Patrick's thoughts, too.
Bryan
-----
[^1]: https://issues.apache.org/jira/browse/GEODE-10485
[^2]: https://github.com/apache/apache-website-template
[^3]: https://github.com/harmoncoffee/geode-site/tree/GEODE-10468
[^4]: https://lists.apache.org/thread/69fwz35sxpsw1c2hp3t4hgsn38h4sxhd
