Candidates in Quarkus/Red Hat/IBM codebase for a migration to Roq

[ia3andy]

State the site, what it currently uses and the amount of work it would involve.

[ia3andy]

hub.quarkiverse.io (currently in Gatsby)

[ia3andy]

@holly-cummins looking at the site, it should be relatively easy no?

[holly-cummins]

Yes, I think so. It's Gatsby rather than Jekyll, so will need a bit of 'translation' of directory structures, and so on. Another complexity is that it's a mirror of a GitHub wiki, so there's some logic to do with making sure the wiki content renders in the best way for a website. But it should be pretty simple.

[ia3andy]

keycloak.org

[ia3andy]

@edewit would you have a look to the level of difficulty?

[edewit]

I don't think it's difficult it's already has a blog type structure we just need to convince @stianst

[stianst]

Static generator stuff we have for keycloak.org is pretty straightforward, and it relies on FreeMarker and AsciiDoc. What we do have is quite a bit of custom code to handle releases/versions/blogs/extensions/etc. So I don't see much value in moving to a different approach as what we have now (custom stuff) is pretty easy to maintain.

[ia3andy]

quarkus.io

https://github.com/quarkusio/quarkusio.github.io/

Quite large codebase using Jekyll for now

[holly-cummins]

quarkus.io/extensions

This is a Gatsby site with many custom Gatsby plugins, and lots of render-side logic, so this one would be very hard. It pulls information from the registry, maven central, github, and a few other sources, in order to build up a GraphQL model. It also uses a lot of React on the front-end.

[ia3andy]

Yes, it won't be easy for sure.

The cool things is we would be able to use Java services to pull the data, but yeah the react is not easy to convert to html..