no issue
- Our new marketplace (gpm) will make heavy use of package.json files
- Full details, spec, and validator are coming soon. In the meantime here's the basics:
- `name` must be lowercase and hypenated
- `version` must be semver compliant
- `homepage` should be a valid URL (GitHub URL is ok)
- `demo` should be a working Ghost install that uses your theme
- `engines` should contain a Ghost key indicating which version of Ghost the theme is compatible with
- `license` is required, we recommend `MIT`
- `screenshots` should provide a relative path or absolute URL to both `desktop` & `mobile` screenshots
- `author` should be an object. It must contain an email, and can also include a name and url.
- the `gpm` object should:
- indicate the package type (`theme` for now, later `app` or `adapter` etc)
- list out at most 2 marketplace categories for inclusion. Categories can be found in https://gist.github.com/ErisDS/d0674f57eaa087c9f92cbfc8e984d2d6 but are subject to change.
- other fields can be included as per a normal npm package, we recommend including the repostory & keywords with `ghost` & `theme` listed.
- use a `{{#tag}}{{/tag}}` block for tag in tag.hbs
- use two braces consistently for `{{title}}`
- use double quotes consistently for attributes (quote switching is unnecessary)
I recently created a new Ghost blog and a colleague pointed out that ligatures for code blocks looked a bit off. They weren't enabled in Firefox by default, but in Chrome (possibly different browser defaults?). This PR standardises it and removes any ligatures from `<code>` and `<tt>` blocks.
- Including jQuery before `{{ghost_foot}}` means jQuery can be used inside ghost_foot code injection
- It should also improve backwards compat, as without this jQuery code included via ghost_foot may break
No issue
In #189 I reworked much of the CSS for the menu button. The border on the menu button is supposed to be removed on small screens, but I missed that. This removes it.
Closes#196
- Absolutely positions the `.site-footer` when it's adjacent to the `.read-next` container
I've opted to use absolute positioning here because we can't be 10% sure what the height of the footer will be at smaller viewport widths as the `@blog.title` length can vary, so adding loads of breakpoints with negative margins isn't really viable.
No issue
To prevent browsers using an older version of the icon font when a newer version is available, we must add a version number to that src url.
This number must be incremented when the file files change, so this also adds a note explaining that.
