mirror of
https://github.com/TryGhost/Ghost.git
synced 2024-12-01 22:02:11 +03:00
cc276486f0
refs: https://github.com/TryGhost/Ghost/issues/14980 refs: https://github.com/TryGhost/Ghost/pull/15087 - The Tenor v1 API has been decommissioned https://developers.google.com/tenor/guides/migrate-from-v1 - Updated the API to v2, but there are some differences we have to account for - Swapped from using the old "trending" API to the new "featured" API, which at present seem to be the same thing - Added a new client_key, which identifies the integration using the google API key, as google API keys can be used for multiple APIs and projects - Fixed up the error handling to support Google's error format, and also caught and replaced the error that everyone with old keys will see to make it clearer. This includes adding an htmlError property so that we can output HTML safely in the frontend. There is still an active TODO with the naming of the config key, but we will resolve this after merging admin into the monorepo. Co-authored-by: Hannah Wolfe <github.erisds@gmail.com> |
||
---|---|---|
.. | ||
adapters | ||
authenticators | ||
components | ||
controllers | ||
errors | ||
helpers | ||
initializers | ||
mixins | ||
models | ||
modifiers | ||
routes | ||
serializers | ||
services | ||
session-stores | ||
styles | ||
templates | ||
transforms | ||
transitions | ||
utils | ||
validators | ||
app.js | ||
index.html | ||
README.md | ||
router.js | ||
transitions.js |
Ghost Admin App
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!)