How shadman1077/osus-eye-website works
Project type and purpose
• This is a static, bilingual marketing website (“OSUS Eye Website”) exported from Webflow.
• Purpose: serve responsive, SEO-optimized HTML/CSS/JS pages (in two locales) with rich media (images, fonts, videos).
File structure
• Top level:
• HTML pages (e.g., index.html, community.html, discover.html, etc.)
• css/ (normalize.css, webflow styles)
• js/ (webflow.js)
• fonts/ (GTAmericaArabic .otf)
• images/ (static images folder)
• videos/ (MP4/WebM versions)
• en/ (mirrors of top-level HTML pages for “en” locale)
• documents/ (animation JSON)
• No backend code, APIs, or database layers—purely static assets.
README
• Confirms static Webflow export, bilingual support, responsive design, SEO focus, modern-browser compatibility.
• No custom server logic, no dynamic data fetching.
a. Main components
1. Client (Web Browser)
2. CDN / Web Server (e.g., Netlify, S3 + CloudFront, GitHub Pages)
3. Static Assets
– HTML pages (root and /en)
– CSS files (normalize.css, osus-eye-website.webflow.css, webflow.css)
– JavaScript (webflow.js)
– Fonts (GTAmericaArabic)
– Images
– Videos (MP4/WebM)
– Documents (JSON animations)
4. External Services (optional)
– DNS provider
– Analytics (Google Analytics or similar)
– SEO crawler/Search engines
b. Relationships and interactions
• Client → CDN/Web Server: HTTP(S) requests
• CDN/Web Server → Client: serves static HTML, CSS, JS, media assets
• Browser: renders HTML, applies CSS, executes JS (Webflow runtime), requests images/fonts/videos
• (Optional) Browser → Analytics endpoint: tracks page views
• Search engine crawlers traverse public URLs for SEO.
c. Architectural patterns/design principles
• Static site hosting (no server-side rendering or dynamic API).
• Bilingual content via directory structure (/en prefix).
• Separation of concerns: structural HTML, presentation CSS, behavior JS.
• Asset optimization: separate directories for fonts, images, videos.
d. Key technologies/frameworks
• Webflow-generated HTML/CSS/JS
• CDN or static-site host (e.g., AWS S3 + CloudFront, Netlify)
• Standard web assets (HTML5, CSS3, ES5 JS)
• JSON for animations
Essential architectural elements
• Explicitly separate localization paths (/ vs /en).
• Static hosting layer and absence of application server.
• Asset types and their delivery flow.