Here is the actual version of my eBook compiler, adorned with cowsay user feedback.
Why don’t you save the long pandoc command lines as a bash script?
In this project I write in Markdown most of the time. I may need the same text in many formats:
- .docx for the boss
- .pdf for nice presentations
- .tex for serious work
- .epub for ebooks
- .mobi for Kindle
In order to create an Ebook and a Kindle version, you need to:
pandoc myText.md -o myText.epub
Kindlegen will create a file with the .mobi extension: myFile.mobi. That’s it. Your book is ready for Kindle.
Here’s a list of pages, that I tend to use over and over again:
- Daring FireBall: Markdown.
- Using Pandoc to Create Your ePub eBook.
- The best tutorial: Creating an ebook with pandoc.
- How We Automated Our Ebook Builds With Pandoc and KindleGen.
Let’s try a conversion from Markdown to an eBook. The –ebook-cover will ad a frontpage. So you’ll have an eBook with a nice cover. The –toc means Table of Content.
pandoc -s --epub-cover-image=owl.jpg --toc meta.txt markdown.md -o x.epub
As you progress the pandoc commandline tends to become very long indeed. I save such lines i as a bash script. Here’s a sample:
# Create the eBook and a Kindle version of the same
pandoc -S --epub-cover-image=owl.jpg --toc -o yourBook.epub meta.txt markdown.md
Save the file as myFile.sh. Then run this command: chmod a+x myFile.sh. Now you can run the entire command like this:
in a terminal. As soon as your pandoc command works you can save it for future use. You could even save the script in
Then you can use your script as a Linux command.
I’m sure that you can do something similar in Windows or OSX. In the heyday of MS DOS I might have saved the pandoc command in a .bat file. But in the end I prefer a Linux solution.
– By thine own ingenium create your solution …
In this blogpost by Mike Schroder you can see, that WordPress will have better PDF support from WP 4.7.
However, the PDF support needs several dependencies:
Core support is provided through
WP_Image_Editor_Imagickand requires Imagick, ImageMagick, and Ghostscript support. When not supported, or if the generation fails, WordPress falls back to previous behavior and saves the attachment without adding image previews to meta. (Quote: Mike Schroder Nov. 15th. 2016)
Inspiration from Yeat’s “A Vision”
In 1925 the nobel prize winner and author W.B. Yeats published “A Vision”. Here he introduced the dichotomy of Primary and Antithetical. To Yeats there is an opposition between Primary and Antithetical thinking.
We could draw an analogy. Connect Primary with “Drag and drop production”, and Antithetical with “Focus on code / database”. Then you’ll get a suggestive illustration.
Now the extremes would be rare. But you could perhaps imagine a user, that does not understand any code at all. Everything is done via drag and drop. Would such a user be able to make a professional webpage. My answer is clearly: yes.
You could also imagine a user who does not care for the GUI at all. Everything is PHP or SQL to that user. Such a user could build new funcitonality on the core functions of WordPress. Writing code for the sake of code would be possible. But it’s absurd.
Most users are somewhere in between. The more you work with WordPress development, the more you’ll be dragged towards the code side.
The more you can accomplish with a content management system without having to write code, the better it is. But the human race is creative. We often seek something new.
And so the primary drag ‘n dropper depends on the coder – and vice versa.
In my research project I have seen very good multimedia productions with hardly any code. But if your vision transcends the limits of the out-of-the-box WordPress – then you need a skilled coder.
How to use the model
You can use the model in order to visualize the complexity of a WordPress task or solution. Let’s use a Child Theme as a sample:
A Child Theme will use a given theme – and elaborate on the code. The developer will have to write some code. Depending on the amount of added functionality, widgets, plugins etc. we can place the dot.
In this way we can use the original model by W.B. Yeats in order to visualize the complexity of a WordPress solution.
Another sample: install and use a new theme via the dashboard:
The model is a visualization of the balance between code and user. Usability is the raison d’être for code.
Nick Halsey made a usability test on Twenty Seventeen. See the results here. The method seems to be observation of usage and notes during the test. Four users tested the new theme. According to the web guru Nielsen you could find around 90% of the usability errors in this way.
Why you should know WordPress?
Have a look at the statistics. WordPress powers 25% of the web.
Why should you know anything about WordPress? Because it powers 25% of the web. In a not so far future WordPress may power more web pages than the home-hacked ones.
The illustration above demonstrates the present power of WordPress. The green line shows websites that don’t have a CMS. Perhaps they’ve hacked their own system. Who knows what they did.
The rising red line at the bottom of the graph is WordPress. You can see, that the line rises. The red line is what is happening out there. WordPress powers more and more web pages.
The many lines at the bottom of the image are all the other CMSs. As you can see the competition is almost nil. WordPress may not be the best CMS out there. Perhaps one of the geeky CMSs used by 0.00001% may be far better.
Knowing WordPress equals knowing content management. So here you have the statistic argument for knowing WordPress.
If you want to try the new version of WordPress the Beta Tester Plugin is a must. However, don’t run it on a production server! After all a tester isn’t stable.