Skip to content
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

[Feature] Table of content on main page #83

Open
1 task done
sj11105 opened this issue Jan 14, 2025 · 10 comments · May be fixed by #84
Open
1 task done

[Feature] Table of content on main page #83

sj11105 opened this issue Jan 14, 2025 · 10 comments · May be fixed by #84
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@sj11105
Copy link

sj11105 commented Jan 14, 2025

Problem

By adding the table of content on the main page , it will be easy for the users to navigate through website as it causes confusion otherwise.

Description

I have added a table of content on main page that leads to the main website as well as other navigation panels that are present in the website navbar.

Additional context

As you suggested that adding table of content will solve the other issue as well .

Screenshot 2025-01-14 110427
this is how i thought of designing this

Implementation

  • I would be interested in implementing this feature.
@sj11105 sj11105 added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Jan 14, 2025
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Jan 14, 2025
@possumbilities possumbilities moved this from Triage to Backlog in possumbilities Jan 14, 2025
@possumbilities
Copy link
Contributor

Hi @sj11105 Thanks for making an Issue for this. I think given its simplicity a list of links that go to the various contexts would be enough to accomplish what needs to happen.

The design shown above isn't inline with the Vocabulary design system and is probably a bit more complex than this use-case requires.

@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

ok so you want me to make just a simple list of links with minimal design right?

@possumbilities
Copy link
Contributor

@sj11105 Yes! I doubt you'd even need to modify any CSS to do so.

@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

ok ok i will be sharing the screenshot asap

@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

Screenshot 2025-01-14 201023
I hope this works

@possumbilities
Copy link
Contributor

@sj11105 That screenshot works, but it should link to all the pages within the contexts folder, labelled appropriately (and linked appropriately)

@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🧹 status: ticket work required Needs more details before it can be worked on labels Jan 14, 2025
@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

ok please assign me this i will complete it by today

@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

Screenshot 2025-01-14 203818
I have added labels for all the pages and also linked them correctly . The code is ready to be merged

@possumbilities
Copy link
Contributor

@sj11105 I think you should move to a PR

@sj11105
Copy link
Author

sj11105 commented Jan 14, 2025

Yes i have raised the PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants