kramdown | Markdown editor you really want | Editor library

Converting thousands of Stack Exchange Q&A in markdown format isn't as easy as simply copying them over to GitHub Pages. The python program stack-to-blog.py was used to convert Stack Exchange posts to GitHub Pages Posts. The full stack-to-blog.py program can be accessed on the Pippim Website repo 🔗.

The program automatically:

• Creates Jekyll front matter on posts and front matter totals for site.
• Selects Stack Exchange Posts based on meeting minimum criteria such as up-votes or accepted answer status.
• If self-answered question, the answer is included and not the question.
• If self-answered question, the accepted answer alone doesn't qualify. Votes from other are the qualifier.
• Initial testing allows selecting small set of random record numbers to convert.
• Converts Stack Exchange Markdown formats to GitHub Pages Kramdown Markdown format.
• Creates hyperlinks to original Answer in Stack Exchange and Kramdown in GitHub Pages.
• Creates search word to URL indices excluding 50% of words like "a", "the", etc. to save space.
• Selectively inserts Table of Contents based on minimum criteria settings.
• Selectively inserts Section Navigation Buttons for: Top (Top of Page), ToS (Top of Section), ToC (Table of Contents) and Skip (Skip section).
• Selectively inserts "Copy Code Block to System Clipboard" button based on lines of code.
• Creates HTML with "Top Ten Answers" with the most votes.
• Creates powerful nested expandable/collapsible detail/summary HTML for many thousands of tags by post.
• Remaps hyperlinks in Stack Exchange Posts to {{ site.title }} website posts if they were converted.
• Fixes old broken #header Stack Exchange Markdown.
• Converts < block quote Stack Exchange Markdown into what works in Jekyll Kramdown.
• Convert Stack Exchange tags to fenced code block language.
• When no fenced code block language is provided, uses shebang language first (if available).
• Converts older four-space indented code blocks to fenced code blocks.
• Converts Stack Exchange Hyperlinks where the website post title is implied and not explicit.
• Prints list of self-answered questions that were not accepted after the mandatory two day wait period.
• Prints list of Rouge Syntax Highlighting languages not supported in fenced code blocks.
• Prints summary totals when finished.

Full documentation is provided here.

This is what program looks like when running:

From what I understand, Ruby moves all stdlib parts into gems, some are "default gems", as in, they are normally installed with Ruby and don't need a reference in your Gemfile, but some are "bundled gems" which also are installed with Ruby, but need a reference in Gemfile. The problem stems from a fact, that with every Ruby release, some "default gems" become "bundled gems".

Such a situation happened with webrick in the past.

In your case it's most likely that you need rexml, which just became a "bundled gem" in Ruby 3.0: https://stdgems.org/rexml/

All this about a theory, but a solution is pretty simple. You just need to do

What I would suggest is to ensure that your GEM_PATH contains the path that you have set in your GEM_HOME variable. Myself, I have those environment variables which work all the time:

The solution was to surround the footnote in a

block with the markdown argument.

I ended up using task list which gives a handy progress indicator of work which shown as a checkbox.

I had the same problem and I found a workaround here at https://github.com/jekyll/jekyll/issues/8523

Add gem "webrick" to the Gemfile in your website. Than run bundle install

At this point you can run bundle exec jekyll serve

For me it works!

In ./_includes/pagination.html it tells pagination where to navigate when going to newer posts. By default this is set to / which works when your blog posts usually are. I simply changed this to /blog.

The full change can be seen here: https://github.com/bgigurtsis/blog/commit/72f6210518551b8983a27ef2bf44bf67028b6b4f

Azure Devops Pipelline Jekyll Build Failure

If you are using the private agent, please try to following steps to resolve this error:

• Running bundle info kramdown will give you the path to where kramdown has been installed.
• Run gem env to get an insight on all paths Ruby is concerned about.
• If the directory where kramdown got installed from above isn't listed in the gem env output, you'll have to manually add that path

If you are using the hosted agent, please try to reference following suggestions：

Add gem "webrick" to the Gemfile in your website. Than run bundle install

At this point you can run bundle exec jekyll build

Thanks to jonrsharpe comment, I reoriented my searches and found this blog post on heroku engineering blog. Eventually, as stated by jonrsharpe:

The Nginx buildpack won't have Ruby in at all - you need to do any building in the Ruby buildpack context, so all the static buildpack needs to do is serve the results.

Therefore, to launch my middleman build command, I needed to hook somewhere in the ruby buildpack thing. And in the "jekyll on heroku" link, everything is explained: one should override the assets:precompile rake task.

1. Add gem "rake" to my Gemfile (and bundle, of course)
2. Create a Rakefile with the assets:precompile task :