[📑 Docs]: import Glee docs under tools folder

[AnimeshKumar923]

What Dev Docs changes are you proposing?

• To help setup the workflow from Create GitHub Action to Render Docs into AsyncAPI Website Pages glee#481, we need to import the existing docs. Also, we need to add the weights and categorization to match same as the existing docs format.

• Sample format: tutorials section. We can see that there is the sub-categorization of docs which is present inside the getting-started folder and how it relates to its parents.

• Make a separate branch and do your work on that branch only. Don't make changes to the master branch.

• Follow this guide before working on this issue.

Tasks

• Create glee folder under website/pages/docs/tools/glee (I'm assuming Glee falls under tools section, please correct me if I'm wrong)
• Copy reference folder from here and paste it inside glee folder.
• Inside reference folder, there are three sub-folders namely, classes, interfaces and modules. In each file under the three sub-folders, we need to add a parent child relation similar to this.
  cc: @alequetzalli @thulieblack

Code of Conduct

• I agree to follow this project's Code of Conduct

[AnimeshKumar923]

/gfi docs

[AnimeshKumar923]

what are the docs to import first as to get the workflow started?
cc: @KhudaDad414 @Souvikns @afzal442

[derberg]

to start pushing Glee or any other docs to website, there is nothing that must be done in the website

you need automation in glee, like:

• cli example: https://github.com/asyncapi/cli/blob/master/.github/workflows/update-docs-in-website.yml
• generator example: https://github.com/asyncapi/generator/blob/master/.github/workflows/update-docs-in-website.yml

the only thing that is not there in examples, is something that was added later, a config file for Edit button. So the automation you add, should also edit https://github.com/asyncapi/website/blob/master/config/edit-page-config.json and add your repo there

[AnimeshKumar923]

the only thing that is not there in examples, is something that was added later, a config file for Edit button. So the automation you add, should also edit https://github.com/asyncapi/website/blob/master/config/edit-page-config.json and add your repo there

@derberg can I add this manually? or do I have to use automation/script?

Edit button.

Are you talking about this Edit button?

[derberg]

Are you talking about this Edit button?

the intention is that this edit button, if possible, is done automatically by the integration script, this is why we have it in JSON file.

[AnimeshKumar923]

Are you talking about this Edit button?

the intention is that this edit button, if possible, is done automatically by the integration script, this is why we have it in JSON file.

Okay. Let me figure it out then...

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[AnimeshKumar923]

resolved with asyncapi/glee#548