Repository navigation
Rearrange sidenotes to avoid overlapping - #67
Merged
Merged
Conversation
janezd
changed the title
janezd
force-pushed
the
relayout-sidenotes
branch
from
September 14, 2025 20:31
aca89a2 to
c260c92
Compare
janezd
force-pushed
the
relayout-sidenotes
branch
from
September 15, 2025 11:49
c260c92 to
956e195
Compare
janezd
force-pushed
the
relayout-sidenotes
branch
3 times, most recently
from
September 15, 2025 19:50
d44abde to
7b9d7db
Compare
janezd
marked this pull request as ready for review
September 16, 2025 13:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ref #62.
If a side note overlaps with a previous one, it is pushed down.
I tried a number of approaches, but contexts seem to be the easiest way to register all sidenote components within mdx. Not only because it is easier to share it down the hierarchy of the book: approaches with reporting refs were a nightmare.
This works for
<Sidenote>and<ExpandingSideImg>, not for<!!! float-aside !!!>, which are not React components and can't be controlled in a similar way. The easiest way to include float-aside would be to simply replace them with ` when parsing the mdx. This is done in #68.