Investigate table of content use case · Issue #137 · contentlayerdev/contentlayer · GitHub

contentlayerdev / contentlayer Public

• Notifications You must be signed in to change notification settings
• Fork 193
• Star 3.5k

• Code
• Issues 90
• Pull requests 3
• Discussions
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Investigate table of content use case #137

Copy link

Copy link

Open

Open

Investigate table of content use case#137

Copy link

Labels

has-workaroundmeta: never-staleneeds-researchtopic: markdown/mdx

Description

schickling

opened on Mar 8, 2022

Issue body actions

My first approach would be to try to use computed fields for this.

Related

• https://github.com/syntax-tree/mdast-util-toc
• https://github.com/remarkjs/remark-toc
• https://github.dev/shuding/nextra/blob/f8d25f29d321550b6586f9d6ed0546e8654dd1f8/packages/nextra/src/types.ts#L25

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

Labels

has-workaroundmeta: never-staleneeds-researchtopic: markdown/mdx

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions