In MedHub, every SRL is built using the article page-type (or "template"). An article page type model consists of very specific entries at very specific points of the page:
The article hero (section-HeroArticle)
The content block (section-ContentBlock)
The Contact Us banner (section-Banner)
The references drawer (section-ExtraFooter)
This means that you can only use these four sections to author each of these pages, and each section is needed in order for the page to be published live. Other parts will contribute to the contents - for example you can embed videos and images into the Content Block, and your Hero may have buttons, but if we're strictly speaking about modules or widgets on the page, those are the four that make up each and every article page.
The hero buttons are the same two buttons used across all articles, and the beauty of Contentful is that you can just reuse those buttons, not author one every time you need it. Note too that the section-LocalDisclaimer is not standalone, but referenced into the hero so that it renders appropriately in terms of spacing and padding.
As of the day of writing, the Show Updated Date field is not actually being used in the content block, so the updated date is the first part of the body that should be authored. You can embed other entries (specifically videos and images) within the Content block, hyperlink to external content or the reference drawer, and style the text just like you would using any other WYSIWYG. Please note however that several options that you might expect to be available to you are not - you cannot centre-align text nor can you add subscript or superscript. Our solution to display the references in an appealing way has been to utilize unicode.
The banner at the bottom of each article is the same banner used across all articles, and the beauty of Contentful is that you can just reuse it, not author one every time you need it. Saves you time and saves space.
The extra footer is the last flexible item authored on an article page. You can display entries with or without a numbered list, but the assumption is that you will use the latter. You can add styling such as bolding, italics, and hyperlinks, and a button to download the Fact Sheet. Again, for the purposes of ease and reuse, it is the same button in the footer used across all articles.
<TL;DR>? Download the video and I will show you this process using the compose app and outline some particulars of the structure.
The FAQ detail pages have their own page-type named (you guessed it!) FAQ. It looks very similar, once published, at an article, but has the categories sidebar and some additional fields in the model for date and related content.
An FAQ URL looks like this
or, more generally
so there are three content types with slug data contributing to the final product and the final URL - the subpart-product item, which contains the bolded slug, the subpart-faqCategory, which contains the italicized part, and finally the pageFAQ itself, which contains the underlined slug. The "/faqs" slug is added programmatically. As of the time of writing, the product page is not implemented, so you cannot land at https://domain.com/faqs/product (it serves for now as an intermediate item that contributes to the internal structure of the content). You can, however, navigate to category landing pages (https://domain.com/faqs/product/faq-category) and of course the faq details page itself.
Three microcopies are tied to FAQS and require translation - faq.related.label, faq.sidebar.title, and faq.category.eyebrow.title
Remember! An FAQ flow is product (subpart-product), category (subpart-faqCategory) and finally the FAQ detail itself (https://domain.com/faqs/product/faq-category/name-of-faq-detail-page !)