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

Add Table of Contents to OUSD Blog #105

Open
rmcn15 opened this issue Mar 9, 2023 · 2 comments
Open

Add Table of Contents to OUSD Blog #105

rmcn15 opened this issue Mar 9, 2023 · 2 comments
Labels
enhancement New feature or request P4 Something to consider, a feature request that we may not pursue

Comments

@rmcn15
Copy link

rmcn15 commented Mar 9, 2023

A table of contents on the OUSD blog will help us hit Keywords again within H2s/H3s.

Here's an example on the staging site: https://staging.ousd.com/litepaper

If this can automatically pick up H2s for headers and H3s as subheaders within the ToC that would be perfect. Alternatively I can manually add these sections in the CMS.

@franckc
Copy link

franckc commented Mar 9, 2023

CC @micahalcorn for prioritization

CC @HrikB for commenting on the eng scope

@HrikB
Copy link
Contributor

HrikB commented Mar 11, 2023

Yeah should definitely be possible. It currently pulls each section from the cms... you can see how it is configured in the OUSD - Litepaper collection type. But theoretically it is possible to just read the h2s and h3s of the page and construct that data by itself.

The thing is I will need to attach a reference to each h2/h3 so the ToC navigates properly which I should be able to do from parsing the string... but if that doesn't work we may need to separate each section.

@micahalcorn micahalcorn added enhancement New feature or request P4 Something to consider, a feature request that we may not pursue labels Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P4 Something to consider, a feature request that we may not pursue
Projects
Status: Backlog
Development

No branches or pull requests

4 participants