You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that the output of starlight-obsidian will not match the in-Obsidian or Obsidian Publish view.
Describe the solution you'd like
It would be cool if the Obsidian callout formatting was preserved when mapped into Starlight.
Describe alternatives you've considered
Perhaps it would be possible to build an ObsidianAside component in this integration, and have it override the base Starlight Aside, while preserving the ::: syntax — if using .mdx? Or maybe there's a better way to do that within the existing .md/remark/rehype system.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
The current mapping of Obsidian callouts to Starlight Asides is indeed a best effort. When withastro/starlight#2261 is merged to Starlight, this mapping will be improved icon-wise.
I personally think the difference in styling between Obsidian and Starlight is fine as both are different systems so some differences are expected. However, I'll keep an eye on feedback and if this is a common request, I'll reconsider the approach.
Is your feature request related to a problem?
Obsidian supports a broad range of callouts with different icons and styling for each type. This integration maps those callouts to the smaller set of Starlight Asides.
This means that the output of starlight-obsidian will not match the in-Obsidian or Obsidian Publish view.
Describe the solution you'd like
It would be cool if the Obsidian callout formatting was preserved when mapped into Starlight.
Describe alternatives you've considered
Perhaps it would be possible to build an
ObsidianAside
component in this integration, and have it override the base Starlight Aside, while preserving the:::
syntax — if using.mdx
? Or maybe there's a better way to do that within the existing.md
/remark/rehype system.Additional Context
No response
The text was updated successfully, but these errors were encountered: