Wren - README.md

Wren is a web-based, static site, blog tool. It requires the user to create most of the features that would be automatically created in "normal" web publishing apps.

For example, the homepage is not automatically generated. index.html in root directory and in sub-directories get created and update like any other post.

The same applies to archives and tag-related pages. It's a slower way to produce content, which may mean staying more focused and writing when having something important to create, instead of saving ev

It has an API, which can be accessed with command prompt utilities or curl. I'll need to finish creating the command prompt utility, and enable the API to support preview when access has no authentication.

For logging into a Wren site, it uses a no-password login mechanism. The author submits an email address, and the login activation link is emailed to the author. The app uses MailGun.

Text can be formatted using Markdown/MultiMarkdown and HTML commands.

Here's a test site that uses posts that I created elsewhere in the past:

• http://wren.soupmode.com

I'm also using Wren to store updates about my Dad's cancer treatment at:

• http://dad.soupmode.com

For search, I will rely on using Google and/or DuckDuckGo.

I need to add support for writing with the JavaScript editor that I have enabled with my other web publishing apps.

To access the markup text version of a post, replace ".html" at the end of the URL with ".txt".

Wren maintains a list of all links in a file called links.json. Wren uses this file to create rss.xml, sitemap.xml, and mft.html.

mft.html lists the most recent posts in an HTML file that uses microformats. Some Indieweb users prefer to syndicate their content by marking up their HTML files with microformats. Parsers would read a user's homepage to create a feed to be read by someone else, instead of accessing a user's RSS feed.