To import posts into WriteFreely from an outside platform, it is ideal to get all articles into a JSON document that looks like the following, where each object in the array is a complete article:
"title": "Optional Post Title",
"body": "Entire post content, in Markdown or HTML, including any images and #hashtags.\n\nNote: newlines should be preserved in this field, even when using HTML.",
These field names map directly to the API — you can read details in the API documentation. Otherwise, a few notes:
The slug should contain only alphanumerics and hypens. Any invalid characters will be automatically converted.
The body property should include all original markup (HTML) and Markdown, with newlines (WriteFreely respects and requires newline literals). Note: Getting as close to Markdown / plain text as possible here is ideal, as it provides the best editing and data export experience. But WF will render HTML.
Include any categories or tags as #hashtags, inline in the body. To make it look nice, you might append any to the end of the post, separated from the post body by \n\n.
Supply a created time, in the RFC3339 format (shown above) and converted to the UTC timezone, to preserve original publish date and time.
In this format, we can trivially loop through the array of objects and POST each one directly to the WriteFreely API — creating either drafts or blog posts.
Right now, we have a pause on major features in WriteFreely. I've finally started to work through the backlog of outstanding pull requests, some of which were from mid-2019, and now am getting to more of the polishing side of things. So coming soon, there will be some small new visual changes in WriteFreely / Write.as, particularly that affect user blogs.
Dates on blog posts. It's been missing for years. They'd show on the blog home page, but not blog posts. Well, this is no longer the case. Soon, posts on blogs that use the Blog display format will consistently show dates both on their home page and individual posts. Other display formats will continue not showing dates, because that's exactly what they're there for: not showing dates.
Also, dates are now correct, relative to your device's timezone!
<table> style. These elements were previously unstyled. Now they'll have some improved, basic styling that you can easily override with custom CSS. See #194.
Consistent user page headers. User pages (Blogs, Drafts, Account Settings, etc.) were all over the map with their headers. I'd start using a new style on new pages and not update the old ones. Well, now that's fixed in #262. Write.as users will notice this change is already live.
Slightly more line height. We've added 10% more space between lines of text. It's perhaps too small to really notice, but large enough to make a nice improvement. Changes in #263.
On the admin side, we're redesigning the dashboard to make it much more user friendly, and optionally less technical, in cases where an instance is in a hosted environment and the admin doesn't care about getting into the weeds. See #264. We need this change in Write.as for Teams, but it should also prove helpful for other WriteFreely hosts.
Particularly since these are visible changes that affect users, we want your feedback! Please jump into those pull requests on GitHub, try things out, and let us know what you think. We want to be sure people are happy with these upcoming changes before they get released to everyone.
Dates on this blog should now be correct to your current timezone. This post is set as published just a bit after midnight UTC, so it should change to the day before (January 28) for anyone in the Americas.
Dates on this blog should now be correct to your current timezone. This post is set as published just a bit before midnight UTC, so it should change to the day after (January 29) for anyone in Europe, Africa, Asia, etc.
A recent idea I had: what if WF federated Notes instead of Articles in certain situations? I just tweaked this instance so that if there's no newline in a post, it'll come out as a Note. Otherwise it'll be an Article, like normal. Thoughts? Reply to @email@example.com.