0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2025-02-10 23:36:14 -05:00
ghost/core
Hannah Wolfe 2c7245e0e5 issue #58 - removing the iiwf
In order to remove the iiwf we need to be able to lint backend and frontend code separately.
Changed our devDependency for grunt-jslint to use a fork which has multiTask (PR sent to main repo)
Updated Gruntfile with split rules for the jslint tasks
As a result, a few files failed to pass the new rules, these have been fixed and added to the commit
2013-06-25 13:38:41 +01:00
..
admin issue #58 - removing the iiwf 2013-06-25 13:38:41 +01:00
frontend closes #187 foreach column parameter 2013-06-23 16:46:02 +01:00
lang Bookshelf provider abstraction and tests 2013-05-23 23:02:41 -05:00
shared Import and Export UI 2013-06-23 16:06:57 -05:00
test closes #101 - data model updates 2013-06-17 23:59:08 +01:00
ghost.js issue #165 - reloading settings 2013-06-17 23:24:05 +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.