How dangnhutnguyen/azota-bypass-website-container-show works
Project type and purpose
• This is a single-page, static, front-end tool (index.html + script.js) hosted on GitHub Pages.
• Purpose: Load the AZOTA web-app in a controlled iframe or window, accept warnings automatically, maintain 16:9 ratio, and let the user interact/bypass certain restrictions.
File structure
• README.md: usage instructions and user flow.
• index.html: the only HTML entry point (UI shell).
• script.js: all the business logic—injecting/controlling the AZOTA page, setting window ratio, handling inputs (URL, password, email), button events.
Key components
a. User (Browser) – the end user running the tool in a modern browser.
b. Static Host (GitHub Pages) – serves index.html and script.js.
c. UI Shell (index.html) – input fields (AZOTA URL, password, email), “Load Website” button, embedded view.
d. Client-Side Logic (script.js) –
• Reads user inputs
• Opens/embeds the AZOTA URL in a controlled window or iframe
• Listens/accepts any warning dialogs automatically
• Enforces window size (16:9 ratio)
e. External Service (AZOTA) – the remote examination platform; runs inside the embedded view.
Relationships and data flow
• User → (interacts) → UI Shell
• UI Shell → (passes inputs) → Client-Side Logic
• Client-Side Logic → (embeds/controls) → External AZOTA Service
• External AZOTA Service → (renders inside) → UI Shell/Browser
• All static assets ← (served by) ← GitHub Pages
Architectural patterns & design principles
• Single-Page Application (SPA) style, but no framework—vanilla JS.
• Host–Client separation: static host only serves files; all logic runs in the browser.
• Encapsulation of external service in an isolated container (iframe or window).