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
wp_exporter produce a more Jekyll compatible front, but it has a bug that delete some links (youtube links in my example).
So I used exit_wp that keep all the content properly, but the front lack of permalink.
Another issue is that both front ends their permalink with a slash instead of .html, which makes cobalt try to generate /permalink/index.html instead of /permalink.html.
So maybe we can improve the converter by providing some options:
provide some regex to define how to parse the permalink attr, so we can say which field we need to convert into permalink, and how (like dropping the base url my example)
make sure that no trailing slash remains and add extension .html
or even drop the permalink completely
The text was updated successfully, but these errors were encountered:
From cobalt-org/cobalt.rs#374
While working on migrating my blog from WP to Cobalt through Jekyll, I've used 2 different WP plugin to export to Jekyll:
wp_exporter
)exitwp
)wp_exporter produce this kind of frontmatter:
exit_wp:
wp_exporter produce a more Jekyll compatible front, but it has a bug that delete some links (youtube links in my example).
So I used exit_wp that keep all the content properly, but the front lack of permalink.
Another issue is that both front ends their permalink with a slash instead of
.html
, which makes cobalt try to generate/permalink/index.html
instead of/permalink.html
.So maybe we can improve the converter by providing some options:
.html
The text was updated successfully, but these errors were encountered: