Add banners to indicate this resource is experimental

[caufieldjh]

The main Dismech page and the disorder browser page should clearly indicate that Dismech is in a pre-alpha experimental stage and is undergoing continual development.
This could take the form of highly visible banners at the top of each page.

[github-actions]

Issue Summary

This issue requests adding visible banners to the Dismech website indicating that the resource is in a pre-alpha experimental stage and undergoing continual development.

Context & Current State

Dismech currently has three main HTML entry points:

1. Main landing page (/index.html) - Polished hero section with feature descriptions
2. Disorder browser (/app/index.html) - Faceted search interface for exploring disorders
3. Individual disorder pages (generated from /src/dismech/templates/disorder.html.j2)

Currently, none of these pages display any warning or notice about the experimental nature of the resource. The landing page presents Dismech as a professional, production-ready tool with statements like "A curated, evidence-backed knowledge base" without qualifying that it's in early development.

Why This Matters

User expectations: Without an experimental/pre-alpha banner, users may:

• Assume the data is comprehensive and production-ready
• Cite incomplete or evolving information in publications
• Not realize that definitions and classifications may change
• Miss the opportunity to provide feedback during active development

Best practices: Similar research databases often use banners like:

• "Beta version - Content under active curation"
• "Experimental resource - Not for clinical use"
• "Pre-release - Data subject to change"

Implementation Approach

The banners should be added to:

1. Main Landing Page (/index.html)

Add a prominent banner above or within the hero section, potentially styled as:

<div class="experimental-notice">
  ⚠️ <strong>Experimental Resource:</strong> Dismech is in pre-alpha development. 
  Content is actively being curated and may be incomplete or subject to change.
</div>

2. Disorder Browser (/app/index.html)

Add a notice banner above the search interface, possibly with a dismissible option:

<div class="beta-banner">
  This is an experimental browser for a knowledge base under active development. 
  Data completeness and accuracy are continually improving.
</div>

3. Disorder Page Template (/src/dismech/templates/disorder.html.j2)

Add a notice in the page header or breadcrumb area to ensure every disorder page shows the warning.

Design Considerations

Visual prominence:

• Use attention-grabbing but not alarming colors (amber/yellow rather than red)
• Make it visible without dominating the page
• Consider using an info icon or warning symbol

Messaging:

• Keep it concise (1-2 sentences)
• Clearly state the experimental nature
• Optionally link to a page explaining development status
• Consider adding a link to the GitHub issues for feedback

Example styling (based on current color scheme):

.experimental-notice {
    background: linear-gradient(135deg, #fef3c7 0%, #fde68a 100%);
    color: #78350f;
    padding: 16px 24px;
    border-radius: 8px;
    border-left: 4px solid #f59e0b;
    margin-bottom: 20px;
    font-size: 0.95rem;
}

Related Patterns

Looking at similar biomedical resources:

• Human Cell Atlas: Uses "Data Portal (Beta)" in header
• Alliance of Genome Resources: Shows version number and "Release candidate" badges
• Reactome: Has version info and "under development" notices for new features

Suggested Next Steps

1. Design banner text and styling that matches the existing Dismech aesthetic
2. Add banner component to all three page types
3. Consider adding a "About the Data" or "Development Status" page linked from the banner
4. Optionally add a dismissible cookie-based notice for returning visitors

Related Issues

No directly related issues found, but this complements:

• Compliance and quality assurance efforts (dismech-compliance skill)
• Evidence validation work (dismech-references skill)
• Overall data maturity improvements

---

Implementation complexity: Low - This is primarily a frontend HTML/CSS update requiring edits to 2-3 template files.

Priority: Medium-High - Important for setting appropriate user expectations before wider promotion of the resource.