Ghost/core
John O'Nolan 2be5ce72ae Merge pull request #140 from matthojo/Login-Screen
Vertically center login form, fixes #134
2013-06-11 09:56:47 -07:00
..
admin Merge pull request #140 from matthojo/Login-Screen 2013-06-11 09:56:47 -07:00
frontend Directory scanning on contents/themes and plugins 2013-06-09 20:17:54 +01:00
lang Bookshelf provider abstraction and tests 2013-05-23 23:02:41 -05:00
shared Merge pull request #131 from javorszky/iss82-2 2013-06-11 04:41:22 -07:00
test Merge branch 'pr/119' 2013-06-09 21:41:07 +01:00
ghost.js Directory scanning on contents/themes and plugins 2013-06-09 20:17:54 +01:00
README.md

Core

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

  • admin - the views, controllers, assets and helpers for rendering & working the admin panel
  • frontend - the controllers & helpers for creating the frontend of the blog. Views & assets live in themes
  • lang - the current home of everything i18n, this was done as a proof of concept on a very early version of the prototype and needs love
  • shared - basically everything to do with data & models. The sqlite db file lives in the data folder here. This is the part that needs the most work so it doesn't make much sense yet, and is also the highest priority
  • test - currently contains two sad unit tests and a set of html prototypes of the admin UI. Really, this folder should reflect all of core. It is my personal mission to make that happen ASAP & get us linked up with Travis.
  • 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 & frontend.

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