Imagine this: You’re a new developer starting onboarding with your organization, your spirit burning bright with great desire to craft and create.

The keys to your new digital kingdom, your laptop and access credentials, have just been handed over to you.

Amid the excitement, you discover a welcome email in your inbox, with a link to access the Red Hat Developer Hub (RHDH), your organization’s Internal Developer Portal (IDP).

Included in the welcome email are some useful links to provide more details on the technologies you’ll be engaging with in your new role.

"It looks like this handy glossary is going to be a useful companion through my journey," you think to yourself.

With these resources at your fingertips, you’re now ready to start working on your new project.

Eager to check out the RHDH, you quickly follow the instructions from your welcome email.

You use this URL to log into RHDH.

Next, you click on the GitLab button to start the authentication process.

Now, it’s time to enter your username and password as detailed below:

After inputting your credentials, you click the Sign in button.

You then click on the Authorize keycloak button to authorize Keycloak to access you account.

Moments later, you’re welcomed by the RHDH landing page.

Eager as you are, you immediately want to explore the Golden Path Templates (GPT) you’ve heard so much about from your colleagues.

You find and click the Create link in the left menu.

Among the options, you spot the GPT titled Insecured Quarkus Service Software Supply Chain

Feeling a mix of excitement and curiosity, you click the Choose button.

As the form for the Golden Path Template (GPT) appears, you’re pleasantly surprised.

Unlike other complicated ticketing systems you’ve used before, this form is refreshingly simple and seems tailor-made for your particular task.

"Ah, so my team has opted to use Quarkus for this project. That’s a great framework for developing Kubernetes-native applications," you tell yourself, with excitement sparking within you..

You click Next.

You’re pleased to find all the input fields are already pre-populated for you.

You also note that your organization is using Red Hat Quay as the image registry.

You click Next on the this form as well.

Now, you hit the Review button for a final look at the form inputs.

Everything checks out, so you confidently click on the Create button.

The Golden Path Template (GPT) kicks into action, and in just a few seconds it sets up everything you need for your Quarkus application.

The GPT has done quiet a bit of heavy lifting on your behalf here:

You click on the Open Component in Catalog link.

And just like that, you’re directed to your Dashboard, where all the tools you need to start coding are readily available at your fingertips.

The first thing you decide to do is dive into coding on your project.

You decide to use the Integrated Development Environment (IDE), OpenShift Dev Spaces, that Developer Hub has been configured to use. You find and click on the OpenShift Dev Spaces (VSCode) link conveniently located in your Dashboard.

You log in using your OpenShift credentials by clicking the Log in with OpenShift button.

Then, you choose the Single Sign-On option by clicking the rhsso button

You then enter your username and password as follows:

After inputting your credentials, you click the Sign in button.

You authorize OpenShift Dev Spaces to access your account by clicking the Allow selected permissions button.

OpenShift Dev Spaces then begins creating your workspace, processing a Devfile containing all the configuration needed to set up your development environment.

A prompt Do you trust the authors of this repository? will appear. Select Do not ask me again for other repositories and then click Continue

Subsequently, you click Authorize devspaces to grant OpenShift Dev Spaces access to your GitLab account.

After waiting a few minutes for OpenShift Dev Spaces to finish setting up your workspace, you’re presented with a fully fledged IDE accessible from your browser.

You click the button Yes, I trust the authors.

To accomplish your task, you need to:

In your insecured-app workspace, you expand the folders src → main → java, and then open the ExampleResource.java file.

On line 14, you replace the return message of the hello method from "Hello RESTEasy" to "Hello from RHDH".

Next, you update the JUnit test for this method.

You expand the folders src → main → test, and open the ExampleResourceTest.java file.

On line 18, you change the expected text from "Hello RESTEasy" to "Hello from RHDH".

You recall your team’s explanation that the documentation coexists with the code, nestled in the same git repository as a markdown file.

You expand the docs folder and open the markdown file Index.md.

At the document’s end, you add: "Release 1.0: Update to ExampleResource.hello() method to return 'Hello from RHDH'."

Having completed your task, you’re ready to commit your changes.

You click on the Source Control icon located in the left menu.

Then, you enter the commit message "My First Commit" and click on the Commit button to finalize your changes.

In the pop-up window that follows, you click Yes to stage your changes.

Finally, you click on the Sync Changes button.

In the pop-up that follows, you click OK to push your changes and complete the process.

You’ve successfully implemented your change and updated the documentation in one commit, following the "docs as code" methodology where documentation is treated with the same level of care and under the same process as source code.

You are delighted by knowing that following this methodology ensures that your documentation is as current as your code itself.

Your commit triggers the build pipeline for your Quarkus application.

You switch back to the RHDH Dashboard tab in your browser and select the CI tab from the top menu.

And just as you expected, a build pipeline has already been triggered.

You eagerly expand the pipeline view to monitor the progress of this pipeline run.

After a few minutes of anticipation, the pipeline run concludes, and the application image is successfully built.

You select the Image Registry tab from the upper menu and confirm that your image has been pushed to the Registry.

Finally you switch to the Docs tab and verify that documentation is up to date.

With a sense of accomplishment, your task now complete, you draft an email to the QA team, inviting them to begin testing your changes.