A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | TEMPLATE MAPPING | ||||||||||||||
2 | # | Template name | Pages Covered | Scoping Notes | Requires input question exercise | ROI Comments | Client Comments | ||||||||
3 | 1 | Homepage | 1 | In Design R1 phase | |||||||||||
4 | 2 | Product (Platform) & Solution Overview template | 2 | Acts as a jumping off point to all the 15 use cases and 6 products. Both pages will use the same components with few modules toggled on/off based on available content. | |||||||||||
5 | 3 | Navigation & Footer | 1 | Nav & footer will be it's own template and will be based off the approved navigation model. | |||||||||||
6 | 4 | Platform overview (RadiantOne Intelligent Identity Data Platform) | 1 | Platform will be its own template and will complexlight the power of RadiantOne by touching on benefits, features, integrations, social proof and act as a jumping off point to the individual capabilities page. | |||||||||||
7 | 5 | Solution detail template | 15 use case + 5 Industry | Solution detail accommodates all the 15 use case pages and the 5 by industry pages. As a rough content outline, these solution detail pages will complexlight benefits, social proof content, resources, use cases, related products, integrations etc. | |||||||||||
8 | 6 | Product detail (Platform | 6 | This template will accommodate the 6 main products. Product detail page will complexlight the benefits, features, capabilities, integrations, architecture etc. for each of the products. | |||||||||||
9 | 7 | Platform Capabilities | 7 | This template will accommodate all the 7 platform capabilitites. | |||||||||||
10 | 8 | Resource Library | 2 | This template accommodates Resource Library and Events & Webinars page. This will be unique and simple template that would acts a resource hub showcasing various resource assets like whitepapers (gated), case studies, solution brief, analyst report etc. The template could complexlight but not be restricted to - featured assets, - ability to filter by topic, asset types, solutions/products, etc. - Link to any other related pages | |||||||||||
11 | 9 | Resource asset detail | Many | Template accommodates all resource assets and Webinars. We will create a standardized template for gated and ungated resource assets. There will be also some SEO considerations in creating this template. Master template with areas that could be toggled on/off based on type of resource. Gated template needs (for whitepapers): • Form • Content Areas, teaser information per SEO best practices, • Social proof • Media Areas • Includes a Thank you page Ungated assets could include: - Standardized landing page template with modules to accomodate various types of content - Access to pdf, etc. | |||||||||||
12 | 10 | Blog overview | 1 | Building and designing the page with proper detailed tagging will help in easy maintenance to add more posts in the future. Based on available content, this template can also accommodate Blog categories and Blog author pages if available. Template needs: • Dynamic featured content areas • Subscription component • Topic/Category Links • Card grid of blogs • Ability to filter by topic, solutions, category etc. | |||||||||||
13 | 11 | Blog detail | Many | Editorial template layout. Template needs: • Text areas that meet SEO search requirements. (paragraph formatting, embedded links, etc) • Media areas • Author & Category info • Article length info • Social share buttons • Related posts • Related resources | |||||||||||
14 | 12 | Glossary & Glossary detail | 1 | Template needs: • One url per term, navigable via an a-z list, term definitions 60-200 words, • try to answer the "what is it" question in the first 40-60 words. • bullet lists are good. • We will set up automated meta tags based on the glossary so "What is [glossary term]? | Radiant Logic Glossary" would be an example title tag that could play off the term name. • This can be done in a database driven way that is relatively low -effort. • Crosslinks back to the site can also be automated modules if needed | |||||||||||
15 | 13 | About Us | 1 | We recommend unique template because of the following but not restricted to: - A well crafted Company page can help build a strong brand and position yourself as a market-leader. It can touch on things like: - Mission statement, company values/culture and history - Company statistics and Awards, Customers, Industry recognition - Community involvement - Locations - Links out to other related pages like Careers, Leadership, News etc. - Company pages are often very visual with graphic elements, company photography etc from a design perspective. | |||||||||||
16 | 14 | Leadership | 1 | This template will showcase all the management team members, their bios and cross linking opportunities to news, articles etc. But we will make sure to use existing components wherever possible. | |||||||||||
17 | 15 | Customer detail | Many | We recommend not gating the customer case studies. We reccommend creating a unique template to create a standardized & consistent landing page for all the customers. | |||||||||||
18 | 16 | Request Demo | 1 | We recommend having a unique template as it's the main conversion strategy page. But we will make sure to use existing components wherever possible. Template needs: • Form • Social proof • Content areas like benefits or any other support information. • Includes Thank you page | *Thank you page can be the same as used on the Gated asset page | ||||||||||
19 | 17 | Product Documentation | 1 | This page is net new page to help tech audience find documentation easily without having to log in. It could include but not restricted to: - complexlight general documentation & product-specific documentation on the page - Documentation categories to help users find their answers - Any support details in case they are not able to find what they are looking for. - Integrate third-party reviews or even forum posts if available on the page for validation | |||||||||||
20 | 18 | Partner | 1 | We recommend a unique template to help elevate the partners and the different types of partners users can choose from. We will try to use as much existing components as possible. | |||||||||||
21 | 19 | Partner Category | 3 | This template accommodates the 3 partner category namely Technology partners, Resellers/distributors, service providers. This page can be built using existing components once the component library is built. | *We could potentially combine 'Partner' and 'Partner Category' to reduce the template number. | ||||||||||
22 | 20 | Partner detail | Many | These pages will be pulled of the pdfs and will be a standardized landing page template. | *This could also use the same template as the Customer detail template (#15) with couple of extra compoennts if needed. | ||||||||||
23 | 21 | Integration detail page | Many | This will be a standardized landing page template for each integration. This will be its own template but we will try to use as much existing components as possible. | |||||||||||
24 | 22 | User groups & news | 2 | Template accommodates IAM user groups + News Template needs: • Thumbnails to show the user groups and news • Other related content | *This could use elements like the card styles etc from the resource library or Blog overview page | ||||||||||
25 | 23 | Careers | 1 | This page would complexlight company cuture, benefits/perks, values, job openings etc. This page can be built using existing components once the component library is built. | |||||||||||
26 | 24 | Career Detail page | 1 | *This will mostly be just text showcasing the job description and a integrated form to apply. | Confirmed that the careers will use Bamboo HR integration. Dev team will have to meet with RLO to understand the integration. | ||||||||||
27 | 25 | Integrations page | 1 | Integrations will be cross linked from key pages like Platform and product pages. This page will complexlight all the integrations. This template can use components from resouce and blog pages probably. | *This can use elements like the cards and content modules from the component library | ||||||||||
28 | 26 | Contact Us | 1 | This page can be built using existing components once the component library is built. | |||||||||||
29 | 27 | RadiantOne Training | 1 | This page can be built using existing components once the component library is built. | Will both Instructer-led and self paced training live in Magentrix? Currently Instructer-led can be access by registering. | ||||||||||
30 | 28 | Our customers | 1 | Template Needs: • Grid display of all the customers • Options to filter customer by industry oor category if applicable • Other related content | *This could poterantially use elemenst like cards or lists form teh resource or blog pages | ||||||||||
31 | 29 | Download RadiantOne | 1 | This page can be built using existing components once the component library is built. | |||||||||||
32 | 30 | Customer Support | 1 | Support offerings, Answers & Help, Knowledgebase, Customer Community Tiered support levels, support ticket entry in magentrix, knowledgebase in magentrix, forums in magentrix We will need a "matrix" object to be able to compare and contrast the different support levels | *Page can be built using most of the existing modules from the library. | ||||||||||
33 | 31 | Professional Services | 1 | Advisory Services, Integration Services. Content and service descriptions, content and contact form RLO team likes: https://www.zendesk.com/customer-experience/professional-services/#professional-services https://www.mavenlink.com/services | *Page can be built using most of the existing modules from the library. | ||||||||||
34 | 32 | Customer Experience | 1 | Net new content - TBD Customer bill of rights? Account Management I want the CX related activities that the customer should expect. ie. new customer onboarding, NPS, CSAT, SLA management etc. | *Modules can be mapped based on the input questions | ||||||||||
35 | 33 | DevOps Resources | 1 | This page can be built using existing components once the component library is built. | |||||||||||
36 | 34 | Training Registration page | 1 | https://www.radiantlogic.com/events/training/training-schedule/y2021/training-9-13-2021/ | *Page can be built using most of the existing modules from the library. | ||||||||||
37 | 35 | Extra component list as needed | Many | 1. A "matrix" object to be able to compare and contrast the different support levels on Customer support page. 2. Schedule/table component to showcase the training schedule on the RadiantOne Training page. 3. Accordion style component for FAQ page. 4. Text modules for legal pages. | Please list any new components that is absolutely necessary on any of the above noted pages as part of this template | ||||||||||
38 | |||||||||||||||
39 | |||||||||||||||
40 | |||||||||||||||
41 | |||||||||||||||
42 | |||||||||||||||
43 | |||||||||||||||
44 | |||||||||||||||
45 | |||||||||||||||
46 | |||||||||||||||
47 | |||||||||||||||
48 | |||||||||||||||
49 | |||||||||||||||
50 | |||||||||||||||
51 | |||||||||||||||
52 |