-
Notifications
You must be signed in to change notification settings - Fork 104
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
[convert-jekyll] define excerpt separator as option #375
Comments
The challenge will be that this is a non-default 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 grumble Jekyll doesn't document the frontmatter variable |
Converting the excerpt_separator is a great idea, but without Jekyll standard it's hard to do… |
Can you clarify what you mean here? |
The missing doc you grumbled about ^^ |
Its not documented but it seems we can count on it |
Closed for cobalt-org/cobalt-migrate-jekyll#2 |
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: