TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-11-24 14:43:08 +03:00
Code Issues Projects Releases Wiki Activity
d27f32fb4d
Ghost/core
History
Hannah Wolfe d27f32fb4d Bug fix - unable to publish 
- The addition of published/draft statuses to the post model on the frontend was being returned to the server.
- These additional properties are client-side only and are now unset before the model is saved
2013-07-07 19:41:05 +01:00
..
admin Bug fix - unable to publish 2013-07-07 19:41:05 +01:00
frontend closes #195 posts date on content page 2013-07-04 19:42:49 +01:00
lang Fixing up some inconsistent TODO: items. 2013-06-25 17:58:26 +01:00
shared Getting rid of adminnavbar filter and console.logs 2013-06-30 16:50:26 +01:00
test Increment slug if duplicate 2013-06-25 20:48:48 -05:00
ghost.js issue #186 - load plugins 2013-07-01 20:24:48 +01: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.