Next.js Discord

Discord Forum

Help with creating a blog using Fumadocs

Unanswered
tsa posted this in #help-forum
Open in Discord
tsaOP
I wanted to add a blog to my portfolio, so I came across FumaDocs. It looked cool, so I followed the documentation and used parts of the FumaDocs repo to set up the blog.

I'm not entirely sure if I did everything correctly. This is the repo: https://github.com/techwithanirudh/shadcn-portfolio/tree/canary/src/app

I wanted help with adding custom fields to the existing metadata provided by fumadocs.

22 Replies

Asian black bear
Additionally you don't have any question or request in your original post. What are you looking for?
tsaOP
@fuma nama Hey
How would I add a custom schema while using @fumadocs/content-collections
fuma nama
you just use object spread like: { ...original, myProperty: xxx } to the schema.
tsaOP
cool, tysm!
@fuma nama you just use object spread like: `{ ...original, myProperty: xxx }` to the schema.
tsaOP
Is there a way for fumadocs to use the existing next-themes instance, so that when I switch color schemes fumadocs's rendering too changes the color

I looked up root provider for fumadocs
fuma nama
disabling theme can do the trick
joulev
i think if you are bringing your own styles you should use fumadocs in headless mode and use your own UI
@joulev i think if you are bringing your own styles you should use fumadocs in headless mode and use your own UI
tsaOP
i've never used fumadocs before, so idk what i'm doing but it seems good so far
fuma nama
For custom color schemas you can use our tailwind css plugin or css variables. But changing next themes config (only light/dark mode) doesn’t need further setup
@fuma nama For custom color schemas you can use our tailwind css plugin or css variables. But changing next themes config (only light/dark mode) doesn’t need further setup
tsaOP
this is what I did, most of it is from fuma, works fine
@joulev i think if you are bringing your own styles you should use fumadocs in headless mode and use your own UI
tsaOP
Hey!

I'm doing this
<InlineTOC items={page.data.toc} />

and i'm getting a type error
TS2322: Type
{ title: string | number | bigint | boolean | { type: string | {} | {}; props: any; key: string | null; } | { [Symbol. iterator]: {}; } | { children: string | number | bigint | boolean | { type: string | ... 1 more ... | {}; props: any; key: string | null; } | ... 4 more ... | undefined; type: string | ... 1 more ......
is not assignable to type TOCItemType[]
fuma nama
Try as any first and see if there’s any issue
The information you provided is insufficient for further investigation
@fuma nama Try `as any` first and see if there’s any issue
tsaOP
yeah, that works, but i probably want to fix this without doing that
@fuma nama The information you provided is insufficient for further investigation
tsaOP
i just copied the fumadocs blog example, but i'm using content collectors instead, so i changed some stuff, i'm not so sure if me porting to content collectors is causing the issue. i can give more info
@tsa yeah, that works, but i probably want to fix this without doing that
fuma nama
Probably because some updates from Content Collections, their types are quite complicated. You can use any as a temporary solution, will fix it later