Initial mirror of the HPE Design System

Readable mirror of https://design-system.hpe.design, sourced from
github.com/grommet/hpe-design-system (Apache-2.0) at commit 567c4d5
(2026-07-16).

The upstream site is a client-rendered Next.js export with no sitemap; it
returns a 1.5 KB empty shell to curl. This repo is the same guidance in plain
Markdown with every value resolved, plus the assets checked in.

Docs: scope and authority model, brand foundations with resolved color and
spacing tables, the design token tiers and version map, UI copy rules,
accessibility conformance and the responsibility split, the component and
template inventory, and an adoption/review checklist.

Assets: 452 SVG icons, 5 HPE and Aruba word-marks, 282 documentation graphics.

HOWTO-mirror-the-design-system.md is a verified runbook for rebuilding this
from scratch against a newer upstream.

Colors were resolved programmatically, not transcribed: token JSON stores
references, not values.

Apache-2.0 upstream. Note that it covers copyright, not trademark; Brand
Central remains authoritative for the HPE marks.
This commit is contained in:
2026-07-30 08:34:50 -04:00
commit 0730557624
752 changed files with 8423 additions and 0 deletions
@@ -0,0 +1,136 @@
WEBVTT Kind: captions; Language: en
00:05.225 --> 00:07.025
Hello, my name is Bill Tipton and
00:07.025 --> 00:09.334
I work for Hewlett Packard Enterprise
00:09.334 --> 00:10.925
as a Product Accessibility Champion.
00:12.358 --> 00:14.425
As part of my responsibilities,
00:14.725 --> 00:18.096
I educate and advise our product designers,
00:18.096 --> 00:20.289
developers, and decision-makers
00:20.289 --> 00:23.225
on accessible user experiences.
00:24.925 --> 00:27.399
Unfortunately in May of 1999,
00:27.399 --> 00:29.610
I suddenly went completely blind.
00:29.974 --> 00:33.174
Since then, I have used a screen reader daily
00:33.174 --> 00:35.825
to access the internet and other
00:35.825 --> 00:37.325
digital technologies.
00:38.725 --> 00:41.281
I often experience what it is like
00:41.333 --> 00:43.149
to attempt to use software with
00:43.425 --> 00:47.525
many accessibility and usability issues.
00:48.425 --> 00:51.414
It is not a pleasant feeling or experience
00:51.414 --> 00:54.811
when you are excluded from accessing a product
00:54.811 --> 00:58.705
due to technical issues that could have easily
00:58.705 --> 01:01.347
been avoided if somebody took the time
01:01.347 --> 01:05.525
to incorporate accessibility early in the
01:05.525 --> 01:08.499
design or development process.
01:09.845 --> 01:12.841
Although I am a member of the disabled community,
01:13.225 --> 01:16.225
I cannot speak for all people with disabilities.
01:17.325 --> 01:20.106
However, I personally would like the chance
01:20.120 --> 01:21.634
to be able to use all
01:22.025 --> 01:25.925
digital technologies including software effectively,
01:26.325 --> 01:28.922
so I am able to participate equally
01:28.922 --> 01:31.823
in all of life's digital opportunities.
01:31.800 --> 01:35.525
Through direct engagements, live demonstrations,
01:35.725 --> 01:37.425
and usability evaluations,
01:37.825 --> 01:42.525
I highlight the requirements, design standards, and value
01:42.278 --> 01:43.897
to our business success
01:43.897 --> 01:47.025
by supporting a diverse set of user personas,
01:47.325 --> 01:51.625
including our valued customers with disabilities.
01:52.725 --> 01:56.255
I encourage all researchers, product designers,
01:56.255 --> 01:59.391
developers, product managers, and others
01:59.391 --> 02:03.284
to incorporate accessibility and usability to create
02:03.284 --> 02:06.671
more accessible products and experiences.
02:06.682 --> 02:09.119
In life and in our work,
02:09.119 --> 02:12.625
it is important to continuously advocate for
02:12.625 --> 02:14.900
inclusive environments for all,
02:14.926 --> 02:17.441
including becoming an ally for our
02:17.425 --> 02:18.725
disabled community.
02:19.425 --> 02:20.299
Thank you, and now
02:20.299 --> 02:22.025
let's go out and create some positive change.