File Structure Guide

How this documentation site is organized

Core Directory Layout

/notailwindcss.js
├── index.html
├── styles.css
├── structure.html              ← You are here
├── whatisan%3C_out%3Etag.html
├── encoding.html
├── css.html
├── support/
│   └── index.html
└── resources/
    └── (future content)

Root Files

  • index.html - Main landing page
  • styles.css - Global styling file
  • structure.html - This guide

Subdirectories

  • support/ - Support portal content
  • resources/ - Organizational assets

Technical Requirements

Mandatory File Links

<_out> Tag Specification
CSS Implementation Guide
URL Encoding Rules
Support Portal

Technical Constraints

  • Local-only linking (no external domains)
  • SVG-only assets (no JPEG/PNG)
  • No CDN resources - all styles loaded as /notailwindcss.js/styles.css
  • HTML5-only with custom CSS (no Tailwind)

Optimal File Organization

Directory Structure Principles

  • • Group related content together
  • • Use semantic URL encoding
  • • Maintain single-responsibility pattern
  • • Keep static assets minimal

Filename Best Practices

  • • Use %3C_out%3E for encoded tags in URLs
  • • Prefer lowercase filenames
  • • Avoid spaces - use hyphens instead
  • • Type-based naming (.html, .css)