Product pages have two main style variations, which are different enough that they each require different logic.
Category 5 matches the style which we are implementing, and therefore requires (hopefully) less work.
1) Left rail variances are not going to be a concern for import; for now it is generally assumed that the left rail is the same for every product page.
2) Industry/Brand/Category metadata are in the metadata of the page, so they should be captured if available. (brand, industry, productCategory)
3) Keywords and other metadata should also be captured as page metadata
Categories 2, 4 and 9 are a different style and need slightly different handling:
1) Same metadata requirements apply as before
2) The hero portion of the page should be broken up:
The title should be its own section with an H1 tag
The text should be default content in the next section
If a technical document link or data sheet is provided, a Document (Technical) block should contain those links
If SDS or other document links are provided under a product literature section, they should be listed in a Document (Product) block
3) The MORE content below the hero block should be concatenated below the technical documentation (if it exists) and above the product documentation.
Product pages have two main style variations, which are different enough that they each require different logic.
Category 5 matches the style which we are implementing, and therefore requires (hopefully) less work.
1) Left rail variances are not going to be a concern for import; for now it is generally assumed that the left rail is the same for every product page. 2) Industry/Brand/Category metadata are in the metadata of the page, so they should be captured if available. (brand, industry, productCategory) 3) Keywords and other metadata should also be captured as page metadata
Categories 2, 4 and 9 are a different style and need slightly different handling:
1) Same metadata requirements apply as before 2) The hero portion of the page should be broken up: