← Hub Versioning & Deprecation
v10.0
01 Overview Component lifecycle at a glance

Every component in the GFS Design System follows a strict lifecycle from introduction to retirement. This page tracks status for every component, documents migration paths for consolidated pages, logs breaking changes, and defines the deprecation policy.

0
Current
0
Legacy
0
Deprecated
0
Removed
■ Counts update live based on the registry below
02 Versioning System Component lifecycle stages

Every GFS component moves through four lifecycle stages. Status is tracked per-component, not per-page — a single page can contain components at different lifecycle stages. The design system lead is responsible for all status transitions.

Current
Actively maintained, tested, and documented. Use this for all new work. Receives bug fixes and enhancements.
Use freely
Legacy
Still functional, but a newer replacement exists. Receives critical bug fixes only. A documented migration path is available.
Migrate when possible
Deprecated
Scheduled for removal. Do not use for new work. Existing usage must be migrated within the 90-day grace period.
Do not use — migrate now
Removed
Deleted from the codebase. Archived in the changelog for historical reference. No support of any kind.
Gone — see changelog
Transition Rules
Current → Legacy
When a replacement component is shipped and documented. No deadline on migration.
Legacy → Deprecated
When the team decides to remove the old component. Starts the 90-day grace period.
Deprecated → Removed
After 90 days. Files are deleted, code is archived in the changelog entry.
■ All transitions are announced in the changelog and flagged with a badge on the component page
03 Component Status Registry Full inventory — sortable & filterable
0 components
Component Category Version Status Since Migration Path
■ Click column headers to sort · Use filters to narrow by status · Search matches component or category name
04 Migration Guides Consolidated & renamed components

During the v10.0 consolidation, several standalone pages were merged into unified references. Below are step-by-step migration guides for each consolidation. Click any card to expand the full guide.

icons-expanded-1/2/3.html icons.html Icon Library Consolidation
What Changed

Three separate icon pages (icons-expanded-1.html through icons-expanded-3.html) were merged into a single icons.html with 616 SVG icons across 30 categories. All icons are now searchable from one location.

Before
<!-- Linking to separate icon pages --> <a href="icons-expanded-1.html">Icons A-H</a> <a href="icons-expanded-2.html">Icons I-P</a> <a href="icons-expanded-3.html">Icons Q-Z</a>
After
<!-- Single unified icon page --> <a href="icons.html">Icon Library (616 icons, 30 categories)</a> <!-- Deep link to a category --> <a href="icons.html#s-navigation">Navigation Icons</a>
Action Required

Update all internal links from icons-expanded-*.html to icons.html. Icon SVG markup is unchanged — no code modifications needed.

social.html + social-mega.html social.html Social Card Consolidation
What Changed

The social-mega.html mega-collection was absorbed into the main social.html page, which now contains 120+ social card templates across 13 categories. All original card patterns were preserved.

Before
<!-- Two separate social pages --> <a href="social.html">Social Cards (Basic)</a> <a href="social-mega.html">Social Cards (Full Collection)</a>
After
<!-- Unified social page --> <a href="social.html">Social Cards (120+ templates, 13 categories)</a>
Action Required

Replace all social-mega.html links with social.html. Card class names are unchanged.

animations-1.html ... animations-8.html animations.html Animation Library Consolidation
What Changed

Eight separate animation pages were merged into a single animations.html with 105+ animations across 47 sections covering CSS, GSAP, Lottie, Framer Motion, Anime.js, Three.js, Spring, and Scroll-driven patterns.

Before
<a href="animations-1.html">CSS Transitions</a> <a href="animations-2.html">CSS Keyframes</a> <a href="animations-3.html">GSAP</a> <a href="animations-4.html">Lottie</a> <a href="animations-5.html">Framer Motion</a> <a href="animations-6.html">Anime.js</a> <a href="animations-7.html">Three.js</a> <a href="animations-8.html">Scroll-Driven</a>
After
<!-- Single animation reference --> <a href="animations.html">Animation Library (105+ animations)</a> <!-- Deep link to a library section --> <a href="animations.html#s-gsap">GSAP Animations</a> <a href="animations.html#s-lottie">Lottie Animations</a>
Action Required

Update all links. Animation CSS class names and keyframe names are unchanged. JS initialization code for GSAP/Lottie is identical.

documents.html, writing.html, email-templates.html, proposals.html documents.html Document Templates Consolidation
What Changed

Four separate document-related pages were merged into documents.html covering templates, writing guidelines, email templates, and proposal formats in one unified reference.

Action Required

Update all internal links to point to documents.html. Use section anchors for deep linking to specific template categories.

marketing.html, sales-tools.html, competitive.html marketing.html Marketing Suite Consolidation
What Changed

Three pages covering marketing strategy, sales tools, and competitive analysis were combined into marketing.html with 35 sections.

Action Required

Update all internal links to marketing.html. Section IDs remain stable for deep linking.

netsuite.html, suitelet-templates.html, netsuite-portals.html netsuite.html NetSuite UI Consolidation
What Changed

Three NetSuite-related pages were merged into netsuite.html with 21 mockups covering records, Suitelets, and portals.

Action Required

Update links. Note that the Suitelet button class was renamed from .btn to .app-btn in Suitelet contexts to avoid CSS conflicts. See Breaking Changes (Section 05) for details.

■ Click any migration card to expand the full guide with before/after code examples
05 Breaking Changes Log Changes that could break existing usage

Breaking changes are modifications to existing classes, IDs, file names, or markup structure that could cause regressions in pages consuming the design system. All breaking changes are versioned and logged here.

Version Type Before After Affected Scope Notes
v10.0 Rename .btn .app-btn Suitelet templates in netsuite.html Renamed in Suitelet contexts to avoid collision with design system .btn class. Design system .btn unchanged.
v10.0 Delete icons-expanded-1.html icons.html All pages linking to expanded icon pages Three files removed; unified into icons.html
v10.0 Delete icons-expanded-2.html icons.html All pages linking to expanded icon pages See icons-expanded-1 entry above
v10.0 Delete icons-expanded-3.html icons.html All pages linking to expanded icon pages See icons-expanded-1 entry above
v10.0 Delete social-mega.html social.html Hub links, bookmarks Mega collection merged into social.html
v10.0 Delete animations-1.html ... animations-8.html animations.html All pages linking to individual animation libraries 8 files removed; 105+ animations unified
v10.0 Move netsuite.html netsuite.html NetSuite Suitelet references, portal links Merged records, Suitelets, and portals into one page
v10.0 Rename #s01, #s02 ... (generic IDs) #s-colors, #s-typography ... (semantic IDs) foundation.html deep links Section IDs made semantic for better deep linking
v10.0 Change grid-template-columns: repeat(N, 1fr) grid-template-columns: repeat(N, minmax(0,1fr)) All grid utilities (.g2 through .g6) Prevents overflow on long content; existing layouts may shift slightly
v10.0 Change box-shadow on cards border: 1px solid var(--silver) All card-like components Flat design directive: no shadows, 1px borders only
v10.0 Move documents.html documents.html Document template links Writing, email, and proposal templates merged in
v10.0 Move marketing.html marketing.html Marketing and sales links Strategy, sales tools, competitive merged into 35-section page
v10.0 Rename .card (generic) Context-specific classes Layout cards across all pages Avoid generic .card for layout; use purpose-specific class names
■ Always check this log before upgrading · Breaking changes are cumulative across versions
06 Deprecation Policy How components are retired
Deprecation Timeline
Day 0
Announcement
Deprecation notice added to the changelog. Component page receives a red "Deprecated" badge in its section header. Status updated in this registry.
Day 1 – 60
Grace Period
Component continues to function. Migration guide is published here. Teams are notified and expected to begin migrating. Bug fixes for critical issues only.
Day 61 – 90
Final Warning
Reminder notice issued. Remaining consumers are contacted directly. No further bug fixes. Component renders a console warning in dev builds.
Day 91
Removal
Component files are deleted. Source code is archived in the changelog entry with a full snapshot. Status updated to "Removed" in this registry.
How Deprecation Is Announced
01 A timestamped entry is added to changelog.html with the component name, reason, and replacement.
02 The component's section header receives a Deprecated badge visible on the page.
03 This versioning page is updated with the new status and migration path.
04 The hub index.html entry is annotated with a yellow warning indicator.
How to Request Keeping a Deprecated Component
01 File a request with the design system lead (currently Michael Levine) before Day 60 of the grace period.
02 Provide a written justification explaining why migration is not feasible within the grace period.
03 If approved, the component receives a 90-day extension (one extension maximum). The status remains "Deprecated" throughout.
04 If denied, the original Day 91 removal date stands. No further appeals.
Archive Location

All removed components are archived in two locations:

Changelog
Full HTML snapshot is stored inline in the changelog.html entry for the version that removed it.
Dropbox Archive
Original files are moved to Dropbox/GFS New Team Folder/GFS x Claude AI/Design System Archive/
■ 90-day grace period · One extension allowed · All removed code is archived, never permanently lost
← Back to Hub · GFS Design System v10.0 · Global Food Solutions, Inc. · Edgewood, NY