You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following is our roadmap for handling Cloud PAL's offboarding, transitioning the existing site to a legacy site, and creating our new C4IP site.
1. Cloud PAL Phase 2
Apply top banner to our site pushing people to the Cloud PAL site. Publish: ASAP
Put banners on all Cloud PAL pages that live on the C4IP legacy site, giving users time to adjust to the fact that Cloud PAL is separating. Complete when Travis issue is overcome in collaboration with Stephanie.
Note we will leave all the Cloud PAL pages on the legacy site. This will make it a v10/v11 mash up. The new site will not have the Cloud PAL pages.
The old site will live on as a legacy V10/V11 site. Meanwhile the new site will:
Present the new IA and improved content, and come into alignment with all other Carbon sites, starting with deletion of Cloud PAL pages in the new site (already merged).
Rather than starting from the ground up, we will be building based on legacy site which is Gatsby v 3, Carbon Gatsby version 2.3.2. Our approach will be highly subtractive.
Note this method carries over the many navigation bugs on the existing site, which needs issues to fix.
We will explore using tags in the LHN for PLG patterns. And we need to consider the need for 3rd level navigation, and the possibility of implementing tree view. Finally, our approach paves the way for using docs templates for Core, which would include the addition of demo and the accessibility cards and tags.
Create issues to delete any junk pages
Look at site efficiency (i.e. file structure for images)
The text was updated successfully, but these errors were encountered:
The following is our roadmap for handling Cloud PAL's offboarding, transitioning the existing site to a legacy site, and creating our new C4IP site.
1. Cloud PAL Phase 2
2. Create new repository to host new website
3. New site
All issues relating to the new site live here
The old site will live on as a legacy V10/V11 site. Meanwhile the new site will:
The text was updated successfully, but these errors were encountered: