Pluxml #430
Merged
Pluxml #430
Conversation
This file contains 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
|
@jekyllbot: merge +minor |
jekyllbot
added a commit
that referenced
this pull request
Mar 9, 2020
|
Fixed most of Rubocop offenses in b3b328e |
parkr
reviewed
Mar 9, 2020
| JekyllImport::Importers::Pluxml.run({ | ||
| "source" => "/pluxml/data/articles", | ||
| "layout" => "your_layout", | ||
| "avoid_liquid" => TRUE |
There was a problem hiding this comment.
Using true here instead of TRUE is recommended, just FYI.
~$ irb
TRUE
>> TRUE
(irb):1: warning: constant ::TRUE is deprecated
=> true
There was a problem hiding this comment.
@parkr Right, I've changed it to lowercase.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PluXML is a blog CMS based on XML files instead of a database for articles and comments.
This script will help people to import their articles and drafts in Jekyll, with Nokogiri library.
I found some troubles with my own articles when you have source code in articles with a format similar to liquid, so I also include an option to tell Jekyll to not use the liquid render in exported files.