2020-04-29 18:44:27 +03:00
|
|
|
const should = require('should');
|
2021-10-06 12:52:46 +03:00
|
|
|
const getStructuredData = require('../../../../core/frontend/meta/structured-data');
|
2016-01-17 13:07:52 +03:00
|
|
|
|
|
|
|
|
describe('getStructuredData', function () {
|
2017-08-03 14:48:39 +03:00
|
|
|
it('should return structured data from metadata per post', function (done) {
|
2020-04-29 18:44:27 +03:00
|
|
|
const metadata = {
|
|
|
|
|
site: {
|
|
|
|
|
title: 'Site Title',
|
|
|
|
|
facebook: 'testuser',
|
|
|
|
|
twitter: '@testuser'
|
|
|
|
|
},
|
|
|
|
|
authorName: 'Test User',
|
|
|
|
|
ogType: 'article',
|
|
|
|
|
metaTitle: 'Post Title',
|
|
|
|
|
canonicalUrl: 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
publishedDate: '2015-12-25T05:35:01.234Z',
|
|
|
|
|
modifiedDate: '2016-01-21T22:13:05.412Z',
|
|
|
|
|
coverImage: {
|
|
|
|
|
url: 'http://mysite.com/content/image/mypostcoverimage.jpg',
|
|
|
|
|
dimensions: {
|
|
|
|
|
width: 500,
|
|
|
|
|
height: 500
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
ogImage: {
|
|
|
|
|
url: null
|
|
|
|
|
},
|
|
|
|
|
twitterImage: null,
|
|
|
|
|
ogTitle: 'Post Title',
|
|
|
|
|
ogDescription: 'Post meta description',
|
|
|
|
|
twitterTitle: 'Post Title',
|
|
|
|
|
twitterDescription: 'Post meta description',
|
|
|
|
|
authorFacebook: 'testpage',
|
|
|
|
|
creatorTwitter: '@twitterpage',
|
|
|
|
|
keywords: ['one', 'two', 'tag'],
|
|
|
|
|
metaDescription: 'Post meta description'
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
const structuredData = getStructuredData(metadata);
|
2016-01-17 13:07:52 +03:00
|
|
|
|
|
|
|
|
should.deepEqual(structuredData, {
|
|
|
|
|
'article:modified_time': '2016-01-21T22:13:05.412Z',
|
|
|
|
|
'article:published_time': '2015-12-25T05:35:01.234Z',
|
|
|
|
|
'article:tag': ['one', 'two', 'tag'],
|
2016-03-03 11:52:27 +03:00
|
|
|
'article:publisher': 'https://www.facebook.com/testuser',
|
|
|
|
|
'article:author': 'https://www.facebook.com/testpage',
|
2016-01-17 13:07:52 +03:00
|
|
|
'og:description': 'Post meta description',
|
|
|
|
|
'og:image': 'http://mysite.com/content/image/mypostcoverimage.jpg',
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
'og:image:width': 500,
|
|
|
|
|
'og:image:height': 500,
|
2019-09-10 12:37:04 +03:00
|
|
|
'og:site_name': 'Site Title',
|
2016-01-17 13:07:52 +03:00
|
|
|
'og:title': 'Post Title',
|
|
|
|
|
'og:type': 'article',
|
|
|
|
|
'og:url': 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
'twitter:card': 'summary_large_image',
|
2016-02-20 18:55:35 +03:00
|
|
|
'twitter:data1': 'Test User',
|
|
|
|
|
'twitter:data2': ['one', 'two', 'tag'].join(', '),
|
2016-01-17 13:07:52 +03:00
|
|
|
'twitter:description': 'Post meta description',
|
2016-06-30 03:04:43 +03:00
|
|
|
'twitter:image': 'http://mysite.com/content/image/mypostcoverimage.jpg',
|
2016-02-20 18:55:35 +03:00
|
|
|
'twitter:label1': 'Written by',
|
|
|
|
|
'twitter:label2': 'Filed under',
|
2016-01-17 13:07:52 +03:00
|
|
|
'twitter:title': 'Post Title',
|
2016-03-03 11:52:27 +03:00
|
|
|
'twitter:url': 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
'twitter:site': '@testuser',
|
|
|
|
|
'twitter:creator': '@twitterpage'
|
2016-01-17 13:07:52 +03:00
|
|
|
});
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
done();
|
2016-01-17 13:07:52 +03:00
|
|
|
});
|
|
|
|
|
|
2019-05-06 06:51:44 +03:00
|
|
|
it('should return structured data from metadata with provided og and twitter images only per post', function (done) {
|
2020-04-29 18:44:27 +03:00
|
|
|
const metadata = {
|
|
|
|
|
site: {
|
|
|
|
|
title: 'Site Title',
|
|
|
|
|
facebook: 'testuser',
|
|
|
|
|
twitter: '@testuser'
|
|
|
|
|
},
|
|
|
|
|
authorName: 'Test User',
|
|
|
|
|
ogType: 'article',
|
|
|
|
|
metaTitle: 'Post Title',
|
|
|
|
|
canonicalUrl: 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
publishedDate: '2015-12-25T05:35:01.234Z',
|
|
|
|
|
modifiedDate: '2016-01-21T22:13:05.412Z',
|
|
|
|
|
ogImage: {
|
|
|
|
|
url: 'http://mysite.com/content/image/mypostogimage.jpg',
|
|
|
|
|
dimensions: {
|
|
|
|
|
width: 20,
|
|
|
|
|
height: 100
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
twitterImage: 'http://mysite.com/content/image/myposttwitterimage.jpg',
|
|
|
|
|
ogTitle: 'Custom Facebook title',
|
|
|
|
|
ogDescription: 'Custom Facebook description',
|
|
|
|
|
twitterTitle: 'Custom Twitter title',
|
|
|
|
|
twitterDescription: 'Custom Twitter description',
|
|
|
|
|
authorFacebook: 'testpage',
|
|
|
|
|
creatorTwitter: '@twitterpage',
|
|
|
|
|
keywords: ['one', 'two', 'tag'],
|
|
|
|
|
metaDescription: 'Post meta description'
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
const structuredData = getStructuredData(metadata);
|
2017-08-03 14:48:39 +03:00
|
|
|
|
|
|
|
|
should.deepEqual(structuredData, {
|
|
|
|
|
'article:modified_time': '2016-01-21T22:13:05.412Z',
|
|
|
|
|
'article:published_time': '2015-12-25T05:35:01.234Z',
|
|
|
|
|
'article:tag': ['one', 'two', 'tag'],
|
|
|
|
|
'article:publisher': 'https://www.facebook.com/testuser',
|
|
|
|
|
'article:author': 'https://www.facebook.com/testpage',
|
|
|
|
|
'og:description': 'Custom Facebook description',
|
|
|
|
|
'og:image': 'http://mysite.com/content/image/mypostogimage.jpg',
|
|
|
|
|
'og:image:width': 20,
|
|
|
|
|
'og:image:height': 100,
|
2019-09-10 12:37:04 +03:00
|
|
|
'og:site_name': 'Site Title',
|
2017-08-03 14:48:39 +03:00
|
|
|
'og:title': 'Custom Facebook title',
|
|
|
|
|
'og:type': 'article',
|
|
|
|
|
'og:url': 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
'twitter:card': 'summary_large_image',
|
|
|
|
|
'twitter:data1': 'Test User',
|
|
|
|
|
'twitter:data2': ['one', 'two', 'tag'].join(', '),
|
|
|
|
|
'twitter:description': 'Custom Twitter description',
|
|
|
|
|
'twitter:image': 'http://mysite.com/content/image/myposttwitterimage.jpg',
|
|
|
|
|
'twitter:label1': 'Written by',
|
|
|
|
|
'twitter:label2': 'Filed under',
|
|
|
|
|
'twitter:title': 'Custom Twitter title',
|
|
|
|
|
'twitter:url': 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
'twitter:site': '@testuser',
|
|
|
|
|
'twitter:creator': '@twitterpage'
|
|
|
|
|
});
|
|
|
|
|
done();
|
|
|
|
|
});
|
|
|
|
|
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
it('should return structured data from metadata with no nulls', function (done) {
|
2020-04-29 18:44:27 +03:00
|
|
|
const metadata = {
|
|
|
|
|
site: {
|
|
|
|
|
title: 'Site Title',
|
|
|
|
|
facebook: '',
|
|
|
|
|
twitter: ''
|
|
|
|
|
},
|
|
|
|
|
authorName: 'Test User',
|
|
|
|
|
ogType: 'article',
|
|
|
|
|
metaTitle: 'Post Title',
|
|
|
|
|
canonicalUrl: 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
modifiedDate: '2016-01-21T22:13:05.412Z',
|
|
|
|
|
authorFacebook: null,
|
|
|
|
|
creatorTwitter: null,
|
|
|
|
|
coverImage: {
|
|
|
|
|
url: undefined
|
|
|
|
|
},
|
|
|
|
|
ogImage: {
|
|
|
|
|
url: null
|
|
|
|
|
},
|
|
|
|
|
twitterImage: null,
|
|
|
|
|
ogTitle: 'Post Title',
|
|
|
|
|
ogDescription: null,
|
|
|
|
|
twitterTitle: 'Post Title',
|
|
|
|
|
twitterDescription: null,
|
|
|
|
|
keywords: null,
|
|
|
|
|
metaDescription: null
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
const structuredData = getStructuredData(metadata);
|
2016-01-17 13:07:52 +03:00
|
|
|
|
|
|
|
|
should.deepEqual(structuredData, {
|
|
|
|
|
'article:modified_time': '2016-01-21T22:13:05.412Z',
|
2019-09-10 12:37:04 +03:00
|
|
|
'og:site_name': 'Site Title',
|
2016-01-17 13:07:52 +03:00
|
|
|
'og:title': 'Post Title',
|
|
|
|
|
'og:type': 'article',
|
|
|
|
|
'og:url': 'http://mysite.com/post/my-post-slug/',
|
|
|
|
|
'twitter:card': 'summary',
|
2016-02-20 18:55:35 +03:00
|
|
|
'twitter:data1': 'Test User',
|
|
|
|
|
'twitter:label1': 'Written by',
|
2016-01-17 13:07:52 +03:00
|
|
|
'twitter:title': 'Post Title',
|
|
|
|
|
'twitter:url': 'http://mysite.com/post/my-post-slug/'
|
|
|
|
|
});
|
✨ [FEATURE] AMP⚡ (#7229)
closes #6588, #7095
* `ImageObject` with image dimensions (#7152, #7151, #7153)
- Returns meta data as promise
- returns a new Promise from meta data
- uses `Promise.props()` to resolve `getClient()` and `getMetaData()`
- Adds 'image-size' util
The util returns an object like this
```
{
height: 50,
url: 'http://myblog.com/images/cat.jpg',
width: 50
};
```
if the dimensions can be fetched and rejects with error, if not.
In case we get a locally stored image or a not complete url (like `//www.gravatar.com/andsoon`), we add the protocol to the incomplete one and use `urlFor()` to get the absolute URL. If the request fails or `image-size` is not able to read the file, we reject with error.
- adds 'image-size' module to dependencies
- adds `getImageSizeFromUrl` function that returns image dimensions
- In preparation of AMP support and to improve our schema.org JSON-LD and structured data, I made the following changes:
- Changes the following properties to be `Objects`, which have a `url` property by default and a `dimensions` property, if `width` and `height` are available:
- `metaData.coverImage`
- `metaData.authorImage`
- `metaData.blog.logo`
- Checks cache by calling `getCachedImageSizeFromUrl`. If image dimensions were fetched already, returns them from cache instead of fetching them again.
- If we have image dimensions on hand, the output in our JSON-LD changes from normal urls to be full `ImageObjects`. Applies to all images and logos.
- Special case for `publisher.logo` as it has size restrictions: if the image doesn't fulfil the restrictions (<=600 width and <=60 height), we simply output the url instead, so like before.
- Adds new property for schema.org JSON-LD: `mainEntityOfPage` as an Object.
- Adds additional Open Graph data (if we have the image size): `og:image:width` and `og:image:height`
- Adds/updates tests
* AMP router and controller (#7171, #7157)
Implements AMP in `/apps/`:
- renders `amp.hbs` if route is `/:slug/amp/`
- updates `setResponseContext` to set context to `['amp', 'post']` for a amp post and `['amp', 'page']` for a page, but will not render amp template for a page
- updates `context_spec`
- registers 'amp' as new internal app
- adds the `amp.hbs` template to `core/server/apps/amp` which will be the default template for AMP posts.
- adds `isAmpURL` to `post-lookup`
* 🎨 Use `context` in meta as array (#7205)
Instead of reading the first value of the context array, we're checking if it includes certain context values.
This is a preparation change for AMP, where the context will be delivered as `['amp', 'post']`.
* ✨ AMP helpers (#7174, #7216, #7215, #7223)
- Adds AMP helpers `{{amp_content}}`, `{{amp_component}}` and `{{amp_ghost_head}}` to support AMP:
- `{{amp_content}}`:
- Adds `Amperize` as dependency
- AMP app uses new helper `{{amp_content}}` to render AMP HTML
- `Amperize` transforms regular HTML into AMP HTML
- Adds test for `{{amp_content}}` helper
- Adds 'Sanitize-HTML` as dependendy
- After the HTML get 'amperized' we still might have some HTML tags, which are prohibited in AMP HTML, so we use `sanitize-html` to remove those. With every update, `Amperize` gets and it is able to transform more HTML tags, they valid AMP HTML tags (e. g. `video` and `amp-video`) and will therefore not be removed.
- `{{amp_ghost_head}}`:
- registers `{{amp_ghost_head}}` helper, but uses `{{ghost_head}}` code
- uses `{{amp_ghost_head}}` in `amp.hbs` instead of `{{ghost_head}}`
- `{{ghost_head}}`:
- Render `amphtml` link in metadata for post, which links to the amp post (`getAmpUrl`)
- Updates all test in metadata to support `amp` context
- Changes context conditionals to work with full array instead of first array value
- Adds conditionals, so no additional javascript gets rendered in `{{ghost_head}}`
- Removes trailing `/amp/` in URLs, so only `amphtml` link on regular post renders it
- Adds a conditional, so no code injection will be included, for an `amp` context.
- `{{amp_components}}`:
- AMP app uses new helper `{{amp_components}}` to render necessary script tags for AMP extended components as `amp-iframe`, `amp-anime` and `amp-form`
- Adds test for `{{amp_components}}`
2016-08-22 19:49:27 +03:00
|
|
|
done();
|
2016-01-17 13:07:52 +03:00
|
|
|
});
|
|
|
|
|
});
|
