Ghost/ghost/admin/app
Kevin Ansfield 5047b9f3d7 Added initial custom integrations UI (#1051)
refs https://github.com/TryGhost/Ghost/issues/9865, https://github.com/TryGhost/Ghost/issues/9942

- `integration`, `api-key`, and `webhook` models and respective mirage mocks
- moves integration routes around to match ember's concept of nested routes (nested routes reflect nested UI not nested URLs)
- adds custom integrations list to integrations screen
- adds custom integration screen
  - allow editing of integration details
  - show list of webhooks
  - webhook creation modal

NB: the `enableDeveloperExperiments` flag needs to be enabled in the `config.development.json` file for the custom integrations UI to be displayed until it's out of development.
2018-10-18 00:18:29 +01:00
..
adapters Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
authenticators Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
components Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
controllers Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
helpers Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
initializers Fix session restoration 2018-02-20 12:43:15 +00:00
mixins Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
models Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
routes Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
serializers Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
services Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
session-stores Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
styles Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
templates Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
transforms Handle empty array of slack setting objects 2018-07-02 14:57:41 +01:00
transitions Fixed autofocus not working on modal inputs 2018-06-04 17:48:57 +01:00
utils Use Admin API v2 with session auth (#1046) 2018-10-05 19:46:33 +01:00
validators Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01:00
app.js Remove more import Ember via module imports 2018-05-03 17:52:39 +01: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 Added initial custom integrations UI (#1051) 2018-10-18 00:18:29 +01: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!)