Living Style Guide - This page demonstrates all design patterns and components using semantic HTML with minimal component classes.

Edit _data/style-guide-content.md or _data/styleGuideData.js to update examples.

Markdown Content Examples

Typography Examples

This is a regular paragraph with bold text, italic text, and inline code. Here’s a link example.

Heading Level 2

Heading Level 3

Lists

Unordered List

Ordered List

  1. First step in the process
  2. Second step with code
  3. Third step with important information

Code Examples

Inline code: const example = "hello world";

Block code:

function greet(name) {
  return `Hello, ${name}!`;
}

const result = greet("World");
console.log(result);

Blockquotes

This is a regular blockquote. It should be styled distinctly from alerts and callouts. It can span multiple lines and paragraphs.

GitHub-Style Alerts

Note

Highlights information that users should take into account, even when skimming.

Tip

Optional information to help a user be more successful.

Important

Crucial information necessary for users to succeed.

Warning

Critical content demanding immediate user attention due to potential risks.

Caution

Negative potential consequences of an action.

Complex Example

Here’s a paragraph with a callout:

Warning

This is critical information that demands immediate attention.

Followed by more regular text and a code block:

// Example of compliance checking
const checkCompliance = (product) => {
  return product.hasSecurityUpdates &&
         product.hasDocumentation &&
         product.vulnerabilityTracking;
};

FAQ List Component (Simple Links)

Component: components/faq-list-simple.njk | Data: styleGuideData.sampleListFaqs

🚀 Getting Started Questions

Basic questions about the Cyber Resilience Act

FAQ Accordion Component

Component: components/faq-accordion.njk | Data: styleGuideData.sampleAccordionFaqs

🔧 Technical Questions

Detailed technical questions with expandable answers

How do I implement security updates?

Security updates should be implemented promptly following your organization’s change management process. Always test in a staging environment first.

Warning

Never deploy updates directly to production without testing.

Key steps:

  1. Review the security advisory
  2. Test in staging
  3. Deploy during maintenance window
What documentation is required for compliance?

You need to maintain comprehensive documentation including:

  • Risk assessments
  • Security measures implemented
  • Incident response procedures
  • Vulnerability management process

Tip

Keep all documentation version-controlled and easily accessible for audits.

How should I handle vulnerability disclosure?

Establish a clear vulnerability disclosure policy that includes:

Important

Your disclosure timeline should align with the severity of the vulnerability.

Create a security.txt file and publish contact information for security researchers.

Status Badges

Component: components/faq-badges.njk | Data: styleGuideData.sampleBadgeFaqs

Status badges appear on FAQs to indicate their review state. They use <data> elements with semantic values.

Navigation Cards

Used on home page and list indexes with hover effects and arrows. Uses .card-grid and .card classes.

Half-Width Cards

Cards can be displayed in a two-column layout using .card-grid.half-width.

Disclaimer/Warning Block

Uses semantic <aside> element.

Semantic HTML Structure

Markup Philosophy

The templates use semantic HTML5 elements with minimal component classes:

CSS Architecture

Hybrid Approach

uses a hybrid CSS architecture combining semantic HTML with light component classes:

Component Classes

Utility Classes

CSS Features