✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b6ed1e3
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/6393f9470048ca0008749637
😎 Deploy Preview	https://deploy-preview-1097--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

⚡️ Lighthouse report for the changes in this PR:

Lighthouse ran on https://deploy-preview-1097--asyncapi-website.netlify.app/

yay! nice job so far! thank you for taking care of that so quickly 🙌🏽🙌🏽🙌🏽

We need to have another technical feedback review by @derberg before we can merge tho, so now we wait for him 😄✌🏽

@alequetzalli thank you for your compliments. I was only able to complete the task so quickly because of your well detailed and timely feedbacks. It's been a pleasure working with you on this, and I'm looking forward to working with you on a new task once this current one is completed.

It looks good. My only concern is that it is CLI docs authored in website repo, and it should be authored in cli repo, like we do with generator.

@alequetzalli I mean we need docs under cli repo (but 3 markdown files, one for intro, one for installation and one for usage, and later we can add a nice one about context concept explanation), and then add automation to cli repo that will push any updates done to docs, to the website repo.

Hey @activus-d, kindly update the GoBack button on /docs/guides page to point it to the new AsyncAPI CLI page created by you.

@akshatnema Thanks for the Observation. The branch has been updated.

Hey @activus-d here is what you need to do:

1. We are not going to merge this PR; as Lukasz observed, we want to host docs in their main repo and have them copied to the website repo where we can maintain them in the official website.
2. You must create a NEW PR in the CLI repo with this same exact content. Make sure this new PR in the CLI repo is only the written docs' content. (You don't need to add the prev/next buttons here since those only work on the /website repo.)
3. For this NEW PR, let's actually make a tiny change. We want to have this CLI docs have subsections in the left-hand navigation. To accomplish that, you must separate your current CLI docs into separate files instead of only 1 file like you currently have in this PR. Let's separate your content based on the outline into 3 tiny sub-sections: introduction.md, installation.md, and usage.md.
4. @derberg needs to code an automation that copies new docs added in CLI repo to the /website repo. Once that functionality is complete, it will be automatic to open a PR in both CLI and /website repoes. (Lukasz needs to sync with us on what he thinks his next steps here are and timeline)
5. After the new automation copies the docs over to a new PR in the /websiterepo, you must ensure to add the prev/next buttons just like akshat showed you here.

I realize this is a lot of extra steps to think about, so please let us know if you understand and if you're able to do next steps. 😄✌🏽

later we can add a nice one about context concept explanation

Not quite, that is not what the Concepts sections is for and you should not duplicate content buckets into sub-sections.

Instead, the CLI tool will be introduced in the first file of introduction.md and any background context needed to introduce the tool shall be inside the Introduction section.

@derberg

Not quite, that is not what the Concepts sections is for and you should not duplicate content buckets into sub-sections.

oh, sorry, by concept I meant concept in general, not Concept bucket. So like in generator, where we have docs that explain different generator concepts, but these are just on the list of docs for generator. Same I mean for CLI, we just need to have later a document that explains "context" functionality/concept in the CLI.

2. You must create a NEW PR in the CLI repo with this same exact content. Make sure this new PR in the CLI repo is only the written docs' content. (You don't need to add the prev/next buttons here since those only work on the /website repo.)
3. For this NEW PR, let's actually make a tiny change. We want to have this CLI docs have subsections in the left-hand navigation. To accomplish that, you must separate your current CLI docs into separate files instead of only 1 file like you currently have in this PR. Let's separate your content based on the outline into 3 tiny sub-sections: introduction.md, installation.md, and usage.md.

@alequetzalli Alright. However, you are yet to tell me which of the directories in the CLI repository would host the documents. Is it that I will create a new folder at the root of the repository and name it (let's say docs)? I need a specific direction in this regard.

@activus-d yes, new docs directory like https://github.com/asyncapi/generator/tree/master/docs

@derberg @alequetzalli I will work on it and make a pull request soon.

@alequetzalli @derberg the pull request has been made as instructed. Kindly review.

CLOSING in favor of resolving via asyncapi/cli#414