-
Notifications
You must be signed in to change notification settings - Fork 70
Old: Roadmap History
Release the API, Ember and Multi-User projects as Ghost 0.5
See 0.5.0
Maintenance release with many new features
See Milestone History or the release post
Maintenance release, see 0.4.1
See Milestone History or the Release Notes
Maintenance & security release, see 0.3.3
Maintenance release, see 0.3.2
Maintenance release, see 0.3.1
See 0.3.0
See the Epic for an overview of the project, what was required and why. Additionally, see the issue backlog to pick up issues and monitor progress.
- To standardise the Ghost data API by introducing a standard format which closely matches JSON-API
- To introduce new API endpoints needed for Apps, Themes and other core parts of Ghost.
- To introduce permissions / access control across the entire API
- To produce structure documentation of each endpoint, the expected response and any errors that may result
The Ghost Admin will be rewritten in Ember.js as a full client side SPA, consuming the Ghost data API. This is a dependency for all features which depend on UI changes. This project was started several weeks ago, but has been put on hold so that everyone can focus on the refactoring work to the API which is a dependency if the Ember admin is ever going to work. We should be back to this project before the end of April.
See the Epic for an overview of the project, what is required and why. Additionally, see the issue backlog to pick up issues and monitor progress.
- To rebuild the entire Ghost admin in Ember.js
- To resolve as many UI bugs/issues as possible
- To create a framework for rapid development of user interfaces in Ghost
- To lay the groundwork to deliver significant improvements for mobile
- ?To introduce a more holistic solution for managing keyboard shortcuts?
Ghost will get the option to add multiple users, with differing roles and permissions.
- To make it possible to have a multi-user blog
- To ensure that the admin UI is safe from XSS and other security issues
- To improve the first run/install and introduction experience for users
Milestone 4 resulted in version 0.4.0 of Ghost.
Milestone 4 is the first milestone which is not only after the public launch, but also developed in the open allowing anyone to get involved. This means that Milestone 4 has a heavy focus on architecture, further improving the Ghost internals, making it easier to work with, and adding non-user-facing features that will help Ghost to grow new features quickly in the future.
We had also planned to make our Ghost Developer Tools, or the API for building Apps, available at the end of this milestone, so that developers can start building Apps to extend Ghost's functionality. This too required a focus on the Ghost internals and so has been moved to its own project in 0.5.
There are also a number of important enhancements and features we want to add to the publishing experience, to reduce user frustration wherever possible.
Getting Apps off the ground:
-
Proposal: Plugin Architecture Refactor#769
-
Post settings menu: published time#907 -
Add a warning message when leaving the page with unsaved post content.#1327(Solve data loss problem) -
Featured posts:#1111,#1112 -
Static pages:#969,#1329,Casper#39,#1350
-
Post Settings UX#1351[TOP PRIORITY] -
New cmd+enter shortcut to go to a new paragraph without modifying the current line#645 -
Improve image uploader UI#1356 -
[BUG] Wrong notification on updating post#1368 -
[BUG] Allow multiple underscores like: _________#1113 -
[BUG] Markdown bug: no new line inserted when quotes are used#974
Items which focus purely on the Ghost internals have been pulled out into their own category. Many of these are required in order to introduce required features and improvements.
-
Cache Control Headers#1470 -
Migration Refactor
-
Config & internal structure
Vast improvements to Ghost's test suite include: running unit tests against sqlite, mysql #921 and postgres (Allowed failure) #1555. Separating the test fixtures out from Ghost's installation fixtures #362, proper tests for the API #1189 and adding a code overage tool #361
The following issues don't really fit into any other major Milestone 4 category, but are still scheduled to get done in 0.4.
- Automatic Update Available Notifications #1464
-
In {{excerpt}} convert new lines to spaces#531 -
Added new helper to escape URIs called {{encode}}#1092 -
Create prefix and suffix attribute for {{tags}} helper#607
-
Enhancement: Remove "Insecure Content" warning for backend over SSL#1300 -
Replace cookieSession with session#1230
-
Limit login attempts#499 -
Improved password reset tool#1471 -
Account redirects#1472 -
[BUG] Signing in and then pressing the back button takes you to /ghost/signin/ instead of /ghost/#596
Bugs which don't fit into the categories above. PLEASE KILL THESE WITH FIRE.
-
Editing publish date of unpublished post yields JavaScript error#1332 -
custom partial/pagination.hbs not cleared on theme switch#1203
The work towards Milestone 5 has already delivered significant new features, bug fixes, and awesome infrastructural changes that make Ghost easier to work with. At the same time, there is a very long way to go still before we can deliver 0.5, and that is being extended because of the switch-over to Ember. Therefore the Ghost team has decided to take advantage of being pre-1.0 and deliver a patch release with new features.
0.4.2 will deliver many of the theme changes that were planned for 0.5, and some that were planned for 0.6! It will also fix a number of particularly hairy bugs, and significant improvements to the editor.
Take a look at the closed issue list to see what will be in 0.4.2
Tasks:
- Add
package.jsonsupport for themes, providing theme developers with a simple way to define key data about their themes. - Develop the advanced
hashelper to provide more options for customising themes dependent on what data is available. - Add the much-awaited tag pages feature.
- Introduce support for custom page and tag templates, allowing individual pages or tags to have a different templates.
Goal: Ghost 0.5 should significantly improve the ease of creating and customising a blog.
Tasks:
- Improvements towards using Ghost as a module, publish to npm
PLEASE NOTE:
- All dates mentioned here are estimates and are by no means definitive.
- Version numbers are also estimates, we may or may not increment at these points.
- This is still a work in progress in terms of features, some may be added, others may be removed or delayed
I’m pretty certain that this is going to be TLDR; for many people, so in summary:
- We are introducing a new 0.1.1 milestone which marks the point at which Ghost should be useful as a blog, this milestone replaces 0.2.0 for delivery mid-June.
- At 0.1.1 it will be required that every contributor to Ghost setup a blog using Ghost & write at least one post a week. It doesn’t need to be public, although we’d like access, and we’re not expecting works of literature, we just want all of the developers to be exercising the system regularly.
- 0.2.0 is still the point at which VIP KickStarter access will happen, and we are hoping to only push it back by 7 days
Version 0.1.0 - Initial Prototype - Completed 11th May
The first version of Ghost was a prototype version opened up to a small group of contributors. It had:
- divided the code into core and user content
- basic structure of admin vs frontend code mapped out inside of core
- very basic save, edit and list features for posts
- a single theme with very basic functionality
- a single plugin, hard-coded to load/not load
- some notion of hooks for themes & plugins.
Version 0.1.1 - Deployed Ghost - Completed 18th Jun
In order to ensure that the code we are delivering in the 0.2.0 milestone meets requirements, we’re introducing a new milestone: 0.1.1
At version 0.1.1 it should be possible for any of the core developers to run Ghost as a public blog. It may be missing key features which one would expect from a blog, but it should be stable and safe in terms of future updates.
At this point, we want all contributors to deploy and run Ghost as a blog somewhere, and publish something at least once per week. It doesn't have to be public or prolific, but it's important that we test the code by having it running in real-world environments and being used in real world situations.
A core dev should be able to (this means editing config files, or replacing images manually is acceptable but not desired):
- setup and run a blog
- there should be some means to deploy a blog on ec2/nodejitsu/appfog or somewhere
- it should be easy to run the blog in such a way that is stable and long-running.
- configure an admin level user & login/out as that user
- configure the blog to look like it belongs to them, this includes setting through any means:
- title
- description
- logo
- icon
- create, edit and publish a text-based blog post
- start a new post, save it as a draft which is not shown on the front end
- edit draft and published posts & save the changes
- publish draft post so it becomes visible on the frontend
- no fancy image upload in the preview, images can be added by using standard markdown
- have their homepage display a list of published posts ordered by publish date
- displays their configured title / desc
- shows a list of n posts
- only published posts should be shown
- most recently published post should be first
- have each post link to a post page which displays the post
- clicking on any post in the home page should take you to a single post page
- backup their blog before doing an upgrade to a new version
- possible to export (and import) all data as JSON
- maybe have a grunt task to zip & store the custom content
##Version 0.2 - Developer access - Completed 11th July
The second version of Ghost is intended to be released to VIP KickStarter backers via weekly and nightly builds. This version should be the first version which is feature complete enough to be realistically used by folks to run a blog, and therefore will start to require some compatibility between versions.
Any developer should be able to (this means there is a UI or tool provided and documented):
- download the code from a secure location, using their KS email address
- setup and run a blog
- there should be some simple means to deploy a blog onto a platform, and growing/improving documentation on how to deploy it elsewhere.
- it should be easy to run the blog in such a way that is stable and long-running.
- create themselves an admin user
- Single admin user registration
- Can login and logout
- Admin user owns all the things
- configure their blog’s frontend settings via the settings panel
- title
- description
- create and edit blog posts
- start a new post, save it as a draft which is not shown on the front end
- edit draft and published posts & save the changes
- publish draft post so it becomes visible on the frontend
- delete any post
- post can be deleted from the manage posts screen
- transition post to published
- post is marked as published
- post is given published at & published by properties
- from this point on, post appears in frontend, correctly ordered by its published date
- there is no scheduling available yet.
- a post can be unpublished
- have their homepage display a list of published posts ordered by publish date
- displays their configured title / desc
- shows a list of n posts
- only published posts should be shown
- most recently published post should be first
- pagination should be available to view older posts
- Theme/plugin API stuff:
- Theme API basics
- Static menu
- Plugin API basics
- Theme API basics
- Users / ACL - we will begin with the concept of a single admin user who has all permissions
- Admin frontend - should be converted fully to Backbone
- Function wrappers removed from node code
- Ghost.js cleanup
In addition to features, we have the following requirements if it is to be possible for us to realistically run Ghost as a blog.
- Stability
- Ghost shouldn’t crash unexpectedly
- We need to be reasonably certain that we are using error handling where necessary
- Well-tested
- Ghost should have been running, as a blog, at several locations
- We should have as much test coverage as possible
- Upgradable & data safe
- we need to be able to, at the bare minimum, export post data before an upgrade incase we break something terrible & lose data
- we will need a plan for how to upgrade Ghost without overwriting data, custom images, custom themes and custom plugins
we will have to manage database changes through migrations, meaning tying down the data model is a high priority any filters in place must continue to work in the same or similar way features should not be removed
We will have breaking changes, there is little doubt, but these will require a version bump
##Version 0.3 - Kickstarter access - Est 16th September*
[Planning WIP]
Version 0.3 will be released to all 5,236 KickStarter backers in mid September. As such we want to focus on user experience and making Ghost feel like a real blogging application. We also want to ensure at this point that Ghost is reasonably stable & feature rich.
With this in mind, for 0.3 we'd like to focus on the following key areas:
- Users
- Whilst we'll prob stick with the single-admin-user-owns-all-the-things for now, we should work on making the ownership explicit by rolling out the ACL system across the admin.
- Add the user UI so that the details of the admin user can be changed
- Get the concept of post author rolled out across the admin and frontend
- Advanced post features
- First and foremost this includes:
- archive page
- post tagging
- post SEO
- Image uploads
- Other potential features for this release include a simple RSS feed, search, comments (disqus), custom fields, editing permalinks etc, haunted markdown (image, video, small). We'll play it by ear and see which features we think are most important / we are able to fit in the release.
- First and foremost this includes:
- 3rd Party Integrations
- We need to start by designing the architecture behind 3rd party integrations & connecting various services for various tasks: sharing, liking, pulling data for dashboard widgets, and implementing services like comments which work on the blog.
- We need a set of core tools for authenticating and authorising with various schemes and for interacting with various kinds of API (most are REST or at least HTTP based)
- Additionally, the dashboard needs love. We need to plan out how internal widgets will work too and for 0.3 we'd like to have the following widgets up and running:
- Analytics
- App.net
- Internal
- Themes & Plugins
- API
- Roll out filters across the admin and api (see Imagining Ghost Themes and Plugins)
- Connect up with the tools for 3rd party services
- Improvements and additions to helpers (kinda requires the advanced post features)
- Installing/registering/loading
- The UI for activating a plugin and theme
- Add the concept of package.json to themes & plugins
- Add the ability to register custom filters and helpers from plugins and themes
- API
- Internal - i.e all the things we need to do to ensure Ghost is awesome:
- finishing the conversion of the admin UI to backbone
- adding a build step for the masses of client scripts
- sharing code between server and client where possible
- refactoring bits we aren't happy with (like ghost.js)
- improving unit test coverage for core inc adding unit tests for client
- adding automated functional tests
- Interactions Epic: #268
- User Epic: #269
- Themes & Plugins Epic: #270
- Advanced post features Epic: #271
##Version 0.4 - Public access - Est Early October
- Custom field image uploads
- Install
- Dynamic Menu (ui to edit single menu)
- Schedule post
- Mobile UI + Interactions
- Importer
- WordPress
- Tumblr
- Blogger
- Pages
##Version 0.5 - ? - Est 16th December
- Version control / revisions
- RSS & Pubsubhubbub
- Dashboard
- full set (initial...)
- Post queue
- Auto save + offline
- User management
- Haunted markdown (full basic...)
- Share to...
- ADN
- Theme-styled markdown/editor preview
##Future Release
- Public API
- User roles
- Multi Author
- Upgrade to MySQL/PostGres
- Switch to NoSQL
- Advanced publish workflows