Custom Code and AI-Generated Content Guidelines

To ensure all website content remains accessible, consistent, and maintainable, editors should avoid adding custom or AI-generated code that overrides the site’s design system or introduces unsupported layouts.

Core Principle

If you need custom styling or layout beyond what the system provides, contact the web team instead of creating a workaround.

What is NOT allowed

Editors should not paste or create custom code generated by tools like ChatGPT, Copilot, or similar tools if it includes:

1. Inline styling

Avoid using:

style="font-size:18px; font-family:Arial; color:#333;" etc

Why this matters:

• Breaks site-wide consistency
• Overrides accessible font and contrast settings
• Makes future updates difficult

2. Custom layout systems

Do not add:

display:flex, grid, or custom column layouts
Bootstrap, Tailwind, or other framework classes
Manually created multi-column designs

Why this matters:

• Can break responsive behavior
• Often fails accessibility requirements (reading order, zoom, mobile)
• Conflicts with existing theme styles

3. Font overrides

Do not change:

font family
font size outside heading options
line height or spacing

Why this matters:

• Reduces readability and accessibility
• Creates inconsistent user experience

4. Embedded scripts or style blocks

Do not include:

<script>...</script>
<style>...</style>

Why this matters:

• Security risk
• Not supported in most CMS environments
• Can interfere with global functionality
• Can compromise the entire web ecosystem (crash the entire website)

5. Excessive or unnecessary HTML

Avoid:

deeply nested <div> or <span> elements
copying full HTML sections from external tools

Why this matters:

• Makes content harder to maintain
• Can introduce accessibility issues (missing structure, poor semantics)

What TO do instead

1. Use built-in components

Always use:

• approved heading styles (H2, H3, etc.)
• lists, tables, and buttons provided by the system
• pre-designed layout blocks

2. Keep content semantic and simple

Structure content using:

• proper headings (no skipping levels)
• paragraphs and lists instead of styled text

3. Request enhancements when needed

If something isn’t possible with existing tools contact the web team and provide an example of what you’re trying to achieve.

We can:

• create reusable components
• ensure accessibility compliance
• maintain consistency across the site