feat(docs): add guide for creating an app with Juno UI Components

[ArtieReus]

Summary

This PR introduces documentation on how to create an app using Juno UI Components. The guide covers the setup process, including adding dependencies, configuring Vite, and integrating Juno-specific providers and components into your application.

This PR does not include any interface descriptions or instructions for integrating the app with Greenhouse or Aurora. Future documentation updates may cover these integrations as needed.

Changes Made

• Added a step-by-step guide for creating an app with Juno UI Components.

Checklist

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or errors.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3db3589

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

PR Preview Action v1.4.8
🚀 Deployed preview to https://cloudoperators.github.io/juno/pr-preview/pr-679/
on branch gh-pages at 2024-12-12 09:05 UTC

[ArtieReus]

@edda do you want to mention anything about the app props embedded and fullWidthContent for the AppShell?

[andypf]

Great!

[andypf]

@ArtieReus, could you please add a section about bundling? Specifically:

• Standalone Applications: For standalone applications, all libraries should be bundled directly into the application.
• Host-Dependent Applications: If the application is designed to run on a host that already provides certain libraries, these libraries should not be bundled. Instead, they should be added to the peerDependencies section.

found an issue

[edda]

I like it a lot! Very good instructions.
Only thing missing is the info about differences in bundling when building for standalone vs. embedded <- @andypf

[barsukov]

LGTM from my side make some changes that was requested and we are good to go

[edda]

@edda do you want to mention anything about the app props embedded and fullWidthContent for the AppShell?

Ah yeah, good point. I think it's enough to mention that those props exist and to check the storybook documentation of AppShell for more details (what they do is documented there)

[edda]

Perfect! One small suggestion to make it a bit clearer what people can expect from our host apps.