Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the Static Site Generation doc and getting started to the Roq Site #319

Closed
ia3andy opened this issue Dec 11, 2024 · 4 comments · Fixed by #329
Closed

Move the Static Site Generation doc and getting started to the Roq Site #319

ia3andy opened this issue Dec 11, 2024 · 4 comments · Fixed by #329

Comments

@ia3andy
Copy link
Contributor

ia3andy commented Dec 11, 2024

During a Roq demo, @emmanuelbernard told me it would be better to have a doc outside the Quarkiverse one for the Static Site Gen part.

I also think that makes sense.

The idea is to move all the non standalone docs to the site (it shouldn't be too hard as we support asciidoc :) and have a link in the Quarkiverse doc pointing to the site.

@ia3andy
Copy link
Contributor Author

ia3andy commented Dec 11, 2024

I think I'll also request roq.quarkus.io sub-domain (@maxandersen does that make sense?)

@maxandersen
Copy link
Member

Not following the issue ?

On first hunch I wouldn't hook roq into Quarkus.io. It's in quarkiverse.

@ia3andy
Copy link
Contributor Author

ia3andy commented Dec 12, 2024

It's about not overwhelming users with Quarkiverse stuff when they hook in Roq and they shouldn't have to care if they don't want to...

@emmanuelbernard
Copy link

My point is that the user base for Roq is not a Quarkus audience. They need a top level landing site explaining what roq is about. Roq.com really. I think roq.quarkus.io almost miss the mark too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants