We use cookies to customize content for your viewing and for analytics. If you continue to browse this website, we will assume that you are happy to receive all our cookies. For further information please read our cookie policy.
These are the three page types that form the product Brand Architecture section of the site. The page types form a loose rather than a strict hierarchy because an item or product can exist in more than one place. For example, the Spine capability appears in both the orthopaedic and neurotechnology portfolio.
Page type | Usage |
---|---|
Portfolio |
|
Capability |
|
Specialty |
|
The Brand Architecture pages function like sections in a product catalog and are designed to support a smaller set of components. At launch, they will have very limited options for customization. All capability and specialty pages consist of:
As a result of using the same set of components, the Brand Architecture pages will generally look the same.
Currently no, however there are plans to enhance these pages after launch.
The Brand Architecture pages are designed to display a limited set of content until a majority of the product section of the website is populated. Once there is a better understanding in regard to the volume of dynamic content that will displayed on the Brand Architecture pages, the team will be able to design appropriate enhancements to these pages which can include a banner carousel.
A specialty page is the third-content type in the Brand Architecture and is a child of a capability.
Specialty pages simply provide a way to categorize products within a given capability. A specialty page is optional; for capabilities that have few products, a specialty page may not be needed.
With the exception of the specialty tiles that appear on a capability page, there is no visible difference between a specialty and capability page.
Products, systems and procedures will appear in a respective capability or specilaity page if they are tagged appropriately. However, businesses are encouraged to work with the owning business and the brand team prior to cross-marketing products.
These are the three page types that businesses can use to showcase their product offering. See the table below for general guidance around the page types and how they should be used.
The purpose for differentiating between the three content types is best demonstrated on the capability and specialty pages; system pages have a teal 'system' badge and procedures have a purple 'procedure' badge which helps visitors filter the grid by page-type.
Functionally, the only difference between the page types is that the "Product Group" and "Product List" components are available on the procedure and system pages and not on the product page.
Page type | Usage | Components |
---|---|---|
Product page |
|
|
Procedure page |
|
|
System page |
|
|
Before the initial launch, businesses will need to contact the WebContentTeam@stryker.com to add or delete pages. After launch, Business Unit Leads will be trained and can then have control of the pages within their area of the site.
The Brand Architecture is the primary navigation visitors will use to browse Stryker's product offering. This will help present our breadth and depth of products in a context that is relevant to customers rather than the way our company is organized.
Businesses are encouraged to work with the Brand team to evolve the Brand Architecture so it appropriately represents their products.
Through the use of tags on product, procedure, and system pages, businesses can determine where their products appear in the Brand Architecture without making changes directly to the Brand pages.
To organize products using a taxonomy not supported by the Brand Architecture, businesses can leverage the filter dropdowns on the capability and specialty pages.
Company pages and the Brand Architecture pages are managed by the Corporate Communications and Brand teams respectively. Businesses will have permissions to "update" Brand Architecture pages and will need to coordinate with the Brand team to publish to production.
To feature content on the homepage or any company page, businesses will need to reach out to the appropriate points of contact on the Corporate Communications team.
Businesses can cross-sell products today on product, procedure, or system pages by using Featured Content components in the customizable area to link to related products.
System and procedure pages have two other components: product list and product group, that dynamically populate based on tagging. Cross-selling on Brand Architecture pages is planned after the initial product pages have been created and the site has launched.
The Stryker.com team is working with legal to determine the best method for handling trademarks across the site. As of now, the current plan is to have a single page that lists all company trademarks in once place and have a global link in the footer that will be visible on all pages. This would eliminate the need for busineses to load it at the bottom of every single page the trademark appears.
Highest resolution is fine as long as the aspect ratio is correct. The Digital Asset Management (DAM) system will create renditions so the components throughout the site can render the image correctly.
Controlled documents (surgical techniques, IFUs, etc.) are not to be loaded into the DAM at this time. Those assets should be linked to the system of record (e.g. GCS/CDN) using a combination of an External Asset Library page and Resources and Download component.
Filters provide businesses with a way to classify products using a taxonomy other than what is covered by the Brand Architecture. Businesses are free to choose product classifications that are best suited for their product offering. Some examples are: indication, product type, brands, etc. Filters on the capability page can be different from the filters on the specialty page.
The maximum number of filters on any page is three.
Yes. Businesses can create their filter categories in the "Custom" area of the AEM tagging application. Once filters are created, authors will need to tag each product accordingly. Then, the filters will need to be added to the Filtered Content Grid component of the respective page.
Page metadata is configurable via the "Page Properties" section.
Authors are limited to the components that exist. New functionality will be prioritized and developed in collaboration with the Digital Communications team and Stryker IS.
Because the platform is designed to evolve in order to meet the changing needs of the business; your feedback is welcomed.