Photograph: Shane Rounce on Unsplash

Learn Courses preview Course plans by Shane Rounce. Enrolment is not open.

← All courses

Warm sunlight dissolving into soft circles of light

Photograph: Shane Rounce on Unsplash

Course plan · Enrolment not openApplication engineering · Self-paced

React experiences with static public HTML and reliable sharing

With Shane Rounce

I teach react experiences with static public HTML and reliable sharing through a practical project, worked examples and checks that another person can repeat. This is a complete course plan; lesson recordings, workbooks and delivery are still to be produced.

4 weeks20 learning hoursSelf-paced

I’m developing this course as part of Learn Courses. This is the full teaching plan, ready to review before I produce the lessons and open enrolment.

IS THIS FOR YOU?

Who I’m building this for

Frontend developers building searchable public applications.

Before you begin

A computer with a current browser and permission to use the project material.
Basic familiarity with Git and the relevant development tools. Work takes place in an isolated test environment.
No client records, credentials or production changes are needed for the exercises.

PROPOSED COURSE FEE

£149

Provisional planning figure, not an approved price or an offer for sale. I have assumed reusable self-paced lessons and bounded support. Production effort, access period, assessment support and tax treatment need confirming before sale.

Planning price only. Enrolment is closed and no payment is taken.

Explore a sample learning space →

The sample is fictional. It is separate from this course’s future lessons.

A PRACTICAL NEXT STEP

What you’ll be able to do

Define which routes need indexable HTML and which require a signed-in application.
Build route-specific titles, canonical URLs and article content that remain present before JavaScript runs.
Generate distinct social images and metadata and test the actual anonymous response for several routes.
Check direct links, hydration, empty data, keyboard journeys and access failures on a staged deployment.

THE TEACHING PLAN

Your next 4 weeks

A clear route through the subject, with something to make, test or reflect on at every stage.

MODULE 1

Separate public pages from private state

I explain the decisions behind separate public pages from private state using worked examples, a deliberately broken case and a corrected version. The lesson distinguishes what the evidence establishes from what still needs checking.

Your practical activity: Define which routes need indexable HTML and which require a signed-in application.
How I’ll check your understanding: Submit the working artefact and a short evidence note for module 1: define which routes need indexable HTML and which require a signed-in application. Include the initial state, the chosen change, a meaningful failure case and the result of the check. I review whether the evidence supports the conclusion and return specific revisions where it does not.

MODULE 2

Render meaningful public HTML

I explain the decisions behind render meaningful public HTML using worked examples, a deliberately broken case and a corrected version. The lesson distinguishes what the evidence establishes from what still needs checking.

Your practical activity: Build route-specific titles, canonical URLs and article content that remain present before JavaScript runs.
How I’ll check your understanding: Submit the working artefact and a short evidence note for module 2: build route-specific titles, canonical URLs and article content that remain present before JavaScript runs. Include the initial state, the chosen change, a meaningful failure case and the result of the check. I review whether the evidence supports the conclusion and return specific revisions where it does not.

MODULE 3

Make each share preview useful

I explain the decisions behind make each share preview useful using worked examples, a deliberately broken case and a corrected version. The lesson distinguishes what the evidence establishes from what still needs checking.

Your practical activity: Generate distinct social images and metadata and test the actual anonymous response for several routes.
How I’ll check your understanding: Submit the working artefact and a short evidence note for module 3: generate distinct social images and metadata and test the actual anonymous response for several routes. Include the initial state, the chosen change, a meaningful failure case and the result of the check. I review whether the evidence supports the conclusion and return specific revisions where it does not.

MODULE 4

Release a navigable application

I explain the decisions behind release a navigable application using worked examples, a deliberately broken case and a corrected version. The lesson distinguishes what the evidence establishes from what still needs checking.

Your practical activity: Check direct links, hydration, empty data, keyboard journeys and access failures on a staged deployment.
How I’ll check your understanding: Submit the working artefact and a short evidence note for module 4: check direct links, hydration, empty data, keyboard journeys and access failures on a staged deployment. Include the initial state, the chosen change, a meaningful failure case and the result of the check. I review whether the evidence supports the conclusion and return specific revisions where it does not.

PUT IT INTO PRACTICE

Your final project

Build and document a complete practical project for react experiences with static public HTML and reliable sharing. Use an invented organisation or an expressly permitted personal project, join the four module artefacts into one coherent result and demonstrate a normal journey, a failure state and a recovery or revision.

What you’ll produce

Module 1 artefact: Define which routes need indexable HTML and which require a signed-in application.
Module 2 artefact: Build route-specific titles, canonical URLs and article content that remain present before JavaScript runs.
Module 3 artefact: Generate distinct social images and metadata and test the actual anonymous response for several routes.
Module 4 artefact: Check direct links, hydration, empty data, keyboard journeys and access failures on a staged deployment.
A concise project brief, source and rights record, evidence log and handover with known limitations.

What good work looks like

Separate public pages from private state: 20 marks for a correct artefact, justified decisions and repeatable evidence.
Render meaningful public HTML: 20 marks for a correct artefact, justified decisions and repeatable evidence.
Make each share preview useful: 20 marks for a correct artefact, justified decisions and repeatable evidence.
Release a navigable application: 20 marks for a correct artefact, justified decisions and repeatable evidence.
Integration and handover: 20 marks for a coherent project, source acknowledgement, appropriate access and a clear explanation of remaining limits. Pass requires at least 70/100 and correction of any privacy, access or destructive-operation defect before completion.

Resources for your learning

A worked example and a deliberately broken fixture for separate public pages from private state.
A worked example and a deliberately broken fixture for render meaningful public html.
A worked example and a deliberately broken fixture for make each share preview useful.
A worked example and a deliberately broken fixture for release a navigable application.
A react experiences with static public html and reliable sharing workbook with evidence prompts and the capstone marking sheet.
A transcript, caption file and text-first lesson version for every recording.
A downloadable source-and-rights checklist and a sample completed project handover.

A course you can access

Provide edited captions, transcripts and a text-first route through every lesson.
Use keyboard-operable exercises, visible focus, legible contrast and no essential autoplay or motion.
Supply downloadable instructions and low-bandwidth alternatives; avoid timed assessment as a default.
Offer equivalent written evidence where live attendance or spoken presentation is a barrier and document support before enrolment.

FINISH WITH SOMETHING USEFUL

How you’ll complete the course

Submit all four module artefacts and respond to assessment feedback.
Complete the capstone at 70/100 or above with no unresolved access, privacy or destructive-operation defect.
Explain a meaningful failure case and the limits of the result in the evidence log.
Completion records describe assessed participation; I am not claiming external accreditation.

Completion will describe the work you have done. No external accreditation or professional qualification is claimed.

BEFORE I OPEN ENROLMENT

What I still need to finish

I’ll turn this plan into a delivered course once the teaching material and the learning service are ready.

Produce and editorially review the four lessons, worked examples, broken fixtures and marking guidance for react experiences with static public html and reliable sharing.
Build and test the course-specific workbook and capstone reference project using synthetic or permitted material.
Pilot the complete learner journey, including mobile, keyboard, captions, assessment feedback and recovery from interrupted access.
Approve the actual price, tax treatment, refund terms, access period, support boundaries and any cohort dates before accepting payment.
Implement and test authentication, server-side paid entitlements, webhook reconciliation, private asset access and tenant isolation before unlocking paid lessons.
Confirm tutor availability, feedback turnaround, moderation responsibilities and capacity before advertising tutor-led support.
Review source licences, sample rights and current official technical guidance before recording or publishing the material.

The ideas behind the course

My published articles are background reading for this plan. The full lessons, activities and assessment material still need producing.

EXPLORE THE ACADEMY

See how the learning space feels.

Try the fictional learner demo →