tqt/Ghost
2
1
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2023-12-13 21:00:40 +01:00
Code Issues 1 Releases Wiki Activity
Ghost/core
History
ErisDS 37d86e07bb Fixing bug in registration 
Switching over to abstracted data provider meant that email_address
accidentally got passed to the model as email and therefore could not
be found. This is now resolved.
Also, added trailing slash to register route, which I believe should be there
2013-05-26 12:38:14 +00:00
..
admin Fixing bug in registration 2013-05-26 12:38:14 +00:00
frontend Updating controllers to use the api + some minor changes to the api calls 2013-05-16 21:56:26 +01:00
lang Bookshelf provider abstraction and tests 2013-05-23 23:02:41 -05:00
shared Merge changes from upstream 2013-05-25 11:55:23 -05:00
test Fixing tests and adding settings provider. 2013-05-25 11:48:15 -05:00
ghost.js Fixing tests and adding settings provider. 2013-05-25 11:48:15 -05:00
README.md Initial commit to GitHub repo 2013-05-11 17:44:25 +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.