Explain the intended learner, prerequisites, format and confirmed timetable. Distinguish an information request from actual enrollment. A weekend workshop page can state its audience, supplied materials and contact process without claiming a certificate that is not offered. Do not publish outdated schedules or promise educational or employment outcomes without evidence.
Write programme pages around learner decisions
Prospective learners need to understand who a programme is for, what it covers and how it is delivered. Begin with those questions instead of a general claim that the organisation transforms lives. State any prerequisites in ordinary language and distinguish intended learning goals from guaranteed outcomes. A website should not promise employment, certification or examination success unless the business has a legitimate, verified basis for the exact statement.
Give each programme a useful structure: audience, subject coverage, format, confirmed schedule and enquiry route. If two courses differ only in the date of the next group, decide whether separate pages are genuinely helpful. A single maintained programme page with current schedule information may be clearer than a collection of expired pages with conflicting details.
Include the information a learner needs before contacting you, but avoid collecting sensitive background data merely to ask a question. The application stage and any later enrolment process may require different information. Define that distinction before deciding the form fields.
Keep schedules and people information trustworthy
Dates are particularly easy to leave behind after launch. Assign someone to update a programme when enrolment closes, a start date changes or a class is cancelled. An old “applications open” notice can create disappointment even when the rest of the page is well written. Show an uncertain schedule as something to confirm, not as an invented date chosen to complete the design.
Publish teacher names, biographies, photographs and qualifications only with permission and accurate wording. If teaching assignments can change, agree how the site reflects that. Do not borrow prestigious organisation names in a way that implies a partnership or endorsement the provider does not have.
For a practical example, a workshop page may state the subject, delivery format and intended level, then invite an enquiry about the next available date. That is more honest than displaying a countdown to a session that has not been scheduled. When a date becomes confirmed, update the same source used by the page and any supporting listings.
Separate a presentation site from a learning platform
A course introduction website can explain programmes and collect interest. A learning platform adds different capabilities: accounts, lesson access, progress, assignments, live sessions or payments. Those features require their own scope and operating decisions. A blog or article section does not become a student portal simply because educational content is published there.
If an external platform is used, identify which part of the journey happens there and who owns the account. Test the transition from the public programme page. The visitor should understand whether they are making an enquiry, applying for a place or completing a paid enrolment. Labels and confirmation messages should match the actual step.
Review a programme on a phone, including dates, long course titles and form errors. A learner should be able to identify the level and next action without downloading a large brochure first. Keep the brochure as a supporting resource if useful, with a matching version date. Clear, maintained programme information is the main value of the site and remains essential regardless of how sophisticated a future learning system becomes.
Review one programme as a learner would. Ask whether its title, level, format and schedule answer the questions a new applicant actually has. Then follow the enquiry button and check the confirmation. The learner should know whether they asked for information, submitted an application or secured a confirmed place.
Try an expired-date scenario before launch. Decide what the page will show when the advertised intake ends and who will make the change. Keeping an old date visible without explanation can damage an otherwise clear programme presentation. A maintained next-intake message is preferable to an invented schedule used to fill a design block.
Keep programme documents consistent with the page. If a brochure includes a different tutor, format or deadline, determine which source is current and update both intentionally. A content owner should be able to find the editable material and the public files during handover. This makes routine programme changes manageable and reduces the risk that several apparently official versions remain online with incompatible information.
Practical checklist
- Describe learning scope
- Verify dates and availability
- Explain how enquiries proceed
A concrete example: A weekend workshop page can state its audience, supplied materials and contact process without claiming a certificate that is not offered.
A boundary to keep clear: Do not publish outdated schedules or promise educational or employment outcomes without evidence.
Your next step
Tell Orvunweb about your project
