Hi Bryan, Thank you for your support and for the vote. I also appreciate you raising the question about Patrick's work and the broader website effort.
I want to emphasize that my intention is not to undermine, replace, or diminish the work that you, Patrick, and others have contributed. A great deal of thoughtful effort has already gone into this work, and I would very much like the community to preserve and build upon those contributions rather than set them aside. My goal with this proposal is simply to offer a practical and maintainable path forward for the website in its current state. I see the Pelican migration as an interim foundation that can help us move away from aging tooling, simplify ongoing maintenance, and make it easier for community members to contribute while longer-term plans continue to evolve. I also appreciate your perspective on the progress already made with the Docusaurus-based effort. If the community believes that work is sufficiently mature and ready to move forward, I would be happy to support a discussion around the best way to build on what has already been accomplished. Thank you again for your support and for helping move the discussion forward. Best regards, Jinwoo Hwang (he/him/his) SAS® Research and Development http://JinwooHwang.com<http://jinwoohwang.com/> From: Bryan G. Behrenshausen <[email protected]> Date: Monday, September 14, 2026 at 11:16 AM To: [email protected] <[email protected]> Cc: Jinwoo Hwang <[email protected]> Subject: Re: [DISCUSS] GEODE-10650: Migrate geode-site to Pelican 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect.checkpoint.com%2Fv2%2Fr01%2F___https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-10485___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86MmRiOGE3OGNlMDRjZDBkOWQyZTk1MjJlOWI1MjgwNTQ6NzpkN2IyOjliMWIxMmE0YzhiZDBkMjRhOGFiNWFkY2NjNTdhZjcwNzNjYjNiYjI0NmEzYTE5Yzk4MWNlMmI4OWQyNmYyOTM6cDpUOk4&data=05%7C02%7CJinwoo.Hwang%40sas.com%7C7c6b9c80258c475f9d0808df1273224f%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C639249957903835217%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xOY9AUlJ3J4T28c%2Bp4n7cjy8M%2F3tVuk%2FOEow12n8Wk0%3D&reserved=0<https://protect.checkpoint.com/v2/r01/___https://issues.apache.org/jira/browse/GEODE-10485___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86MmRiOGE3OGNlMDRjZDBkOWQyZTk1MjJlOWI1MjgwNTQ6NzpkN2IyOjliMWIxMmE0YzhiZDBkMjRhOGFiNWFkY2NjNTdhZjcwNzNjYjNiYjI0NmEzYTE5Yzk4MWNlMmI4OWQyNmYyOTM6cDpUOk4> [^2]: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fapache-website-template&data=05%7C02%7CJinwoo.Hwang%40sas.com%7C7c6b9c80258c475f9d0808df1273224f%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C639249957903853652%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1LV7eY9mRVqgQBHmvMxdF0c8qj4wtKZXFOIPEnNct3o%3D&reserved=0<https://github.com/apache/apache-website-template> [^3]: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fharmoncoffee%2Fgeode-site%2Ftree%2FGEODE-10468&data=05%7C02%7CJinwoo.Hwang%40sas.com%7C7c6b9c80258c475f9d0808df1273224f%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C639249957903866984%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=phepKWgwJWFZuZ6iDsA5YFBYRFlrg%2BqETM1V%2BhRZWik%3D&reserved=0<https://github.com/harmoncoffee/geode-site/tree/GEODE-10468> [^4]: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect.checkpoint.com%2Fv2%2Fr01%2F___https%3A%2F%2Flists.apache.org%2Fthread%2F69fwz35sxpsw1c2hp3t4hgsn38h4sxhd___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86MmRiOGE3OGNlMDRjZDBkOWQyZTk1MjJlOWI1MjgwNTQ6Nzo5MzVmOjJhMjI5YzNlMTI5ZmU2MTdhYjMzMjIzZDU5YjY1NzkwOTViZTg0M2QwMTIyYTIyNzIxMDA5ODZkMWU4ODkzOTc6cDpUOk4&data=05%7C02%7CJinwoo.Hwang%40sas.com%7C7c6b9c80258c475f9d0808df1273224f%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C639249957903877756%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MifB0%2FmhxDCgGf2%2FEkC5tbGDx00OnnfyZGVugCsNFDU%3D&reserved=0<https://protect.checkpoint.com/v2/r01/___https://lists.apache.org/thread/69fwz35sxpsw1c2hp3t4hgsn38h4sxhd___.YzJ1OnNhc2luc3RpdHV0ZTpjOm86MmRiOGE3OGNlMDRjZDBkOWQyZTk1MjJlOWI1MjgwNTQ6Nzo5MzVmOjJhMjI5YzNlMTI5ZmU2MTdhYjMzMjIzZDU5YjY1NzkwOTViZTg0M2QwMTIyYTIyNzIxMDA5ODZkMWU4ODkzOTc6cDpUOk4>
