Ghost/core
ErisDS 6f8752aa22 HTML helpers refactor - issue #246 items 2 and 5.
- moved template logic out of individual helpers and into Ghost
- simplified template-driven helpers into closures which maintain the context of handlebars
- with handlebars context we have access to data, so don't need to pass data in
- check data to test that it is a simple object and not a function
- moved helpers back into index.js
- provided tests for both template functions in ghost and the nav helper so we are back to where we were
2013-07-11 01:30:29 +01:00
..
admin issue #234 - date bug 2013-07-08 12:39:11 +01:00
frontend HTML helpers refactor - issue #246 items 2 and 5. 2013-07-11 01:30:29 +01:00
lang Fixing up some inconsistent TODO: items. 2013-06-25 17:58:26 +01:00
shared issue #234 - date bug 2013-07-08 12:39:11 +01:00
test HTML helpers refactor - issue #246 items 2 and 5. 2013-07-11 01:30:29 +01:00
ghost.js HTML helpers refactor - issue #246 items 2 and 5. 2013-07-11 01:30:29 +01:00
README.md Initial commit to GitHub repo 2013-05-11 17:44:25 +01:00

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.