Ghost/core
Hannah Wolfe 21487aa802 Email errors & cleanup
closes #618

- don't send a welcome email. This appeared to be breaking tests.
- make sure we handle errors from sending emails properly
- use promises when adding notifications
2013-09-04 15:04:25 +01:00
..
client Merge pull request #602 from jgable/fixCtrlS 2013-09-03 13:00:52 -07:00
server Email errors & cleanup 2013-09-04 15:04:25 +01:00
shared Merge pull request #590 from ErisDS/showdown-gfm-fix 2013-09-02 10:58:34 -07:00
test Proper settings infrastructure, allowing new features without compromising old data. 2013-09-03 22:56:34 +01:00
ghost.js Proper settings infrastructure, allowing new features without compromising old data. 2013-09-03 22:56:34 +01:00
README.md App restructure - closes #245 2013-07-11 20:23:34 +01:00

Core

Core contains the bread and butter of ghost. It is currently divided up into:

  • client - the assets, helpers, models, view and templates for rendering the admin panel backbone app
  • server - the controllers & helpers for driving the server side app along with the model, api, and data
  • shared - just contains lang for now, although it's not shared yet, more stuff should go here soon like handlebars helpers
  • test - contains unit tests and a set of html prototypes of the admin UI. Really, this folder should reflect all of core
  • ghost.js - currently both the glue that binds everything together and what gives us the API for registering themes and plugins. The initTheme function is a bit of a hack which lets us serve different views & static content up for the admin & blog

This structure is by no means final and recommendations are more than welcome.