1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost-Admin.git synced 2023-12-14 02:33:04 +01:00
Ghost-Admin/app
Kevin Ansfield eec3714c2b 💄 Fixed scrollbar on editor title input in Chrome on Windows (#822)
closes https://github.com/TryGhost/Ghost/issues/8866
- add `overflow: hidden` to disable scrollbars on editor title input
2017-08-10 17:52:59 +07:00
..
adapters 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
authenticators 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
authorizers deps: ember-simple-auth@1.0.0 2015-10-18 13:17:02 -05:00
components Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
controllers Resolve nightshift visual bugs 2017-07-31 11:49:49 +04:00
helpers 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
html Style updates to new app frame for all other screens 2017-02-17 10:14:16 +00:00
initializers 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
instance-initializers convert ember imports to ember-cli-shim imports where possible (#95) 2016-06-30 11:21:47 +01:00
mixins Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
models Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
routes 🐛 fixed active users list not showing more than 20 users (#806) 2017-07-31 17:10:52 +04:00
serializers 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
services Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
session-stores Update code to match eslint rules 2016-11-14 13:26:00 +00:00
styles 💄 Fixed scrollbar on editor title input in Chrome on Windows (#822) 2017-08-10 17:52:59 +07:00
templates Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
torii-providers 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
transforms 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
utils ctrl/cmd-shift-i triggers image file dialog (#750) 2017-06-22 13:02:38 +01:00
validators Added Twitter & Facebook data override fields to PSM (#814) 2017-08-03 15:45:14 +04:00
_config.yml The great migration (EAK -> ember-cli) 2015-03-11 12:37:41 -06:00
app.js ⬆️ bump core ember dependencies (#804) 2017-07-31 13:38:46 +04: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 💄🐷 sort-imports eslint rule (#712) 2017-05-29 20:50:03 +02:00
transitions.js welcome tour (#527) 2017-06-08 22:00:10 +07: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!)