DURATION

12 WEEKS

DELIVERY

INSTRUCTOR-LED
MON–THU

100% PRACTICAL

LABS/
PORTFOLIO PROJECTS

COMPLETION

CERTIFICATION

Programme Overview

This practical 12-week programme teaches semantic HTML, CSS, JavaScript and React alongside the production of reflowable EPUB 3 publications. Three monthly portfolio projects assess independent production, debugging, testing and documentation. EPUB work begins early and is distributed across Weeks 2 to 4.

Learning outcomes

  • Create responsive, accessible websites using HTML and CSS, with Git and GitHub for version control.
  • Write JavaScript for DOM interaction, forms, state and asynchronous API consumption; develop a component-based React application.
  • Prepare structured DOCX manuscripts and explain EPUB 3 anatomy, metadata, navigation and reading order.
  • Navigate Sigil, edit XHTML/CSS and EPUB resources, and repair a Calibre-generated EPUB.
  • Validate EPUB format with EPUBCheck, evaluate accessibility with Ace by DAISY and manual review, and test reading experiences.
  • Deliver three documented portfolio projects with repeatable quality assurance.
Level & Delivery
Beginner to Junior
Instructor-Led
Guided Labs & Projects
From Semantic HTML to a Validated EPUB 3 in One Practical Programme

Why Enroll?

Frontend Development and EPUB Production is a revised 12-week curriculum delivered by Ibadan Digital Academy. You will build responsive, accessible websites with HTML, CSS, JavaScript and React, and produce reflowable EPUB 3 publications with Calibre, Sigil, EPUBCheck and Ace by DAISY. Every session follows explanation, demonstration, guided practice and independent application, and each month ends with a documented portfolio project that mirrors real publishing and product work.

Dual Skill Set:

Semantic HTML, CSS, JavaScript and React alongside professional reflowable EPUB 3 production.

Three Portfolio Projects:

Monthly assessed projects: a professional EPUB conversion, an interactive website and a React publishing hub.

Production QA Discipline:

EPUBCheck, Ace by DAISY, manual accessibility review and reader testing on every release.

Instructor-Led Delivery:

Monday to Thursday, 11:00 a.m. to 2:00 p.m., with Friday optional for project completion, corrections and mentorship.

Job-Ready Portfolio:

Published websites, validated EPUB 3 titles and accessibility reports you can show employers.

How the Programme Runs

Delivery & Assessment

Teaching runs Monday to Thursday, 11:00 a.m. to 2:00 p.m.; Friday is optional for project completion, corrections and mentorship. At 12 scheduled hours per week, the EPUB sequence is distributed across Weeks 2, 3 and 4. Independent practice is approximately 5 to 7 hours weekly.

  • Weekly labs: 20%
  • Month 1 EPUB project: 20%
  • Month 2 interactive website: 20%
  • Month 3 React capstone: 30%
  • Professional practice: 10%

Evidence includes completed source files, functioning outputs, Git history, accessibility and validation reports, and demonstrations.

12-Week Curriculum

Frontend Development & EPUB Production Outline

Month 1 — Web Foundations and EPUB Production

Week 1. Web foundations, HTML and Git — Tolu

  • Topics: web architecture, paths, editor and terminal, Git, headings, paragraphs, lists, links, images, tables, forms and semantic structure.
  • Practical: build a semantic article and a three-page mini site; compare logical HTML with poorly formatted manuscript content.
  • Exit: commit and explain semantic page structure, heading hierarchy and relative paths.

Week 2. CSS foundations and Sigil orientation — Ismael & Olaide

  • Topics: selectors, cascade, typography, box model, Flexbox and conservative reflowable eBook CSS; Sigil Book Browser, Code View, Preview and resource organisation.
  • Practical: style a web article; open a sample EPUB in Sigil, locate chapters, CSS, images and navigation, then make and verify a basic XHTML/CSS edit.
  • Exit: identify Sigil’s principal areas and verify a basic edit in a saved copy.

Week 3. Responsive design and EPUB source preparation — Ismael & Olaide

  • Topics: CSS Grid, mobile-first design and accessibility; Word heading styles; front, body and back matter; EPUB package anatomy (manifest, spine, navigation) and required metadata.
  • Practical: clean a deliberately messy DOCX, build a chapter map, then correct one chapter boundary, one internal link and one navigation entry in Sigil.
  • Exit: prepare a clean structured source and explain navigation, resources and reading order.

Week 4. EPUB production, quality assurance and delivery — Ismael & Olaide

  • Topics: Calibre DOCX to EPUB 3 settings, Sigil inspection and repair, XHTML/CSS, covers, image alternatives, EPUBCheck, Ace and reader testing in Thorium and Kindle Previewer.
  • Practical: convert, repair, validate, accessibility-check and reader-test an independently produced publication.
  • Exit: no unresolved EPUBCheck errors, with documented accessibility and reader checks.

Month 1 project: professional EPUB conversion (20%) — cleaned source manuscript, complete EPUB 3 with cover and correct metadata, navigation and reading order, EPUBCheck and Ace evidence, reader-testing notes, QC report and Git history.

Month 2 — JavaScript and Interactive Frontend

Week 5. JavaScript foundations and DOM — Paul & Olaide

  • Topics: values, conditionals, loops, functions, arrays, objects, scope, selectors and DOM updates.
  • Practical: build a pricing calculator, an interactive catalogue and debug scripts.
  • Exit: create and update DOM elements from JavaScript with functioning events.

Week 6. Events, forms, state and modules — Paul & Olaide

  • Topics: event propagation, form validation, localStorage, ES modules and code organisation.
  • Practical: build a form with errors and a filterable list with persisted preferences.
  • Exit: demonstrate correct form handling and persistence.

Week 7. Asynchronous JavaScript and APIs — Paul & Olaide

  • Topics: JSON, HTTP, fetch, promises, async/await, errors and loading/empty/success states; never embed secret credentials in frontend code.
  • Practical: build a book-data or media API search interface with robust failures.
  • Exit: show useful API results and graceful errors.

Week 8. Project 2 delivery — Paul & Olaide

  • Topics: responsive QA, accessibility, deployment, integration and presentation.
  • Practical: test phone, tablet and desktop, keyboard navigation, network failures and the production build.
  • Exit: deploy, document and demonstrate the full interface.

Month 2 project: interactive website (20%) — four to six pages for a publisher, academy or SME with three meaningful JavaScript behaviours, a fetch/JSON feature with loading and error states, accessible forms, Git history and a deployed URL.

Month 3 — React, Production Quality and Capstone

Week 9. React foundations

  • Topics: Vite, JSX, components, props, state, events, lists/keys, controlled forms and lifting state.
  • Practical: build book cards, filtered results and modal/details views.
  • Exit: explain component boundaries and state flow.

Week 10. React architecture and APIs

  • Topics: routing, reusable UI, introductory custom hooks, data loading, and error and empty states.
  • Practical: build digital-library views, a detail route and saved items.
  • Exit: demonstrate routed, data-driven screens.

Week 11. Testing, accessibility and deployment

  • Topics: behaviour-focused tests with Vitest/Jest and React Testing Library concepts, keyboard and focus QA, image performance and production builds.
  • Practical: write behavioural tests, complete a Lighthouse-informed review, deploy a beta and test deep links.
  • Exit: show a deployed, reviewed capstone before final week.

Week 12. Capstone release and presentation

  • Topics: fix defects, verify deployment and accessibility, document architecture and present work.
  • Practical: verify mobile and desktop experiences; inspect publication metadata and simulated EPUB QA status.
  • Exit: explain trade-offs, demonstrate user journeys and show QA evidence.

Month 3 project: React digital publishing hub (30%) — four or more routes with reusable navigation, cards and forms, a real JSON data source, search plus two further interactions, a publication detail screen showing metadata and EPUB QA status, at least five automated tests, a deployed build and a case-study README. No backend implementation is required.

Tools & Scope

Frontend, EPUB and Quality Assurance

  • Frontend: VS Code, browser developer tools, Git/GitHub, Node.js/npm for frontend tooling, Vite and React.
  • EPUB: Microsoft Word or LibreOffice Writer for DOCX cleanup, Calibre for DOCX to EPUB conversion, Sigil for EPUB editing, PageEdit for visual editing where appropriate, HTML/XHTML and CSS.
  • Quality assurance: EPUBCheck, Ace by DAISY, manual accessibility review, Thorium Reader and Kindle Previewer.

Scope: reflowable EPUB 3 and frontend development. PDF extraction, fixed-layout EPUB, advanced publishing features and backend development are outside the core assessment. PageEdit is a separate application rather than Sigil’s old integrated Book View, and Kindle Previewer checks the Kindle experience without replacing an EPUB-standard reading-system test.

EPUB Practical Progression

Competency Checklist

  • Orientation: open and save an EPUB; navigate Book Browser, Code View and Preview; recognise differences in older Sigil tutorials.
  • Source and conversion: inspect DOCX, apply real styles, select EPUB 3 in Calibre, and check the output version and structure.
  • XHTML and CSS: edit chapters, headings, links, image alternatives and reflowable styles in Sigil.
  • Navigation: inspect and generate contents navigation; verify chapter order and internal links.
  • Metadata: check required EPUB 3 metadata — title, identifier, language and modified timestamp — and add creator, rights and cover as appropriate.
  • Validation: EPUBCheck conformance, Ace automated findings and a separate human accessibility review.
  • Reader QA: Thorium EPUB review, Kindle-specific preview as an additional compatibility check, with fixes recorded.

Suggested compact lab sequence: 1. Sigil orientation; 2. clean DOCX; 3. examine package and chapter order; 4. convert to EPUB 3 with Calibre; 5. repair XHTML, CSS, navigation and metadata in Sigil; 6. validate and manually inspect accessibility; 7. reader-test and release. Guided labs use the same example publication, followed by an independent manuscript for assessment.

Get Started

Build responsive, accessible websites and publish professionally validated EPUB 3 books. Take the first step with the Frontend Development and EPUB Production programme at Ibadan Digital Academy.