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

links to cobalt-migrate-jekyll docs are for cobalt itself. #10

Open
ghost opened this issue May 8, 2019 · 5 comments
Open

links to cobalt-migrate-jekyll docs are for cobalt itself. #10

ghost opened this issue May 8, 2019 · 5 comments
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented May 8, 2019

the links in README.md for documentation on how to use the migrate tool are for cobalt itself, not the migrate tool.

@epage epage added the bug Something isn't working label May 8, 2019
@epage
Copy link
Member

epage commented May 8, 2019

Sorry, guess I lost track of what was remaining when I was splitting this out.

@ghost
Copy link
Author

ghost commented May 8, 2019

If that tool had some documentation and I could take it for a spin, I'd love to try cobalt again (painful otherwise)

@epage
Copy link
Member

epage commented May 9, 2019

Overall, its still pretty primitive. I've not had time to focus on it. For example, it doesn't migrate configuration, recurse through directories, etc.

@ghost
Copy link
Author

ghost commented Jun 2, 2019

if it moved the yaml frontmatter tags into that extra section (crashes when they're root level tags), that'd set me up. (jekyll doesn't care if extra keys exist in your frontmatter)

@ghost
Copy link
Author

ghost commented Jun 2, 2019

the data tag in frontmatter, I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant