Heikki @ home

Loose leaves from my tree

From org-page to org-webpage

I started this blog last year using org-page. Quite soon the author announced that he will not be supporting the package any more, but continued adding commits to it. I found difficult to keep my blog working and regained partial functionality by moving to an older version from the git repository.

I now made a successful and relatively easy transition to org-webpage, a fork of org-page. Again, documentation is sparse and leaves much to code reading and experimentation to understand what is going on.

Git integration is gone

The major advantage seems to be that org-webpage supports multiple projects. Also, git integration has been removed. It is no longer necessary to commit blog entries to a source branch of the repository to have the engine to generate the HTML for the website into the master branch. It is not even necessary to have the code stored in a git repository.

The published website can be written into a user defined directory, or, in case of github export, will be written into ~/.emacs.d/owp-temp.d/ directory. The uploader is code is written as a bash script into file ~/.emacs.d/owp-temp.d/<NAME>/owp-uploader.sh that is have to be executed from command line.

While this adds steps to the procedure, it is more flexible. The documentation recommends using rclone for syncing the repo to one of the numerous cloud storages. There should be ways to bring all the functionality back within emacs for my specific usage of uploading the site to github.

I feel naked to have a project where my hard labour is not protected by git, so creating a repository for the source files was one of my first things to do.

Fixes from org-page to org-webpage

Since org-webpage was forked from org-page already in March 2015, some things I fixed a year ago in org-page needed to be fixing again. Thet were minor issues in generating the main index file and the navigation bar. Those patches were applied practically immediately by the maintainer "tomashu".

Development web server

It is possible to view locally the web site under development straight from the interactive publishing command owp/do-publication. It uses the pure lisp emacs-web-server that gets installed as a dependency from MELPA.

The new work flow

  • write
  • run test server
  • commit source, push to remote repo with magit
  • publish and push HTML to remote repo