Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

define excerpt separator as option #2

Open
epage opened this issue Aug 31, 2018 · 1 comment
Open

define excerpt separator as option #2

epage opened this issue Aug 31, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@epage
Copy link
Member

epage commented Aug 31, 2018

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?

@epage epage added the enhancement New feature or request label Aug 31, 2018
@epage
Copy link
Member Author

epage commented Aug 31, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant