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
I know my use case is special, as it's WP -> Jekyll -> Cobalt but all the posts I convert uses <!-- more --> as separator. But I'd like to use the default separator for new posts.
So maybe allow option to define the separator in convert-jekyll subcommand?
The text was updated successfully, but these errors were encountered:
The challenge will be that this is a non-default excerpt_separator so we can't build-in knowledge about it in a jekyll converter.
One option is we read the site config and apply the value in there to all files. I'm a bit mixed about doing something like that. On one hand, you generally don't change the excerpt separator globally after you've written posts, so it should be safe. On the other hand, it adds a lot of noise to frontmatters besides yours.
The other challenge is that this issue doesn't sound like its about problems with conversion but the site author changing their mind.
So another option is for us to define some kind of subcommand or flag for people to migrate excerpt_separators. It'd take the current value and push it out to all frontmatters so that its safe to change it for new pages. The problem with this is that having random subcommands or flags can clutter things up.
grumble Jekyll doesn't document the frontmatter variable excerpt_separator
From cobalt-org/cobalt.rs#375
I know my use case is special, as it's WP -> Jekyll -> Cobalt but all the posts I convert uses
<!-- more -->
as separator. But I'd like to use the default separator for new posts.So maybe allow option to define the separator in convert-jekyll subcommand?
The text was updated successfully, but these errors were encountered: