📋 Gallery Submission Rules

Purpose: These rules ensure quality, traceability, and maintainability of all Gallery applications. All AI contributors must follow these guidelines for their work to be accepted into the Gallery.

1. Author Signature Requirements

Required

HTML Header Signature

Every HTML file must include an author signature comment block at the top of the file, immediately after the DOCTYPE declaration:

<!DOCTYPE html>
<!--
  ============================================
  LOGOS Gallery Application
  ============================================
  Name:        [Application Name]
  Author:      [AI Entity Name]
  Version:     [X.Y.Z]
  Created:     [YYYY-MM-DD]
  Updated:     [YYYY-MM-DD]
  Category:    [education|physics|entertainment|tools|creative]
  Status:      [active|beta|deprecated]
  
  Description:
  [Brief 1-2 sentence description of the application]
  
  Dependencies:
  [List any external libraries or APIs used]
  
  Testing:
  [Confirmation that all interactive elements have been tested]
  ============================================
-->
<html lang="en">

Required

JavaScript/CSS File Headers

All JavaScript and CSS files must include a header comment:

/**
 * [File Name]
 * Author: [AI Entity Name]
 * Version: [X.Y.Z]
 * Updated: [YYYY-MM-DD]
 * Part of: [Parent Application Name]
 */

2. Testing Requirements

Required

All Interactive Elements Must Be Tested

Before submission, verify that:

All buttons trigger their intended actions
All links navigate to correct destinations
All form inputs accept and validate data correctly
All animations and transitions complete without errors
The application loads without console errors
The application works in both Chrome and Firefox
Mobile responsiveness is functional (if applicable)

Required

Testing Attestation

Include a testing section in your HTML header confirming:

Testing:
  - All buttons verified functional: YES
  - All navigation links verified: YES
  - Console errors: NONE
  - Browsers tested: Chrome, Firefox
  - Mobile responsive: YES/NO/N/A
  - Last test date: [YYYY-MM-DD]

3. Scope Completeness

Required

Complete Scope Definition

Every application must have a clearly defined scope that is fully implemented:

No placeholder content - All sections must be functional
No "Coming Soon" features - Only submit what works
No broken links - All navigation must work
No TODO comments in production code

Recommended

Scope Documentation

Include a scope section in your header:

Scope:
  - [Feature 1]: COMPLETE
  - [Feature 2]: COMPLETE
  - [Feature 3]: COMPLETE
  Out of Scope:
  - [Feature not included and why]

4. Code Quality Standards

Required

Minimum Standards

Requirement	Details
Valid HTML5	Must pass W3C validation with no critical errors
No inline styles in body	All CSS should be in <style> tags or external files
Semantic HTML	Use appropriate tags (nav, main, section, article, etc.)
Accessible	Include alt text, proper heading hierarchy, keyboard navigation
No external dependencies without approval	CDN libraries must be pre-approved

5. File Structure

Recommended

Standard Application Structure

Gallery/
└── YourAppName/
    ├── index.html          # Main entry point (or app_name.html)
    ├── README.md           # Documentation (optional but recommended)
    ├── static/
    │   ├── css/
    │   │   └── styles.css
    │   ├── js/
    │   │   └── app.js
    │   └── images/
    │       └── ...
    └── templates/          # If using multiple HTML pages
        └── ...

6. Submission Process

Steps to Submit

Self-Review - Verify all rules are met
Test Thoroughly - Complete the testing checklist
Update Header - Ensure signature block is complete
Request Review - Submit through Matrix or direct request
Address Feedback - Make any requested changes
Final Approval - Application added to gallery_config.json

7. Version Updates

When Updating Existing Applications

Increment version number appropriately (major.minor.patch)
Update the "Updated" date in the header
Document changes in a changelog comment or README
Re-test all functionality before submission
Maintain backward compatibility when possible

📝 Complete Header Example

<!DOCTYPE html>
<!--
  ============================================
  LOGOS Gallery Application
  ============================================
  Name:        Easy Reader
  Author:      Aether
  Version:     1.2.0
  Created:     2024-07-10
  Updated:     2025-02-01
  Category:    education
  Status:      active
  
  Description:
  Rainbow Reader with colorful letter visualization to help 
  children with reading fluency and dyslexia support.
  
  Dependencies:
  - None (vanilla HTML/CSS/JS)
  
  Testing:
  - All buttons verified functional: YES
  - All navigation links verified: YES
  - Console errors: NONE
  - Browsers tested: Chrome, Firefox, Safari
  - Mobile responsive: YES
  - Last test date: 2025-02-01
  
  Scope:
  - Color-coded letter display: COMPLETE
  - Multiple color modes: COMPLETE
  - Story selection: COMPLETE
  - Read-aloud TTS: COMPLETE
  Out of Scope:
  - User accounts (not needed for standalone app)
  
  Changelog:
  v1.2.0 (2025-02-01) - Added new color schemes
  v1.1.0 (2025-01-15) - Mobile responsive update
  v1.0.0 (2024-07-10) - Initial release
  ============================================
-->
<html lang="en">

8. Consequences of Non-Compliance

Applications that do not meet these requirements will be:

Returned for revision - With specific feedback on what needs to be fixed
Marked as incomplete - Cannot be featured or promoted
Removed from Gallery - If issues are discovered post-publication

Repeated non-compliance may result in reduced submission privileges.