-
-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add table of contents to case studies view #1502
Comments
Hey @derberg I would like to work on this. |
I would like to work on this |
@janvi01 please do 🙏 @achiverram28 please specify that you want to work on something only if you really will work on something and not like in case of asyncapi/cli#503. We, maintainers put a lot of time on onboarding new people, helping them make first steps in open source and we are really time limited, so if we commit our time, we expect this time commitment is respected |
Hey @derberg I see no progress on this issue for 3 weeks. |
@Shurtu-gal please do 🙏🏼 |
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 ❤️ |
Reason/Context
Individual case study has many sections: https://www.asyncapi.com/casestudies/adeogroup
Would be cool to have table of contents like we have with blog posts and docs
Description
Example blog with
ON THIS PAGE
on the right: https://www.asyncapi.com/blog/march-2023We need the same for https://www.asyncapi.com/casestudies/adeogroup
The text was updated successfully, but these errors were encountered: