Ghost/ghost/admin/app
Kevin Ansfield 352c4af1d7 Refactored usage of .get('property') with es5 getters
no issue
- ran [es5-getter-ember-codemod](https://github.com/rondale-sc/es5-getter-ember-codemod)
- [es5 getters RFC](https://github.com/emberjs/rfcs/blob/master/text/0281-es5-getters.md)
- updates the majority of `object.get('property')` with `object.property` with exceptions:
  - `.get('nested.property')` - it's not possible to determine if this is relying on "safe" path chaining for when `nested` doesn't exist
  - `.get('config.x')` and `.get('settings.x')` - both our `config` and `settings` services are proxy objects which do not support es5 getters
- this PR is not exhaustive, there are still a number of places where `.get('service.foo')` and similar could be replaced but it gets us a long way there in a quick and automated fashion
2019-03-06 13:54:14 +00:00
..
adapters Removed use of ?include=tags,authors,authors.roles query param on post/page requests 2019-02-25 21:55:55 +07:00
authenticators Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
components Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
controllers Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
helpers Bumped dependencies (#1108) 2019-03-05 17:34:00 +00:00
initializers Bumped dependencies (Fixed production build) (#1091) 2019-01-08 12:36:16 +00:00
mixins Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
models Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
routes Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
serializers 🐛 Fixed error when creating subscribers via the admin area 2019-03-06 09:19:39 +00:00
services Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
session-stores Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
styles Added members feature to labs 2019-02-26 15:33:38 +07:00
templates Added error context to API error alert messages 2019-03-06 11:45:47 +00:00
transforms Added ability to configure Slack integration's username (#1084) 2019-01-21 12:26:21 +00:00
transitions Fixed autofocus not working on modal inputs 2018-06-04 17:48:57 +01:00
utils Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
validators Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
app.js Removed unnecessary TextField override 2019-02-11 13:51:10 +00:00
index.html 🤡 Serve own admin favicon (#619) 2017-04-06 17:28:51 +01: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 Refactored usage of .get('property') with es5 getters 2019-03-06 13:54:14 +00:00
transitions.js Unsplash integration 2017-08-15 16:01:12 +01: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!)