FLUNEX: learning English starts with speaking.
English starts with speaking. Automation supports the experience.
HTML · CSS · JavaScript · Hostinger · Google Apps Script · Google Sheets · Looker Studio · WhatsApp · Git
What changes.
Speak from the start.
A structured A1 programme, with lessons and goals aligned to CEFR.
Operations support the learning.
Reminders, attendance and follow-up connected through WhatsApp and Sheets.
How it was built.Decisions, evidence and details
Stack
HTML
CSS
JavaScript
Hostinger
Google Apps Script
Google Sheets
Looker Studio
WhatsApp
Git
report_problem
Problem
- • Overemphasis on grammar instead of real communication.
- • Fragile technical stacks that are hard to maintain.
- • Misalignment between pedagogy, UX, and automation.
- • Limited control for educators over structure and evolution.
The challenge was to scale without increasing complexity while remaining pedagogically solid and technically resilient.
lightbulb
Solution
- • Speaking-first learning design.
- • CEFR-aligned course structure.
- • HTML-based content delivery.
- • Automation-ready architecture.
- • Clear separation between content, logic, and systems.
A static-first, modular platform that prioritizes stability, predictability, and iteration speed.
badge
My role
- • Designed the pedagogical architecture (A1-B1, CEFR-aligned).
- • Defined the UX structure and navigation logic.
- • Implemented the platform with HTML, CSS, and JavaScript.
- • Designed automation workflows (WhatsApp, Sheets, dashboards).
- • Established versioning and refactoring strategies.
school
Pedagogical architecture
- • Speaking-first methodology grounded in CLT and TBLT.
- • Full alignment with CEFR standards.
- • 12 units per level with lessons A/B/C.
- • Objectives, grammar, vocabulary, and pronunciation per unit.
- • Everyday English and exit checks to ensure progress.
- • Modular structure that scales without breaking UX or automation.
account_tree
Technical architecture
- • HTML, CSS, and vanilla JavaScript.
- • Static deployment on Hostinger.
- • Git-based version control.
- • No backend, SSR, PHP, or database dependencies.
- • Externalized automation and data handling.
Result: high stability, minimal maintenance, and predictable behavior.
settings_suggest
Automation & systems
- • WhatsApp-based reminders and attendance.
- • Google Apps Script workflows.
- • Google Sheets as datastore.
- • Analytics dashboards in Looker Studio.
- • AI-powered agents for onboarding and sales.
Automation was designed to support educators, not replace them.
view_quilt
UX & UI decisions
- • Low cognitive load and clear navigation paths.
- • Mobile-first and responsive layout.
- • Consistent layout patterns.
- • Clean typography, neutral palette, and visual hierarchy.
- • Reusable components and consistent spacing.
build
Challenges & solutions
- • Platform instability -> static-first architecture.
- • Content scalability -> strict modular structure and naming conventions.
- • Automation complexity -> decoupled systems from the core platform.
- • UX inconsistency -> centralized templates and reusable components.
emoji_events
Results
- • Stable production deployment.
- • Fully structured A1 program.
- • Automation systems in active use.
- • Scalable foundation for A2 and B1.
- • Reusable architecture for future EdTech products.
psychology
Key learnings
- • Simplicity scales better than complexity.
- • Pedagogical structure is system architecture.
- • Static systems outperform fragile backends.
- • Automation should enhance human teaching.
- • Versioning and refactoring are essential.