Ghost/core
Gabor Javorszky b77a8fd0d9 Notifications on front end
Should close #37. There are persistent and passive notifications.

Persistent ones:
* are stored on `ghost.notifications`.
* have an api made to add / remove them with client side ajax logic (probably not the most elegant, but works)
* uses a modified `flashes.hbs` template
* will only disappear if user closes the bar
* stack

Passive
* added with backbone view / collection combo
* stack
* disappears on navigation and when user closes it
2013-07-22 14:41:27 +01:00
..
client Notifications on front end 2013-07-22 14:41:27 +01:00
server Notifications on front end 2013-07-22 14:41:27 +01:00
shared/lang App restructure - closes #245 2013-07-11 20:23:34 +01:00
test Merge pull request #293 from matthojo/Remove-Codemirror-CSS 2013-07-22 04:22:19 -07:00
ghost.js App restructure - closes #245 2013-07-11 20:23: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.