A clean, Markdown-based publishing platform made for writers. Write together and build a community.
Newsletters / subscribe by email (https://github.com/writefreely/writefreely/pull/478)
Now readers can subscribe to receive blog posts via email! Connect an email service to enable email subscriptions and automated password resets (https://github.com/writefreely/writefreely/pull/777). Admins can enable this with the new [email]
section in their configuration file -- see the documentation for instructions on setting this up.
Note: today, WriteFreely only supports Mailgun as an email service -- but our next release will support plain SMTP, so you can use any provider you want to.
View fediverse followers and email subscribers (https://github.com/writefreely/writefreely/pull/775)
For instances with federation enabled, authors can now privately see who is following them from the fediverse via the new Subscribers page. This page also shows everyone subscribed to updates via email, if enabled.
Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and then update it with:
writefreely db migrate
No additional steps are needed to upgrade from v0.14.0 or v0.13.x. Follow the instructions in each previous release if you're upgrading from an earlier version.
Thanks to everyone who contributed to this release of WriteFreely!
Full Changelog: https://github.com/writefreely/writefreely/compare/v0.14.0...v0.15.0
Fediverse verification (#771)
Verify that your WriteFreely blog on fediverse platforms like Mastodon! Simply go to your blog's Customize page under the Verification section, and enter your fediverse handle or URL. It will place an invisible tag on your blog, so the other platform can verify that the blog is yours. You can also insert a rel="me"
link in your blog bio.
Contact Page (#772)
Admins on multi-user instances can add a Contact page, so members and visitors know how to get in touch. Add your email address, fediverse handle, or any other method you want people to know to reach you!
static/local/custom.css
file (#533)Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and then update it with:
writefreely db migrate
No additional steps are needed to upgrade from v0.13.x. Follow the instructions in each previous release if you're upgrading from an earlier version.
Thanks to everyone who contributed to this WriteFreely release!
created
date when empty on publishNOTE: There is a blocking bug with our upstream tool, xgo
, that helps us cross-compile WriteFreely: techknowlogick/xgo#155. Because of this, we'll only release linux-amd64
builds for the foreseeable future.
Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
No additional steps are needed to upgrade from v0.13.0. Follow the instructions in each previous release if you're upgrading from an earlier version.
Thanks to everyone who contributed bug reports, code, and code review to this release!
@thebaer @StJudeWasHere @egon0 @gytisrepecka @lt3Dev @viasux @clausecker
/feed/
redirectdescription
metadata (#306)map_user_id
(#469)Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
No additional steps are needed to upgrade from v0.13.0. Follow the instructions in each previous release if you're upgrading from an earlier version.
If you are running a custom build: we made changes to UI components that need to be compiled. Run this to compile everything:
make ui
Thanks to everyone who contributed bug reports, code, and code review to this release!
@stayinside @bandicootdancing @PeterCxy @DaarkMoon @poVoq @Tealk @thebaer @mkyos
Classic editor (T727)
If plain text and Markdown aren't your thing, now you can get a more "classic" writing experience with the Classic editor! This features more of a What You See Is What You Get interface that doesn't require the learning curve of Markdown. However, behind the scenes, posts are still saved as Markdown, so you can always switch between the Classic and standard editor. Admins can enable this option by setting editor = classic
in the [app]
config section.
Gopher Support (T559)
Give your audience a old-school, lightweight way to read posts on your WriteFreely instance, via the Gopher protocol! Enable it with the new gopher_port
config value in the [server]
section. When it’s enabled, multi-user instances will show all Public blogs at gopher://[host]:[gopher_port]/
.
Gitea and Generic OAuth Provider Support (#293, #317, #405)
We’ve added more ways for users to authenticate with your WriteFreely instance, via Gitea or any generic OAuth 2.0 provider! Our generic OAuth provider support in particular gives you the chance to use WriteFreely alongside a range of applications that hold your users, from Mastodon to Nextcloud to Keycloak.
Web Monetization Support (T773)
Writers can now accept micropayments for their work via the proposed Web Monetization standard, and even publish exclusive content behind a paywall. Admins can enable this by setting monetization = true
in the [app]
section of their config, or changing the setting in their admin panel. This is just the start as we look to give readers more ways to financially support writers — read more about this on the Write.as blog.
ActivityPub Notes (#220)
Now, WriteFreely is more friendly to microblogs! If a post doesn’t have a double-line-break in it, it’ll be sent to the fediverse as a Note
, rather than an Article
. If you’d prefer to always send Notes, admins can set notes_only = true
in the [app]
config section.
Account deletion (T319)
It’s now easy for users and admins to quickly delete account data from WriteFreely via the web! Admins can access this option from their Admin Dashboard, and users can access it from their Account Settings page, if admins have configured Open Account Deletions (via the Dashboard or config file: open_deletion = true
under the [app]
section).
Post Signatures (T582)
This enables users to add a signature to all blog posts, and update it from a single location (the blog's Customize page).
GetCollectionRedirect()
(#318)slug
parameter when publishing a post (T811)url
property on Publish a Post endpointdescription
at user registrationwriteas
org to writefreely
(#451)Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and update it with:
writefreely db migrate
Finally, generate a new encryption key needed for this release (you can ignore messages about removing existing keys):
writefreely keys generate
No additional steps are needed to upgrade from v0.12.0. Follow the instructions in each previous release if you're upgrading from an earlier version.
If you are running a custom build: we made changes to site styles and added a Javascript dependency that needs to be compiled (prose.js
). Run this to compile everything:
make ui
Thanks to everyone who contributed to this release!
@gytisrepecka @thebaer @RJ722 @ketudb @pascoual @Dar13 @shleeable @joicemjoseph @dariusk @Obayanju @qwazix @Antolius @colin-axner @conor-f @VV-EE @mostfunkyduck @Dak425 @cjeller1592 @x4e @robjloranger
This is a WriteFreely v0.13.0 release candidate. It is intended to be stable, but may not be. Please open bug reports for any issues you find, and otherwise contact us via IRC (#writefreely on freenode) if you have any questions.
Classic editor (T727)
If plain text and Markdown aren't your thing, now you can get a more "classic" writing experience with the Classic editor! This features more of a What You See Is What You Get interface that doesn't require the learning curve of Markdown. However, behind the scenes, posts are still saved as Markdown, so you can always switch between the Classic and standard editor. Admins can enable this option by setting editor = classic
in the [app]
config section.
Gopher Support (T559)
Give your audience a old-school, lightweight way to read posts on your WriteFreely instance, via the Gopher protocol! Enable it with the new gopher_port
config value in the [server]
section. When it’s enabled, multi-user instances will show all Public blogs at gopher://[host]:[gopher_port]/
.
Gitea and Generic OAuth Provider Support (#293, #317, #405)
We’ve added more ways for users to authenticate with your WriteFreely instance, via Gitea or any generic OAuth 2.0 provider! Our generic OAuth provider support in particular gives you the chance to use WriteFreely alongside a range of applications that hold your users, from Mastodon to Nextcloud to Keycloak.
Web Monetization Support (T773)
Writers can now accept micropayments for their work via the proposed Web Monetization standard. Admins can enable this by setting monetization = true
in the [app]
section of their config, or changing the setting in their admin panel. This is just the start as we look to give readers more ways to financially support writers — read more about this on the Write.as blog.
ActivityPub Notes (#220)
Now, WriteFreely is more friendly to microblogs! If a post doesn’t have a double-line-break in it, it’ll be sent to the fediverse as a Note
, rather than an Article
. If you’d prefer to always send Notes, admins can set notes_only = true
in the [app]
config section.
Account deletion (T319)
It’s now easy for users and admins to quickly delete account data from WriteFreely via the web! Admins can access this option from their Admin Dashboard, and users can access it from their Account Settings page, if admins have configured Open Account Deletions (via the Dashboard or config file: open_deletion = true
under the [app]
section).
Post Signatures (T582)
This enables users to add a signature to all blog posts, and update it from a single location (the blog's Customize page).
GetCollectionRedirect()
(#318)slug
parameter when publishing a post (T811)writeas
org to writefreely
(#451)Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and update it with:
writefreely db migrate
Finally, generate a new encryption key needed for this release (you can ignore messages about removing existing keys):
writefreely keys generate
No additional steps are needed to upgrade from v0.12.0. Follow the instructions in each previous release if you're upgrading from an earlier version.
If you are running a custom build: we made changes to site styles and added a Javascript dependency that needs to be compiled (prose.js
). Run this to compile everything:
make ui
Thanks to everyone who contributed to this release!
@gytisrepecka @thebaer @RJ722 @ketudb @pascoual @Dar13 @shleeable @joicemjoseph @dariusk @Obayanju @qwazix @Antolius @colin-axner @conor-f @VV-EE @mostfunkyduck @Dak425 @cjeller1592 @x4e @robjloranger
ActivityPub Mentions (T627)
Enable more interaction with your posts by mentioning users on Mastodon, Pleroma, and other ActivityPub platforms! Users on instances with federation enabled can now insert @[email protected]
to mention someone. You might use this to write a long response to someone in the fediverse, or even mention your own microblogging account, so that replies to your blog post also notify you there, where you can continue the conversation.
New Admin Dashboard (T694)
We've redesigned the admin dashboard to be a little easier to navigate, and generally more user friendly. It now includes an overview of stats for your instance, dedicated pages for app settings and monitoring, and more details on what each configuration option does. We've also made it easier for admins to get to the "Invite people" page.
OAuth 2.0 Support (#225)
Now you can authenticate with your WriteFreely instance via OAuth! This is perfect for WriteFreely communities that are set up to accompany other platforms. We support three providers so far: GitLab, Slack, and Write.as.
Reader Filter Updates (#269)
Now the Reader will show the most recent 250 public posts, instead of only the last three months of public posts. This should be much more fitting for most WriteFreely instances.
Plain Text Import
Now you can import plain text files to publish them as posts on WriteFreely.
js
, jsx
, html
(#270)@context
fields to fix Friendica federation (#299)update_checks = true
in config/api/markdown
endpoint for generating HTML from MarkdownDownload the latest release for your operating system, from the files below. Then follow these steps:
writefreely
servicekeys
directory with the files from the archivewritefreely
service again.Now make sure your database is backed up, and migrate it with the steps below.
ALTER DATABASE writefreely CHARACTER SET latin1 COLLATE latin1_swedish_ci;
writefreely db migrate
No additional steps are needed to upgrade from v0.3.0 or later. Follow the instructions in each previous release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run the following command to generate the latest stylesheets:
make ui
Thanks to everyone who contributed to this release!
@thebaer @robjloranger @qwazix @yalh76 @ngerakines @techknowlogick @shleeable @nkoehring @paddatrapper @cjeller1592
@cjeller1592
@barbrastreisand @wakest @judges119 @laBecasse @misaka00251 @OliverViking @mrvdb @darddan @wiwie @annando
This is a WriteFreely v0.12.0 release candidate. It is intended to be stable, but may not be. Please open bug reports for any issues you find, and otherwise contact us via IRC (#writefreely on freenode) if you have any questions.
ActivityPub Mentions (T627)
Enable more interaction with your posts by mentioning users on Mastodon, Pleroma, and other ActivityPub platforms! Users on instances with federation enabled can now insert @[email protected]
to mention someone. You might use this to write a long response to someone in the fediverse, or even mention your own microblogging account, so that replies to your blog post also notify you there, where you can continue the conversation.
New Admin Dashboard (T694)
We've redesigned the admin dashboard to be a little easier to navigate, and generally more user friendly. It now includes an overview of stats for your instance, dedicated pages for app settings and monitoring, and more details on what each configuration option does. We've also made it easier for admins to get to the "Invite people" page.
OAuth 2.0 Support (#225)
Now you can authenticate with your WriteFreely instance via OAuth! This is perfect for WriteFreely communities that are set up to accompany other platforms. We support three providers so far: GitLab, Slack, and Write.as.
Reader Filter Updates (#269)
Now the Reader will show the most recent 250 public posts, instead of only the last three months of public posts. This should be much more fitting for most WriteFreely instances.
Plain Text Import
Now you can import plain text files to publish them as posts on WriteFreely.
js
, jsx
, html
(#270)update_checks = true
in config/api/markdown
endpoint for generating HTML from MarkdownDownload the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and update it with:
writefreely db migrate
No additional steps are needed to upgrade from v0.11.x. Follow the instructions in each previous release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run make ui
to generate the latest stylesheets.
Thanks to everyone who contributed to this release!
@thebaer @robjloranger @qwazix @yalh76 @ngerakines @techknowlogick @shleeable @nkoehring @paddatrapper @cjeller1592
@barbrastreisand @wakest @judges119 @laBecasse @misaka00251 @OliverViking @mrvdb @darddan
Announce
ing posts via ActivityPub (#212)id
property in collection posts ActivityStreams data (#214)Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
No additional steps are needed to upgrade from v0.11.x. Follow the instructions in each previous release if you're upgrading from v0.10.0 or earlier.
Thanks for contributing to this release!
@robjloranger @cjeller1592
Automatic SSL certificates from Let's Encrypt (T542)
It's now even easier to start up a WriteFreely instance with free, automatic certificates from Let's Encrypt. With the application facing the public internet (i.e. not behind a reverse proxy), you can set a few configuration values to have WriteFreely generate the certificate for you.
For new instances, choose Production, standalone > Secure (port 443), auto certificate during the interactive setup process.
For existing instances, set autocert = true
and tls_cert_path = certs
(see config documentation for more information).
WriteFreely Command-Line Interface
We've released our first official WriteFreely client along with this version: wf-cli
! This is a simple command-line-based tool for publishing to one or many WriteFreely instances. It's perfect for tech-savvy users who don't want to leave their terminal window or anyone looking to build WriteFreely publishing into their desktop writing workflow -- and it's available for Windows, Mac, and Linux.
<audio>
HTML element (#147)title
attribute getting stripped on <abbr>
elements (#184)make build-arm7
Accept: application/json
headers (not only Content-Type
) (#178)User Silencing (T661)
Now instance admins can silence problematic users to make their writing inaccessible to the world and prevent further publishing. This strikes a balance between preventing further abuse and making reversible moderation decisions, as users will still be able to log in to their account and access their data.
This is still experimental, as it needs more extensive testing. Please report any bugs you find and give us any feedback you have on this feature!
Reader-centric instances (T681, #157)
As part of our new Write.as for Teams service, we're experimenting with an alternative configuration for admins that want their site to be more focused on the collective work of its writers, rather than on individuals. It's meant for businesses, organizations, and institutions that want to create more of a shared blog than provide individual blog hosting. It sets the Reader view as the home page, uses blog templates with global navigation, and has hashtags search across all public blogs.
This functionality is not at all finalized, and subject to change drastically without notice. We don't recommend enabling this in your configuration unless you're merely curious or want to provide feedback (which we highly encourage!).
Download the latest release for your operating system. Stop running your writefreely
service, replace all files in your installation with the ones in the archive, and then start your writefreely
service again.
Now make sure your database is backed up, and update it with writefreely --migrate
.
No additional steps are needed to upgrade from v0.10.0. Follow the instructions in each previous #release if you're upgrading from an earlier version.
If you are running a custom build, note that there were style changes in this release. Run make ui
to generate the latest stylesheets.
Our v0.11.0 release featured a new regression that broke single-user instances, and taught us about the value release candidates -- something we'll start doing, going forward. There's no extra work needed to upgrade from v0.11.0 if you've already upgraded from v0.10 -- only your enduring support as we learn how to build good software goodly.
Thanks for contributing to this release!
@robjloranger @OddBloke