Ghost/core/client
Matt Enlow b5af691a61 Save meta title and meta desc on post save
Closes #4369
- Renamed `editor-route-base` -> `editor-base-route` to bring it in alignment with the view and controller mixins
- Consolidated editor route code into editor-base-route
- Removed `serialize` from EditorEditRoute, as it reimplemented the ember default
2014-11-03 21:11:04 -07:00
..
adapters Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
assets Merge pull request #4361 from jaswilli/ember18 2014-10-30 08:26:26 -06:00
components Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
controllers Update Ember to 1.8.0. 2014-10-30 06:01:22 +00:00
docs Implement popovers 2014-10-20 22:09:45 +01:00
helpers Fix argument handling in gh-path helper. 2014-10-27 02:17:07 +00:00
html Custom permalink UI 2014-10-23 12:12:48 +01:00
initializers Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
mixins Save meta title and meta desc on post save 2014-11-03 21:11:04 -07:00
models Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
routes Save meta title and meta desc on post save 2014-11-03 21:11:04 -07:00
serializers Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
templates Update Ember to 1.8.0. 2014-10-30 06:01:22 +00:00
transforms Changed ember models to use moment for dates 2014-06-05 10:30:28 -06:00
utils Save meta title and meta desc on post save 2014-11-03 21:11:04 -07:00
validators Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
views Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00
_config.yml Adding Grunt tasks for Sass 2014-08-31 14:16:58 +01:00
.jshintrc updated Ember Simple Auth to latest version 2014-07-25 16:04:19 +02:00
app.js Rename helpers/ghostPaths.js -> helpers/ghost-paths.js 2014-09-24 20:06:42 -05:00
config-dev.js Get Ember Admin ready for production 2014-07-22 22:33:49 +00:00
config-prod.js Get Ember Admin ready for production 2014-07-22 22:33:49 +00:00
loader.js Add jscs task to grunt file and clean up files to adhere to jscs rules. 2014-09-17 21:44:29 -04:00
README.md First pass refactor of GUI readme redux 2014-08-31 16:56:41 +03:00
router.js Enable JSCS checking on client. 2014-10-25 16:13:04 +00:00

Ghost-UI

[Travis] [SauceLabs]

Ghost-UI is the Ember.js application used as a client-side admin for the Ghost blogging platform. This readme is a work in progress guide aimed at explaining the specific nuances of the Ghost Ember app to contributors whose main focus is on this side of things.

Architecture

ToDo: Explain the basic Ember app structure.

client/
├── assets/
│   ├── ghost.css
│   └── ghost.min.css
├── things/
│   ├── things.js
│   └── things.min.js
└── things/
    ├── things.js
    └── things.js

SASS

All CSS is written in SASS and compiled using grunt. We do not follow any strict CSS framework, however our general style is pretty similar to BEM.

Styles are primarily broken up into 4 main categories:

  • Helpers - are pure-sass files. Variables/mixins/things which are generally never compiled to actual CSS, and are simply used to aid development.
  • Patterns - are base level visual styles for HTML elements (eg. Buttons)
  • Components - are groups of patterns used to create a UI component (eg. Modals)
  • Layouts - are groups of components used to create application screens (eg. Settings)
  • Lib - is where we store styles for 3rd party components.

All of these separate files are subsequently imported and compiled in screen.scss.

Front End Standards

  • 4 spaces for HTML & CSS indentation. Never tabs.
  • Double quotes only, never single quotes.
  • Use tags and elements appropriate for an HTML5 doctype (including self-closing tags)
  • Adhere to the Recess CSS property order.
  • Always a space after a property's colon (.e.g, display: block; and not display:block;).
  • End all lines with a semi-colon.
  • For multiple, comma-separated selectors, place each selector on its own line.
  • Use js- prefixed classes for JavaScript hooks into the DOM, and never use these in CSS as per Slightly Obtrusive JavaSript
  • Avoid SASS over-nesting. Never nest more than 3 levels deep.
  • Use comments to explain "why" not "what" (Eg. This requires a z-index in order to appear above mobile navigation. Not: This is a thing which is always on top!)