Ghost/ghost/admin/app
Rish a85129abc8 Fixed lint
no issue
2019-10-07 09:17:26 +05:30
..
adapters
authenticators Added "What's new" indicator and modal to highlight recent updates (#1292) 2019-08-23 10:01:27 +01:00
components Fixed lint 2019-10-07 09:17:26 +05:30
controllers Fixed lint 2019-10-07 09:17:26 +05:30
helpers
initializers
mixins
models Updated member model to use new subscriptions structure 2019-10-03 23:10:42 +05:30
routes Added csv import/export for members 2019-10-04 15:14:20 +05:30
serializers Content visibility configuration in labs (#1346) 2019-10-02 11:13:59 +02:00
services Added "What's new" indicator and modal to highlight recent updates (#1292) 2019-08-23 10:01:27 +01:00
session-stores
styles Refined Stripe info in member details 2019-10-05 13:10:06 +02:00
templates Added empty Stripe info state for member details 2019-10-05 13:01:43 +02:00
transforms Updated member model to use new subscriptions structure 2019-10-03 23:10:42 +05:30
transitions
utils
validators
app.js
index.html
README.md
resolver.js
router.js Added csv import/export for members 2019-10-04 15:14:20 +05:30
transitions.js

Ghost Admin Client

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.

CSS

We use pure CSS, which is pre-processed for backwards compatibility by Myth. 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:

  • 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)

All of these separate files are subsequently imported and compiled in app.css.

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 over-nesting CSS. Never nest more than 3 levels deep.
  • Use comments to explain "why" not "what" (Good: This requires a z-index in order to appear above mobile navigation. Bad: This is a thing which is always on top!)