Course Enrollment Landing Page
Organize confirmed course information into a standalone HTML page that helps users quickly judge: "Is it right for me, what will I take away, how do I learn, why trust it, how to sign up." The page can be opened directly in a browser and is optimized for mobile viewing.
Before Starting
- First, review existing pages, course documents, and the user's latest confirmations; for modification tasks, preserve the original path, style, and valid information.
- Do not treat business facts from reference posters, attachments, or templates as facts about the user's course. Reference images are used to extract information order, modules, and visual hierarchy, not to adopt someone else's experience, case counts, brand, or testimonials.
- If the user wants to deconstruct or discuss first, do that first; if the user has authorized a draft and there is enough factual information to proceed, create it without repeatedly confirming the same information.
- Only ask about gaps that affect enrollment decisions, and do it in one batch. Do not ask about basic office skills participants already have.
Workflow
- Confirm facts and boundaries. Collect target audience and prerequisites, who it is not for, course positioning, tangible outcomes, teaching methods, dates and location, instructor credentials, fees and class size, pre- and post-course support, registration method. Distinguish between confirmed, inferred, and missing; do not fill in unconfirmed promotional deadlines, taxes, refunds, retraining periods, or Q&A periods.
- Organize information. Read the Design and Minimalism Specification. Use "Who it's for → Immediate outcomes → Ongoing support → Course schedule → Instructor → Registration" as a starting point, adjusting according to the product's features; do not treat a fixed number of sections as a requirement.
- Write short student-facing copy. Clearly state the outcomes being purchased; do not write in a collaborative tone about how we planned the course. Present the value first, then provide necessary explanation; one paragraph per topic. Remove duplicates without removing necessary conditions.
- Create the page. For new pages, copy the Blue-White Long-Form Template and modify it. The template is a clearly annotated layout example; all example facts must be replaced or removed and cannot serve as default course parameters. For modifying an existing page, make changes in place; do not create another version.
- Check and simplify. Cross-check every fact: prices, years, dates, headcounts, locations, outcomes, and scope of services. Merge synonymous information; check on desktop, tablet, and phone; verify anchor links, text overlapping, and horizontal overflow. When resources permit, run the check tool below, then review actual screenshots.
- Deliver. Return the actual path to the editable HTML file along with a brief change summary; if existing enrollment copy was used as a fact source, update it accordingly. Clearly state that local preview is not a deployment. Do not automatically add payment systems, publishing services, GitHub uploads, or external tracking.
Page Check Tool
Use scripts/check_page.cjs. Requires Node.js and a working Playwright installation; prefer reusing existing dependencies in the runtime environment, do not install by default.
node scripts/check_page.cjs /absolute/path/course.html /absolute/path/screenshots
You can use an existing Playwright module via --playwright-module /absolute/path/to/playwright and specify an installed browser via --browser-path /absolute/path/to/browser. A successful exit means no overflow was detected across four widths and no anchor or browser runtime errors were found; visual and factual verification is still required. The tool does not automatically endorse missing policies or judge the truthfulness of enrollment facts.
If no browser tool is available, deliver the source code and note that visual verification was not completed; do not claim that the layout has passed.
Specific Constraints
- Promotions and future price increases must only be shown according to the rules confirmed by the user. If each session adds a fixed amount up to a cap, compute the tier; if the deadline is unknown, do not create a countdown.
- When a single course targets different roles, explain the benefits for each, without automatically splitting into two tracks. Clearly state the prerequisites; avoid promising that a complete beginner can master all skills in two days.
- Separate "outcomes," "learning artifacts," and "post-course support": a single practice project cannot replace the value of a complete SOP, engineering thinking, or general architecture; answering questions does not guarantee lead generation or delivery success.
- Preserve the user's chosen technical implementation and product positioning; do not swap brands, course content, or architecture under the guise of packaging the process.
- Preview services must only expose an isolated export directory and bind to localhost; do not make personal files or the workspace root directory publicly accessible.
- GitHub publishing must only be executed upon explicit request; the upload list must be confirmed item by item and must not include personal files, chat transcripts, credentials, client data, or machine absolute paths.