Replies: 1 comment
-
I think these are roughly in order of usefulness (that is, arbitrary functions are clearly overkill). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Note files get a default URL route right now that is based entirely on their filepath (sans extension). This leads to ugly URLs like
/Foo/Bar%20Qux
(for/Foo/Bar Qux.md
).Let's call this default behaviour the "direct" slug semantic.
direct
(default; filepath sans ext)What other slug semantics are possible? The more pretty ones include,
baseonly
(neuron-style)baseonly-slugify
(neuron-style, but lowercase and whitespace replaced with hyphens)slugify
(like above, but includes fullpath)The above can be specified at per-route (per-folder) level using YAML configuration.
In addition, we may allow the user to specify a custom slug on a per-Markdown file basis in the frontmatter,
This creates
foo.html
. It would createfoo.html
in the containing directory (thus, includes full path) unless that routes's merged YAML config uses one of the "baseonly" semantics (which discards directories in URLs).Progress
slug
in YAML frontmatter, behaving exactly like the feature in neuron: Custom Slugs #51slug
to contain/
(ie. full relative path)Beta Was this translation helpful? Give feedback.
All reactions