Description

The current link to the Dev UI on the Developer Joy page directs users to the Dev UI guide. However, this guide explicitly states:

This guide covers the Quarkus Dev UI for extension authors.

While the guide is helpful for extension authors, it dives into technical details that may not be relevant or appealing to developers who are new to Quarkus and simply want to explore the Dev UI's functionality. A more accessible, visually appealing page would help showcase the dev ui's capabilities in a way that is easier to understand for a broader audience.

Note: This new page is not meant to replace the current Dev UI guide. Instead, it is intended to complement it. While the new page will focus on showcasing the purpose and features of the Dev UI, the existing guide would continue to explain how to utilize the dev ui for extension authorship.

Proposal:

1. Dedicated Dev UI Page
   Create a new page specifically designed to showcase the Dev UI's functionality. This page would focus on what the dev ui offers to developers, emphasizing features over technical setup or extension authoring. Key features to highlight could include:

   • Modifying configuration
   • Viewing Swagger API documentation
   • Building Helm charts
   • Building container images
   • Visualizing dependencies
   • Running integration tests
   • Viewing the README
   • Viewing database entities and SQL scripts for create, update, and drop operations
   • Keycloak integration
   • UI for Kafka

2. Streamlined and Visual Content
   Instead of focusing on backend or extension author-specific details, this page would showcase the Dev UI's functionality with screenshots, GIFs, and simple descriptions. This approach would make the content more engaging and easier for new users to grasp.

3. Homepage Integration
   Add a section to the homepage highlighting the Dev UI as a core feature of Quarkus. This section could provide a brief summary and link to the newly created dedicated page.

Obviously this isn't the final product would actually fit the design, but wrote a quick snippet to get the idea across for what I mean for the homepage section. If implemented, it would obviously follow the design patterns set in the project already, but this is just to illustrate what I am getting at.

Benefits:

• Improved Accessibility: A dedicated page for the Dev UI makes its functionality more accessible to developers who are not extension authors.
• Engaging Design: Visual content and an intuitive layout can better capture attention and communicate the value of the ui.
• Complementary Documentation: The new page will help developers understand what the ui can do, while the current guide continues to serve extension authors.