Please incorporate the "From zero in 5 minutes to dApp" showcase project into the Juno organization

[dennyweiss]

Proposal

The showcase project should move into a separate target repository to allow an easy forking process and streamline adding static website files.

Please recognize that the initially proposed 2 minutes were too ambitious. Realistically, 4-5 minutes are required to go through the process

Resources to consider

• Repository with guide: https://github.com/dennyweiss/from-zero-in-2min-to-dapp
• Process overview
• From Zero in 2 Minutes to dApp – Intro
• From Zero in 2 Minutes to dApp – Action

[peterpeterparker]

Thanks!

I've opened a repository: https://github.com/junobuild/from-zero-in-5min-to-dapp

I suggest you provide a PR so you can receive attribution for your contribution.

After reviewing your guide and repository, please address these notes before submitting the PR:

• "Navigate to Juno" can be shortened to "Navigate to https://console.juno.build"
• Would be great to add a mention that "Creating an Internet Identity" is not a must of one has already an identity
• ⚠️ Please replace "Continue and set pin" with "Passkey." I consider this method insecure because users may too easily lose their identity, particularly on iOS, which cleans the storage every two weeks in case of inactivity, and also because a seed phrase for recovery is not enforced. Additionally, as soon as Juno can disable this method in the II authentication flow, it will definitely be disabled. I've been waiting for this option for months.
• the juno dependencies in package.json are not required
• the viteCompression plugin should be removed given that the CLI takes care of the compression

[peterpeterparker]

The initial suggestions were not addressed, and as a result, the project did not progress further. Since the CLI I envisioned to ease onboarding of new developers has now been developed (repo) and is set to be incorporated into the core documentation, I've deleted the empty repository I created a few months ago for this purpose. With the new setup, a dedicated recipe would be more suitable as a community contribution. I would be happy to integrating this into the website, with or without a blog post, and including an external link to the repository not maintained by Juno.

Let me know if you find time to make the suggested adjustments as for example the PIN method has now been disabled in the latest Juno release, which will need to be addressed.