Ghost/core
Gabor Javorszky 1d9b2d916e Passive notifications are dismissed on settings pane change
Closes #342.
It would be totally cool if we could have a Ghost.PubSub so we could hurl events there and pick them up somewhere else. For some reason all the backbone bits work on models, like `trigger` and `listenTo` and `delegateEvents`.
2013-08-15 23:18:10 +01:00
..
client Passive notifications are dismissed on settings pane change 2013-08-15 23:18:10 +01:00
server fixes extensions bug for image uploader 2013-08-13 21:04:07 +01:00
shared Added image upload reusable plugin 2013-08-05 23:01:48 +01:00
test Fixed word count grammar 2013-08-11 11:55:42 -05:00
ghost.js Improving the use of paths in Ghost 2013-08-12 15:37:23 +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.