Releases · meshcloud/notion-markdown-cms

fix: do not concatenate rich text blocks with an extra space " " character in between. This fixes an issue with code blocks split into multiple rich text blocks

Assets 2

01 Mar 22:19

JohannesRudolph

v0.10.0

5d2eb17

v0.10.0

render links as relative paths
We previously rendered all page links as absolute paths e.g.
/page.md. This created some problems

some page generators that use base path prefixes like /docs/page.md
and thus need to rewrite these links, which is brittle
text editors like VSCode cannot follow the markdown links properly
because they think the links are absolute to the root / of the fs
tools like textlint-rule-no-dead-link expect relative links to resolve
them correctly

Now rendering them as relative paths.

As part of these changes it was also necessary to switch properties
parsing to render properties only as plaintext, not markdown. This is
fine because we consider frontmatter to be data (YML), not markup. Most
site generators cannot deal with markdown in frontmatter anyway.
This change was necessary because we need to parse page properties
before we can determine the destination path of the markdown file where
the page will be rendered to, and that would now require resolving
relative links.

Assets 2

25 Feb 08:57

JohannesRudolph

v0.9.0

9e162cb

v0.9.0

This is a breaking change.

Redesigned properties handling

Consumers needed more control on how to emit frontmatter properties
for advanced scenarios such as renaming/remapping properties to match
the static site generator of choice. By taking this out of configuration
and instead supplying actual functions we can easily pass that control
to consumer while simultaneously removing a lot of complexity from
notion-markdown-sync itself (i.e. the notion of property-keys vs.
property-names). This simplifies the code overall.

Assets 2