The first two steps were done and while the initial export + generation works, the links, structure, and the original stackstorm.com website view is different and relies on default Hugo settings and theme.
Someone needs to dive deeper, create the stackstorm.com theme for Hugo (footer, header, etc), and play with the Hugo configuration to make sure the links/structure is as before.
Ideally, if the blog posts would be managed by hugo, while keeping the other pages behind the stackstorm.com static HTML as they have very custom HTML, and structure.
Important!
The end goal is to make the current stackstorm.com look at least 95% the same as before: structure, pages, HTML for SEO to preserve the original stackstorm view and brand, - no surprises for the visitors.
More context in the https://github.com/StackStorm/community/issues/76 For security/community reasons we migrated from WordPress to GH Static pages and https://stackstorm.com/ is managed via this repository now.
Currently, it's just raw HTML and we want Hugo template for stackstorm.com
In the past @cognifloyd created Hugo pages export from the old Wordpress + CI/CD. The export is available here: https://github.com/StackStorm/stackstorm.com/tree/wip-hugo-theme and includes pages, blog posts and also has required CI/CD GH Actions pipelines to deploy automatically to https://github.com/StackStorm/stackstorm.com/tree/gh-pages.
The first two steps were done and while the initial export + generation works, the links, structure, and the original stackstorm.com website view is different and relies on default Hugo settings and theme. Someone needs to dive deeper, create the stackstorm.com theme for Hugo (footer, header, etc), and play with the Hugo configuration to make sure the links/structure is as before.
Ideally, if the blog posts would be managed by hugo, while keeping the other pages behind the stackstorm.com static HTML as they have very custom HTML, and structure.