Ghost/ghost/admin/app
Hannah Wolfe 2313dab449 Subscribers: router & form helpers
Form:
- add confirm, location & referrer hidden fields
- add script to populate location & referrer
- add helper for creating the email field
- pass through input class and placeholder for email from top level form helper
- rename subscribe_form template & helper as it sounds more natural
- handle success and error cases differently
- improve error message display
- ensure useful data is passed back so that we can show nice messages
- check for honeypot value being filled out
- refactor error handler to set an error and always still render
2016-05-11 10:28:11 +02:00
..
adapters Return http status 204 on deletes 2016-03-22 11:42:48 -05:00
authenticators cleanup usage of Ember.inject 2016-01-19 07:03:27 -06:00
authorizers deps: ember-simple-auth@1.0.0 2015-10-18 13:17:02 -05:00
components Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
controllers Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
helpers Fix editor image perf and upload bug 2016-05-08 12:55:56 +02:00
html Slack integration 2016-05-08 12:49:15 +02:00
initializers Don't add trailing slash to end of url with parameters 2016-04-28 12:42:03 +01:00
instance-initializers deps: ember@2.5.0 2016-04-15 00:24:57 -05:00
mirage Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
mixins Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
models Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
routes Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
serializers Fix redirect to posts list when saving a new post as an author 2016-04-13 12:28:11 -05:00
services Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
session-stores Set localStorage key based on subdir 2016-01-12 17:12:59 +01:00
styles Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
templates Subscribers: router & form helpers 2016-05-11 10:28:11 +02:00
transforms Structured Data 3.0 2016-05-08 17:43:59 +02:00
utils Fix editor image perf and upload bug 2016-05-08 12:55:56 +02:00
validators Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
_config.yml The great migration (EAK -> ember-cli) 2015-03-11 12:37:41 -06:00
app.js deps: ember-cli@2.3.0 2016-02-16 12:32:48 -06:00
index.html Restructure Configuration API endpoint 2016-02-19 18:49:23 +00:00
README.md Convert Sass to Myth 2015-05-22 19:05:09 +01:00
resolver.js deps: ember-cli@2.3.0 2016-02-16 12:32:48 -06:00
router.js Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00
transitions.js Subscribers: Admin User Interface v1 2016-05-11 10:28:11 +02:00

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