Home

Going Forward:

This page covers transitions from the existing 2.0 branch to the desired feature set. It does not cover separation of the blogging platform from my personal blog. This should be something considered during the 2.0 build, but may not need to be a feature.

Post & Page Separation:

These two objects are extremely similar and possibly should be combined into 1 object. This contains an enumerated list of features that I want for both pages and posts, requirements to merge objects, as well as future considerations.

Current Features:

	Page	Post
Publishing	Live once saved	Click to publish
Input Interface	HTML	Markdown converted to html
Categories	No	Yes
Appear in feeds	No	Yes
URL Slugging	Yes	Yes
Forced Dom	Just in section	Additional classes on section

Thoughts On Current Feature Set

Page HTML Restriction

This was originally designed to give me more flexibility in designing pages. I've found that pages are a small portion of my site and are something probably better suited to markdown.

Forced Post Markdown

I write my blog posts in markdown so this forced rendering makes sense. I like markdown because it's not tied to HTML and does not define any style. However, I think there comes a case where I'll want to be able to "edit" generated HTML to add some key feature.

Page Publishing

Page auto publishing is probably something that should be re-visisted. I may want to design a page and have it sit for a bit until I replace an existing page or publish the current page.

Forced Dom

I like having a "default" dom structure that can be used, however I'm wondering if that makes most sense for current expansion. I think a better solution would be templates. User's should be able to select a template for their post or page. THe template would declare the dom structure.

Possibly Updated Feature Set

	Page	Post
Publishing	Delayed Publishing	Delayed Publishing
Input Interface	Markdown to Html or HTML	Markdown to Html or HTML
Categories	No	Yes
Appear in feeds	No	Yes
URL Slugging	Yes	Yes
Forced Dom	Template	Template

With this new feature set the only difference is categories and feed. Pages could obviously have the link to Categories, but not have it exposed anywhere. Then appears in feed could be a boolean flag that is set my default. Though pages and posts would look different in the UI the backend would treat them the same.

Features Going Forward

• Post Series. I'd like to see posts link to each other and pick the post that it should link to. This would be better for posts that build off existing posts or 2 or more posts that follow a given tutorial e..g: "Lets build a blog in laravel".
• Omit home feed. My blog mainly focusses on tech, but I'm thinking of building out posts that are not related. I'm unsure if I want these posts to land on the home page or to be relegated to direct linking or found under series of posts.
• Metadata. I want to build out a blogs for my hikes. I'd like to include slide shows and maps of the hike. I may also want to build out a recipe section for the blog as well, though mainly to illustrate a need to abstracting the ideas here. I think the best way to handle this is by using a type column on the post. The type will allow us to join specific meta data columns and when combined with template should provide all the required flexibility.