MovableType Static comment exporting hack #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Due to plugin architecture change. This change seems working. Will fix to reflect changes to Jekyll 2.0 later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I'm sending this as a pull request, but I'm wondering whether this code should be merged to this repository or not, and want to hear your opinion.
I have created a patch to jekyll-import ( jekyll/jekyll-import#66 ) , to statically generate comments from a MovableType based site.
To generate the site, I have created a modified version of template and plugin based on your work.
I think current code is incomplete, but at least works for me, so want to share this somewhere.
The question is, where is best to distribute this code. Since the code is heavily depends on modified version of jekyll-import, it is natural to put the work into jekyll-import repository. The other option is store these files onto this repository, but it does not have any directory, committing into subdirectory seems odd.
Do you prefer to have these codes at the top-level directory of this repository, or in jekyll-import repository?