You can now create static pages by adding the attributes :hp-type: page in your post.

After saving, it will generate a file in the folder _posts/{title-slugify}.adoc or _posts/{hp-alt-title-slugify}.adoc if you use the attribute :hp-alt-title:.

After publishing, it will generate an html file at the root of the repository.

You can now add entries in the navigation of your blog. In the Settings panel, there is a new tab Navigation:

Then entries will be available in the published documents:

We added a new preview with the content of the generated HTML document for the selected theme:

And you can display it in full size with the button:

There is a new field in the HubPress tab of the Settings page name Blog path:

With this field you can specify the path where the pagination of your posts will be generate. So you can now create a page with the title index (or :hp-alt-title: index) that will be the home of your website. Then you can create an entry in the navigation that will be link on the pagination path.

Here is the navigation for our website:

We added two new entries in the Social network tab:

Actually these entries are only available in themes Casper and Ghostium

The theme Casper has been updated. This version is really beautiful and really comfortable for reading.

This theme is developed by the team of Ghost and sources are available here https://github.com/TryGhost/Casper

Now HubPress use Nuxt.js instead of using an homemade build. It will increase the stability of the build and certainly make contributions easier.

We have also integrated Loki.js in our stack to replace PouchDB

Because donation is not the only way to help an opensource project, we made a page which list some kind of contribution:

https://hubpress.dev/contributing.html

Also we are now on Open Collective!

We still have to define tiers, but if you want to help us with donations and become one of our backers or sponsors, Open Collective is the right place to go.

We wish to thank all those who have supported us since the beginning of the project.

A big thank to Peter Lawrey for having backed us.

You do not need to change the config.json anymore, now you can do it with the Configuration form. This form appears when the configuration of your repository is not done. You have to set the mandatory fields (username, repository name and the branch) and the domain name if you have one.

Click on the Ok, let’s go! button and you will be redirect to the login form. Then login and the configuration will be save on your repository.

That’s it!

Some of you wanted to have a dark theme so we added one. You can now use the theme the-shell in your settings, here is a sample of the result with my personal blog:

We have fixed a bug on the generation of tags, thanks to Krzysztof Zbiciński @zbicin.

We have also fixed the highlighting of code blocks, here is a example with the theme casper:

For the next version, we hope to add the static page feature and why not the sitemap generation.

As usual, if you love HubPress, we’d love to hear why you love it. Why not show your love by sharing this post, or perhaps consider donating through PayPal or Gratipay to HubPress.

And if there is something about HubPress you think we can do better, tell us! We can only improve the tool if you open feature requests in GitHub.

Thanks for using HubPress, and keep sharing!

The biggest addition to this release is the Gitter support chat integration, and dramatically improved posts synchronisation and publishing times.

We’ve made some other changes that you’ll see in 0.7.3, but these were done before this release.

Here’s a summary of those changes.

It’s been two years since HubPress started as a proof of concept. It is now used by over 1000 users worldwide to maintain their blog presence on the internet.

A recent review of the fork statistics of HubPress revealed that a staggering 764 users have set up the product and written at least two posts with our little tool. There are 261 of you that have written at least 5 posts. Congratulations!

If you love HubPress, we’d love to hear why you love it. Why not show your love by sharing this post, or perhaps consider donating through PayPal or Gratipay to HubPress.

And if there is something about HubPress you think we can do better, tell us! We can only improve the tool if you open feature requests in GitHub.

Thanks for using HubPress, and keep sharing!

RSS feed is now available at the url <url_of_your_blog>/rss! It is rebuild when:

In the past we have removed the RSS link on each theme because RSS was not available, themes have been updated and links are here.

You can find a new item in the main menu, Check for upgrade:

It will redirect you to GitHub and you will be able to upgrade your instance in the right way.

We also have added the version add the bottom of the main menu:

We have fixed two bugs:

We hope you enjoy this new release. If you have any ideas for features, or see a problem with this release, we would love your feedback!

First, make sure that you have saved all your blog posts. Every unsaved draft will be lost because we have changed the storage system in this version.

To upgrade your instance you have to create a pull request on your repository. Go to:

For example for our blog, the username is HubPress, the repository name is blog.hubpress.io and we use the branch gh-pages, so the url is:

If you use the branch master like Jared does (his username is jaredmorgs, the repository name is jaredmorgs.github.io):

Then you have to create a pull request with the listed changes and merge it.

The last action is to log into your HubPress administration console. Go to the Settings page and Save. This action rebuilds all your blog posts with the improvements featured in this blog.

And voilà!

Release 0.4.0 added two new themese: ghostium and uno-zen.

What we noticed is that the theme folders used a mixture of upper and lower case, which made it tricky to set the theme correctly in the Admin console.

In 0.5.1 all theme names have been changed to lowercase. This is breaking change, and you will need to check that the theme you’ve chosen in the Settings are lowercase.

Refer to the folder names in the /themes folder in your repository, or in the Administration.adoc Admin Guide.

Technically, HubPress already allowed to you set a collaborator on your repo so more than one user could write posts.

What HubPress didn’t do was honour the post creator (author) if the settings were changed, and the site was regenerated.

With 0.5.1, if you write a blog post, your GitHub user name will always be attached to the post.

If you create a blog post, then another blogger on your team publishes it, the person who originally created the post is credited with writing the post.

In a future release, we plan on enhancing how writer attribution is handled in the post, so stay tuned.

With the 0.5.1 release, the author page is now available!

The author page regroups all the posts for a specific author.

Here is an example from our blog:

You no longer have to "delete" blogs posts by reusing an unwanted, unpublished blog post.

The action overflow (three dots menu) next to each of your posts now has a Delete button.

Previous releases required you to reauthenticate in the HubPress Administration Console to synchronize your local content.

With the 0.5.1 release, we introduce the Synchronize button:

Solarized is now the default theme for the editor, you can switch easily between light and dark with one button:

You can now use includes in your AsciiDoc content:

Developers use gist to store code snippets, and with 0.5.1 you can now use the gist macro to integrate those snippets in your post.

For example with the gist https://gist.github.com/anthonny/7786310 the usage is as follows:

In versions prior to 0.5.1, if you didn’t have a Level 1 heading starting your blog post, you were not able to save your blog post. The error that displayed as a result of this was not clear, which caused frustration for some users.

In 0.5.1, the editor now has basic validation built-in. If you don’t start your blog with a Level 1 heading, there are no Preview or Save buttons in the editor. This is a visual clue to check your blog structure.

If you want some tips on writing successful blog posts with HubPress, check out the Writers' Guide in your repository.

The documentation for HubPress has undergone further improvements to better align the content.

The Administration guide has had a content shuffle to remove information that should have been in the Writer’s Guide.

The Writer’s Guide had some stray Administration content in it, which has now been moved into it’s proper home.

Check out the docs and let us know if you see room for improvement.

Look out for the HubPress docs you see in your forked repository on https://gitbook.com in the very near future.

GitBook are huge supporters of Open Source projects, and make managing documentation for your project or your organisation easy. The team has been very generous in offering HubPress an Open Source license to use for our GitHub organisation.

This allows Jared to separate documentation updates from code releases, and allows you to make in-line comments directly on the hosted docs. No Pull Request required. It’s an easy way to provide quick feedback on the documentation, so the team can make improvements in rapid iteration.

Jared will migrate the user guides currently in your repository over to https://www.gitbook.com/@hubpress/ and will re-align the README.adoc with links to these new resources.

HubPress is now on Gratipay!

It’s not the only way you can help us, but it is certainly a welcome one. Donations are a great way to show your appreciation for the platform: it inspires us to dedicate extra time away from our families and day jobs to make HubPress an awesome blogging platform for you.

To give HubPress a modern, progressive User Interface, we’ve redesigned it using the Material design template.

This provides an even better responsive design for mobile users, and provides a clean interface for new and existing bloggers.

HubPress is moving away from developing in the hubpress.io repository. To ensure the hubpress.io repository remains clean for new adopters, development has shifted to dev.hubpress.io.

The process to commit a change to HubPress is changed to the following:

Once we receive your PR, we’ll review your changes and then either accept them or ask for further changes before final acceptance.

The new repository is backed by Continuous Integration tasks provisioned through Travis-CI, which trigger automatically once a change to /development is detected.

It’s a more scalable way to manage HubPress moving forward.

HubPress uses the professional-looking Ghost themes to allow you to personalise your Blog. It’s been a year since release, so it’s time for a couple of new looks.

The documentation for HubPress has undergone a bit of a face-lift as well.

The README.adoc was becoming more of a User’s Guide and less a terse overview about getting started with the product.

For this reason, the documentation has been separated out into the following documents:

Further improvements to the HubPress documentation set are planned, including:

If you see an improvement to documentation that requires action, follow the Development process steps above.

HubPress is now on Gratipay!

It’s not the only way you can help us, but it is certainly a welcome one. Donations are a great way to show your appreciation for the platform: it inspires us to dedicate extra time away from our families and day jobs to make HubPress an awesome blogging platform for you.

When you logon to HubPress, a personal token is created in your GitHub account. With version 0.3.0, the personal token is now generated according to the environment (Browser and Operating System), and is deleted at each login:

The consequence is that you can no longer have multiple tabs in the same browser open to work on your HubPress blog instance. You can work around this issue by starting two instances of HubPress in different browsers, or by accessing your posts through the GitHub user interface in your blog repository.

If you have never upgraded your instance of HubPress before, follow this tutorial to update your version before 20 April 2015.

While testing the release, The Docs Guy found what appeared to be a rogue commit on config.json on 12 March 2015 by hanwengchen (one of the community translators) that appears in the /master branch. There’s nothing to worry about: the change was reverted later in the commit for the release. You can upgrade with confidence.

A full list of other notable changes can be found in the CHANGELOG.

As the README has grown with HubPress, I’ve noticed that some content (embedded videos in particular) in the README just can not be displayed nicely. This is due to some limitations in the way GitHub presents Asciidoc rendered content. To be honest, README files are really only designed to contain the most basic of instructions, which can help a new user become familiar with the resources available to them in a project. To fix this problem, HubPress needs to present the documentation in a format that is better suited to more traditional user documentation, and leave the README as a launch pad for new users.

I’ve been experimenting with JAQ, which is a continuous docs build system John Ericksen and members of the Asciidoctor Project created. This forkable repository was originally created to be a quick way to set up an Asciidoc Blog without all the complexity of Jekyll. Of course, when the Asciidoctor team saw just how amazing HubPress was, we needed a way to repurpose the project. I approached John because I was looking for a way to easily host Asciidoc User Guides on GitHub, without having to use a PC (I am always on an Android tablet, but only use a PC for work). John made some changes to JAQ which allowed the project to be used as a continuous build system for Documentation. To show you that it works, here is the Asciidoc guide I created voluntarily for FarSight Studios The Pinball Arcade on Android.

As you can see, the presentation you get with JAQ looks professional and is mobile-friendly. Furthermore, as a docs contributor you don’t need to install anything to update a user guide except for a web browser. This is because JAQ uses Travis CI to build the book every time a commit is detected on /master.

Now you’ve read my ideas, go ahead and give your feedback in HubPress Issue 153. This is a community effort, and no idea will be dismissed as long as it is constructive.

Most users of HubPress are tech bloggers and find themselves writing many command-line examples in the blog posts they write. Code Highlighting is now implemented in HubPress.

If your native language does not use latin characters, you can now specify an alternative title that is used to build the URL of your blog post.

This feature is enabled through a new attribute hp-alt-title:

The URL format of the post is http://myblog.com/2015/03/15/please-test-it.html and the title in the blog post remains as テストをしてください

No more 404 on the tags link! Tag page generation is now available. Tags pages are built when you publish a post and the site is re-paginated. It may take a short while for the tag cloud to update on your site.

Our documentation is now available in Chinese and Spanish: thanks to our dedicated community contributors!

You can find all changes in the CHANGELOG