Introducing the Editor stack for Alloy
For quite some time now I've wanted an online blogging solution for RapidWeaver. With the initial release of Alloy I got really close to what I wanted for such a blogging tool -- something that is easy-to-use that and is a flat-file system based around Markdown and YAML.
With the release of the free Alloy v2 update blogging with RapidWeaver is made even easier, as I've added a new stack that will help you to create an online backend for your blog, allowing you to create, modify, delete and backup your blog posts right from your website.
While Alloy v1 made blogging relatively simple and kept us all from having to deal with databases or other complicated setups it just wasn’t enough. While it made maintaining your blog easy, it did ask users to upload and manage their posts through FTP software on their server. This meant making sure your blog posts were named just right as well as it meant creating the YAML front matter for each post as well.
Alloy v2 though keeps you from having to do any of that, and makes managing your posts a breeze! Alloy now includes an Editor stack, which is used for building your own online, backend for your blog. It helps you setup a secure login for your backend, as well as a create a page where you can create new posts, edit and delete existing, draft and future posts, as well as download a backup of your entire posts folder.
We’ ve got a couple of video tutorials to walk you through setting up the Editor stack, which can be found on the Alloy Tutorials page, in addition to the main Getting Started video, and much more! I have embedded the two Editor stack videos below, but be sure to check out the Getting Started video on the Tutorials page as well if you’ve not yet setup a blog using Alloy.
In the first video we walk through how to setup your secure login credentials for your blog’s new backend.
In part two of our Editor tutorial we look at how to use your newly setup blog backend for creating, modifying, deleting and backing up your posts.
In addition to the new Editor stack you can still continue to maintain your blog using your FTP software just as you could in Alloy v1. You still create and maintain your posts in the same way you did before. In fact you can do so even if you’re using the Editor stack. This makes maintaining your blog very versatile, allowing you the flexibility to do so as you wish. We also still offer videos on the Tutorials page detailing how to use your FTP software to manage your blog if you’re interested.
The Editor stack will truly make managing your site’s blog so much more enjoyable!
We hope that everyone enjoys this major update to Alloy and has fun creating and maintaining your blog!
This Update is Free
Also, don’t forget — this upgrade is a free update for all existing Alloy users. If you’re not already an Alloy user, keep in mind that you can use Alloy v1 and v2 on an unlimited number of sites. As always, while this version of Alloy is good for an unlimited number of domains, we ask a small donation of just $10 for each domain past 3 that you will be using Alloy with. This will help us with developing Alloy even further and adding more functionality and features. You can find the Extra Domain button on the Alloy Purchase page if you’d like to help out.
You can learn more about Alloy on its dedicated site, as well as watch a variety of tutorial videos on the Alloy Tutorials page. There is also a documentation page specifically for the Editor stack if you’re interested in its controls and settings.
In addition to the Editor stack’s addition I’ve also made several tweaks and enhancements to Alloy’s code, as well as fixed a couple of smaller bugs. I’ve also added a new Time Zone setting, allowing you to select your local time zone. This will aid in getting Future Dated Posts to show up on the site when you expect them to.
I’ve also written a blog post touching on a quirk I ran into with Stacks’ page-wide variables, which Alloy uses for some of its settings. In this blog post I talk about what this quirk is and how we as a group should look at working around it for the time being.