feat(callout): Move Callout component to nextra/components

[tristandubbeld]

To enable usage of the Callout component in docs, blog and custom themes, we extract it to the nextra package components folder and export it from there.

In this PR

• Moved Callout component from nextra-theme-docs to nextra/components.
• Updated the blog and docs examples.
• Updated the Nextra documentation.
• Decide on clsx package usage in nextra components.

[changeset-bot]

🦋 Changeset detected

Latest commit: 818aa97

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
nextra-theme-docs	Major
nextra	Major
nextra-theme-blog	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextra-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 22, 2023 11:52am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
nextra	⬜️ Ignored (Inspect)	Visit Preview		May 22, 2023 11:52am

[vercel]

@tristandubbeld is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[tristandubbeld]

Instead of using clsx we can use something like TypeToClassName like we do with emojis, what do you think?

[dimaMachina]

I think is totally fine to use clsx in nextra, because I want to move other components from nextra-theme-docs to nextra too - Tabs, Steps, FileTree

[tristandubbeld]

Let me know if you need help with those 👍

[dimaMachina]

Sounds good! You can work on it, thank you!

[tristandubbeld]

Preferring this css rule over using .not-prose to enable callout content to have markup. Not sure if we want paragraphs inside callouts to have more space around them though. Multiple lines do now look like this:

[tristandubbeld]

@B2o5T I can move the Callout docs to the general Nextra pages, what do you think would be a good path / navigation flow? I can do /docs/guide/built-ins/callout for example. Not sure if people start looking there when they need specific built in components if there is just one for the time being. Also unaware of any decisions that were already made on this.

[dimaMachina]

I can move the Callout docs to the general Nextra pages, what do you think would be a good path / navigation flow?

I think is reasonable to move these docs to Nextra pages since nextra-theme-docs now just reexport them

[tristandubbeld]

Should we add a redirect from docs/docs-theme/built-ins/callout to docs/guide/built-ins/callout to the next config? And if I add a changeset, should it be a minor version or a patch?

[dimaMachina]

Should we add a redirect from docs/docs-theme/built-ins/callout to docs/guide/built-ins/callout to the next config? And if I add a changeset, should it be a minor version or a patch?

about redirect - nice catch, you can add it

and about changeset - minor since it's a new feature and not a fix of a bug 🙂

[dimaMachina]

@tristandubbeld Sorry I was OOO last week, I'll release it today

[dimaMachina]

i fixed info callout colors