You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code.quarkus is phenomenal. But, it could be confusing for the low-code user that doesn't (yet) care about Quarkus.
How about a streamlined widget that just asks for the basics needed to build a Roq site and pushes it to GitHub? It could of course use code.quarkus behind the scenes, but a user would not notice this.
This widget should be easily shareable so it can be embedded in other websites. For example, other Roq built websites might like to include it when talking about how their site was built.
I can provide a mockup image if my description isn't clear enough.
The text was updated successfully, but these errors were encountered:
I had something like this in mind already for other extensions, some kind of small configurable web-components provided by code.quarkus.io making it possible to have specific application generators on extensions docs.
That would also fit this use-case.
Thing is, I have a pile of other things in front of that one in my to-do 🫣...
Time is always the problem :-( I assumed it would be low priority, but thought I'd register the idea for when the time comes or incase someone wants to contribute it. I don't think my front-end skills are up to this level of contribution, unfortunately.
Code.quarkus is phenomenal. But, it could be confusing for the low-code user that doesn't (yet) care about Quarkus.
How about a streamlined widget that just asks for the basics needed to build a Roq site and pushes it to GitHub? It could of course use code.quarkus behind the scenes, but a user would not notice this.
This widget should be easily shareable so it can be embedded in other websites. For example, other Roq built websites might like to include it when talking about how their site was built.
I can provide a mockup image if my description isn't clear enough.
The text was updated successfully, but these errors were encountered: