+1! This will greatly enhance the user experience with those services. Additionally, we have the same problem with SonataFlow and jBPM. IIRC, we have 404 pages on services generated with Kogito at the root path.
Can you send/work on a proposal for those too? Cheers! On Mon, Aug 12, 2024 at 11:43 AM Fabrizio Antonangeli < [email protected]> wrote: > Hi Jason, > It will not be a new Dev UI screen. It should be a simple html page as > a first step which will be available at the url of the service, if the > user tries to open it with the browser > (eg. http://localhost:8080/graphql) and will be integrated within the > service image. > > On Mon, 2024-08-12 at 15:01 +0000, Jason Porter wrote: > > When you say "landing page" are you talking about a new dev ui > > screen? A new section/page on our web site? Something else? I'm not > > understanding the full proposal. > > > > On 2024/08/12 10:56:44 Fabrizio Antonangeli wrote: > > > Hello everyone, > > > > > > I am proposing we create two new landing pages, which could > > > optionally > > > evolve into web applications in the future, for the Data Index and > > > the Job > > > Service. This initiative aims to replace the "Query is missing" > > > page error > > > that currently appears when users access the URL > > > http://localhost:4000/graphql and provide the user with some > > > information. > > > Since these two services are consumed by BPMN and SonataFlow, the > > > landing > > > pages should not contain specific references to them. Instead, they > > > should > > > include a brief generic introduction and point to the general > > > GraphQL > > > documentation (https://graphql.org/learn/) for the Data Index. > > > Considering the architecture, we can integrate these landing pages > > > within > > > the kie-tools repository, to allow the reuse of components, and > > > incorporate > > > them into the DI/JS images. > > > > > > If this proposal is accepted, I am also available to work on a > > > graphical > > > mockup to be shared here for feedback. > > > > > > Regards, > > > Fabrizio Antonangeli > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
