Demos consumers implementation guidelines¶
Consumers MUST implement those wireframes
The official design from the out of the box initiative can be found on https://www.drupal.org/node/2900720
Hosting, CSS & html, Urls structure, Models, Architecture, Cache, Service workers etc …¶
Consumers are free to choose tools which fits best their projects concerning those points; because there is a wide variety of consumers with sometimes very different needs.
Consumers may use public JSON-API
Getting started with public JSON API¶
JS Useful libraries to request JSON API :¶
Angular and Ionic consumers may be interested in :
jsonapi-parse : resolve nicely included and relationships from JSON response object.
Minimalistic package that transforms an object to a json api query string, use this only if a more complete library is not a solution for you.
API endpoints usage examples :¶
A list of important resources:
Recipes categories : https://live-contentacms.pantheonsite.io/api/categories
Content model and wireframes have been provided by the Outside of the box initiative.
Frontend consumers should try to follow that.
wireframe : https://www.drupal.org/files/issues/1%20-%20Umami%20Front%20wirefame%20v4.png
The frontpage consists of several elements:
- A list of promoted articles and recipes: This should contain the 3 last “promoted” items. As of now
there is no easy way to query that instead of querying for both the last 3 recipes and articles and merge them manually.
const data = [...recipes, ...articles].sort((item1, item2) => item1.createdAt > item2.createdAt).slice(0, 3)
- Month Editions : The magazine promotion block in the center links to the “Magazine” page
- A list of links:
- Dinners to impress: Filter by category ‘Main Dessert’:
- Learn to cook:
- Baked up:
- Quick and easy:
- A grid of the 4 latest recipes, ordered by create time
wireframe : https://www.drupal.org/files/issues/4%20-%20Umami%20recipes%20wirefame%20v4.png
- The idea of having a list of tags has been bought back into the wireframes and placed in the pre-footer and these can link through to list the tagged recipes - plans for this View will likely be discussed in our next call
Recipe detail page¶
wireframe : https://www.drupal.org/files/issues/5%20-%20Umami%20recipe%20wirefame%20v4.png
The “more recipes” is recipes of the same category (we had the choice here, this still may be discussed : https://www.drupal.org/node/2818741#comment-12122853)
Features listing page¶
wireframe : https://www.drupal.org/files/issues/2%20-%20Umami%20features%20wirefame%20v4.png
API endpoint : http://live-contentacms.pantheonsite.io/api/articles
Features is a list of articles, with a promoted article at the top
There is not yet articles content for now in public API
Features detail page¶
wireframe : https://www.drupal.org/files/issues/3%20-%20Umami%20feature%20wirefame%20v4.png
Main body will be a long text field with full html with the possibility to have images inside. We haven’t faced the idea of having responsive images inside WYSIWYG yet. Just to point out that the main image is a separate field.
Magazine detail page¶
wireframe : https://www.drupal.org/files/issues/6%20-%20Umami%20page%20wirefame%20v4.png
- The magazine page will use the page content type with an aside containing a block that promotes the contact form. The idea is to simply have this content type work in a consistent way for any further pages that may be added to the theme. The contents of the aside can be reviewed as the requirements come together
- The contents illustrated for the page can all be provided via the ckeditor, keeping the design for the page simple but with plenty of opportunity to have some great looking sample content
Get in touch page / Contact page :¶
Expanded/expandable search field that send you to a list of results.
- ‘Get in touch’ is links to a Contact Form
- ‘About Umami Theme’ links to a page providing information about the demo theme itself
Known limitations of current public API¶
- We can’t use imagestyles to scale and crop imported images
- Posting a contact form and sending mail is not yet possible (see https://www.drupal.org/node/2843755 )
- Getting Recipes Image from imageFile property is not yet possible due to a bug, use “image_field” or “thumbnail” proprety as a workaround for now (https://www.drupal.org/node/2890762 . Maybe related to Json Api extras aliasing ? )
- There is not yet something like a “slug” field to create front-end SEO-friendly paths ( but snail module should allow to fix this https://github.com/contentacms/snail )
- there are not articles for now to create “features” pages : http://live-contentacms.pantheonsite.io/api/articles
- Month Edition block : how to implement this ?
- unique path for content : when snail will be ready, we may want to fill “path” field for nodes
Minimal Suggested Implementation¶
Those features compose the minimal suggested implementation for your recipes magazine.
- 3 latest promoted recipes and articles
- 4 latest promoted recipes
- 4 blocks (Dinner to impress, Learn to cook, etc…)
- 1 promoted recipe at the top
- 4 latest recipes + view more button at the top
- 4 recipes for each category + view more button
RECIPES CATEGORY PAGE
- all recipes by category
LATEST RECIPES PAGE
- all latest recipes
- full recipe page
- block « recipes from the same category »
- A menu with “home” and “recipes”