Skip to content

Instantly share code, notes, and snippets.

@clatwell
Created June 20, 2017 20:45
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save clatwell/6fb92f720d94dca01a386bfdcf7c4935 to your computer and use it in GitHub Desktop.
Save clatwell/6fb92f720d94dca01a386bfdcf7c4935 to your computer and use it in GitHub Desktop.
[PHVN] Features and Maintenance

Features

This is the primary list of things we hear about and also think would make sense for Posthaven.

  • Import from other blogs sites – primarily Wordpress a few requests for Tumblr and Medium
  • API – Primarily requested for blog post CRUD
  • Markdown support both in the online editor and when posting via email
  • Other types of payment than via credit card
  • Annual instead of monthly payment
  • More built-in themes
  • Search for posts on the dashboard
  • An option to moderate comments before they go live
  • “Remember me” for passwords on private sites (i.e. allow users viewing via the site password to have persistent sessions so they do not need to enter the password every time)
  • HTTPS everywhere. This is mostly supported but when I turned it on briefly a user complained that his external HTTP media stopped loading, so it would need to be updated to be opt-out (or opt-in).
  • Full HTML export. We currently support Wordpress export but there has been a little interest in being able to export a full static version of a Posthaven site. This is something I’ve considered because it might also be useful internally because we could possibly host sites in archive mode independent of the Rails application to save on costs.

Our theming release last year helped with many common requests. We still get look and feel requests and the answer is most often “it’s advanced functionality but possible via a custom theme”. Most often those types of requests are individual to the user instead of part of trend.

Maintenance

The tasks that are on my radar right now.

  • Upgrade the version of the Facebook Graph API we’re using before its end of life
  • Upgrade to the new Box View API before EOL of the old one
  • Upgrade Rails – This one is some work and more nice to have. We’re on 3.2.* which is not officially supported but is widely enough used that community has consistenlty back ported security fixes so far.
  • Reduce or purge use of the Embedly API. Also more nice to have. We use them for auto-expansion (i.e. a user can paste a URL into a post on its own line and we replace it with embedded content from that URL0. They are flakey and keep chaning their model, but not needed for most of the URLs we support.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment