HTML :html-head, ( blog-read-layout-file ' head ) :html-postamble t Disable some Org's HTML defaults :html-head-include-scripts nil :headlinevels 4 :html-toplevel-hlevel 1 :with-email nil Extra :language "en" :section-numbers nil :html-doctype "html5" :html-html5-fancy t HTML5 :html-extension "html" :htmlized-source t :html-link-home "index.html" :html-home/up-format "" :recursive nil ( setq org-publish-project-alist ` ( ( "org" :base-directory, ( blog-getconf :src ) :base-extension "org" :publishing-directory, ( blog-getconf :out ) :exclude "README\\.md \\ | LICENSE \\ | \\.gitignore \\ | rss\\.org" :publishing-function org-html-publish-to-html Is like having hugo or jekyll directly intergrated into your text editor, plus you can customise the text transformation and the page generation. The generated website uses only html5 and css, but you can extend it as much as you want, adding js or other features. Third is because is so simple to just write a post, build and push the repository all directly from Emacs that no other solutions I’ve tried before can emulate. Second, since Emacs is highly customisable, I created my perfect writing setup combining extensions like olivetti-mode, using the ETBook font, a dark theme and disabling some features like line numbers. With org you don’t need to do that, just use one of the multiple templates offered by the language. Markdown is quite limited and the standard way to extending it consists of using directly HTML, which means adding another markup language. I think it’s way more powerful than the standard markdown since it supports more features 1 with a lot of customisation and functionalities thanks to Emacs. But for Emacs users, extending it is for sure the funniest part.įirst, I like writing using the org markup language. The initial configuration can be challenging if you’re not comfortable with Emacs customisation using elisp. Is a preset configuration that has all included to start with. If you never used Emacs before, you should try Doom Emacs. For now let’s have a look at the Emacs configuration that I used. This blog is auto deployed by just updating the repository, I’ll speak about that in a future article. Push the public/ folder to the git repo using magit.Run the build process with M-x org-publish and selected blog-publish.Save the post in the correct folder C-x C-s.Create a new org-mode buffer with C-x b and write the post.This are the steps I’ve follow with Emacs to write and publish a post: I wrote and converted it to a webpage using Emacs and I will talk about how I configured my favourite editor to make as simple as possible publishing a blog. That’s exaclty the number of steps it took me with this article. How simple should be writing a blog post for a developer? I would say 4 passages write, save, build, publish.
0 Comments
Leave a Reply. |