Refonte Course Listing Requirements in 2026

Last updated: Mon, Aug 17, 2026

Why listing requirements matter in 2026

Course marketplaces have matured, and buyer expectations are higher than ever. In 2026, a course listing must perform two jobs at once. It needs to earn human trust quickly, and it must also be machine readable so platforms, search engines, and recommendation systems can rank and route it correctly. Clear, consistent requirements help you do both.

When your listing follows a predictable structure, learners compare options faster. They can scan your title, outcomes, syllabus, and instructor credentials without friction. That transparency reduces purchase anxiety and improves conversion. Refonte Learning enforces these standards to protect learners and to reward providers who build high quality, outcome oriented training.

The same fields that help humans also help discovery systems. Structured outcomes, explicit prerequisites, and accurate tags tell ranking models where your course belongs. Precision is especially important for AI assisted search and LLM powered copilots that summarize and compare offerings. Ambiguous or missing data makes your course invisible in these flows. A complete listing becomes part of a reliable knowledge graph that points qualified buyers to you.

Listing requirements also de risk ongoing operations. They prevent downstream support tickets, refund churn, and compliance issues. Making expectations explicit around accessibility, intellectual property, and assessment quality helps you ship confidently, then scale. You invest once in a robust listing and keep benefiting as your course is recommended to the right learners across catalog pages, email campaigns, and enterprise portals.

Finally, requirements codify what Refonte will review. Meeting them makes the editorial process faster and clearer. Our reviewers align with the same rubric you see here. If something is out of scope, unlicensed, or poorly specified, you will know before you upload. For a go to market view that complements this deep dive on listing requirements, see the comprehensive pillar on how to sell your course on Refonte Learning.

The rest of this guide explains exactly what we expect in each section of a listing, the measurable standards we apply during review, and the pitfalls that slow approvals. Use it as your working checklist as you build or refresh your catalog in 2026.

Instructor and provider identity standards

Learners buy the instructor as much as the syllabus. Your public profile must make your expertise legible, verifiable, and relevant to the promises in your listing. We look for clarity, not celebrity. The must haves below are required for an instructor or organization level profile to pass review.

Real name or operating name that matches your legal documents and payment information. Avoid pseudonyms in professional listings.
Headshot or brand mark with a clean background, high resolution, and good lighting. For individuals, face centered, eyes visible, no heavy filters.
Expertise summary in 80 to 120 words. Focus on domain credibility that maps to the course. Mention shipped projects, research, or production systems. Avoid vague claims like thought leader or guru.
Role and affiliation. Title and current company if allowed by your employer, or independent consultant status. If you teach with a partner organization, disclose co branding clearly.
Skills and tools. Name the exact frameworks, clouds, stacks, or libraries you work with. Example: Kubernetes, Terraform, AWS, dbt, Snowflake, PyTorch.
Evidence links. One to three links to a GitHub profile, packages you maintain, whitepapers, talks, or documented production work. Avoid link dumps.

Refonte will also complete identity, payment, and tax onboarding privately. Keep your documents current and consistent with your public identity to prevent payout delays. If you are a team, designate a single responsible owner for communications and updates.

We strongly recommend stating topical boundaries. If your deep work is in MLOps, do not over extend into full stack web or exam cram formats just to widen appeal. Learners benefit when instructors stay inside their credibility zone.

New to the platform or shifting to a teaching role this year. Review the application steps and expectations, then become an instructor on Refonte Learning. The onboarding page explains timelines, required documents, and how to position your first listing for a quick approval.

Course metadata rules that drive trust and search

The single best predictor of a fast approval is complete, precise metadata. Think of metadata as your course’s contract with the learner and with search systems. Fill every required field thoughtfully and you will avoid the most common rejection reasons.

Required fields and standards:

Title: up to 60 characters, specific and scannable. Lead with the technology or skill, then the level or use case. Example: Production MLOps with Kubernetes for Mid level Teams.
Subtitle: up to 120 characters, expanding the who and the outcome. Make it a plain language promise, not a list of keywords.
Long description: 300 to 1,200 words. Use short paragraphs. Include context, outcomes, prerequisites, syllabus summary, and delivery format.
Learning outcomes: 4 to 8 bullet points, each starting with an action verb. Link every outcome to at least one assessment and one module.
Audience: who should take this course and who should not. Be candid to prevent mismatched enrollments.
Prerequisites: 2 to 6 bullets. Name the baseline skills and versions learners need. Example: Python 3.10, basic Docker, Git fundamentals.
Level: beginner, intermediate, or advanced. Choose one.
Duration: video hours and estimated total effort in hours. Example: 6 hours video, 12 to 16 hours total.
Delivery mode: self paced, cohort, or hybrid. If cohort, specify start cadence and live touchpoints.
Language and subtitles: specify original audio language and available captions. Non English audio must include English captions if your target audience is global.
Software and environment: name required tools and versions learners must install, plus any platform accounts needed for labs.
Tags: 5 to 10 tags aligned to real search intent. Choose nouns learners actually type, not your internal jargon.

For machine readability and rich discovery, structure your listing so it can map cleanly to the official schema.org Course specification. Clear fields for name, description, provider, instructor, start date, duration, and course mode help search engines and learning portals present your offer with consistent, high quality previews.

Finally, align your promises with your assets. If the title says with Kubernetes, show Kubernetes in labs and projects. If you include vendor names or certifications in the title, ensure you have rights to reference those marks and that your content truly prepares learners for that scope.

Curriculum and syllabus structure that passes review

A well designed curriculum is the backbone of a credible listing. The Refonte review team looks for a logical progression, time boxed modules, and repeated opportunities to verify learning. Your syllabus should function as both a plan and a proof of alignment to outcomes.

Minimum structure guidelines:

5 to 12 modules. Shorter courses are fine if tightly scoped, but avoid a single monolith.
3 to 8 lessons per module. Keep individual video lessons to 5 to 12 minutes to sustain attention. Longer live sessions can be recorded and segmented.
An assessment touchpoint every 20 to 30 minutes of video or equivalent reading time. Use quizzes, short coding tasks, or reflection prompts.
At least one real project. Scope it so a motivated learner can finish in 3 to 6 hours. Provide a rubric.
A capstone that integrates multiple skills wherever appropriate.

Naming conventions matter. Module and lesson titles should be action oriented and specific. Replace generic labels like Introduction with specific statements like Initialize a Git repository for the model API. This scanning clarity boosts conversions and reduces refunds.

Outcome mapping example

Outcome: Containerize and deploy a model backed API on Kubernetes.
Linked modules: Docker fundamentals for ML, Kubernetes Deployments and Services, Observability with Prometheus.
Assessments: Dockerfile review quiz, YAML validation task, deployment troubleshooting scenario.
Project: Package a FastAPI model, push to registry, and deploy to a cluster with monitoring.

Include time estimates for modules and the project. Learners plan around these. We also recommend a quick wins path for busy professionals, such as an accelerated route through the first 90 minutes that lands a tangible result.

If your course targets a certification, put the blueprint mapping in your listing or as a downloadable asset. Name the exam code, the covered domains, and a percentage coverage estimate. Do not over claim if you do not cover the full blueprint.

Media quality, file formats, and asset specs

Production quality signals respect for the learner. You do not need a studio, but you do need clarity. Poor audio is the top reason we ask for edits. Use the following baseline specs to pass review and to give your learners a smooth experience.

Video standards:

Resolution: 1080p recommended. 720p is acceptable for talking head segments if text is not shown. Avoid 4K exports that bloat size without visible benefit for screen recordings.
Frame rate: 24 to 60 fps. Keep it stable across the course.
Codec and container: H.264 in MP4 files. Avoid variable frame rate exports that create sync drift with captions.
Bitrate: target 8 to 12 Mbps for 1080p screen capture. Use constant bitrate or two pass encoding for consistency.

Audio standards:

Microphone: external dynamic or condenser mic. Avoid built in laptop mics.
Sample rate: 48 kHz. Bitrate: 128 to 192 kbps AAC in the final muxed file.
Voice level: average around -16 LUFS for mono. Keep noise floor and room echo low with basic treatment.

On screen readability:

Slides: 16:9 aspect, minimum 24 pt font, high contrast color pairs. Avoid using red and green as the only distinguishing colors.
IDE or terminal: scale UI to 150 percent or more. Use a monospaced font at least 16 pt in the capture.

Captions and transcripts:

Provide SRT or WebVTT caption files for every video lesson. Aim for 99 percent accuracy.
Include speaker identification in multi voice segments and mark non speech audio if it impacts understanding.
Upload a transcript file for downloadable reference. Time stamps are helpful but not required.

Visual assets:

Course cover: 1920 x 1080 pixels, clean composition, minimal text, and a single focal concept.
Thumbnail variant: 1280 x 720 pixels. Ensure the title text remains legible at small sizes if used.
Alt text: add descriptive alt text for covers and diagrams. Describe the what and the why, not just the colors and shapes.

File organization and naming:

Use short, descriptive names in ASCII only. Example: m03_k8s_deployments_lesson02.mp4.
Avoid spaces and special characters that break links or scripts.

These standards keep your assets portable and resilient. They also make it easier for our systems and reviewers to validate your uploads without manual interventions.

Assessments, labs, and real projects

Assessment quality separates entertainment from education. Refonte looks for alignment, feedback, and authenticity. By the time a learner sees a completion badge, they should have demonstrated the outcomes your listing promised.

Quizzes and exams:

Blueprint. Associate each question with a learning outcome and a module. Maintain a coverage table to avoid gaps.
Variety. Mix multiple choice, short answer, and scenario based prompts. Avoid gotcha trivia and trick wording.
Clarity. State the task plainly. Provide distractors that reflect real mistakes, not nonsense options.
Feedback. Explain why an answer is correct or incorrect. Link back to the relevant lesson by title.
Security. Randomize question order and answer options. Avoid reusing exact questions across public channels.

Labs and notebooks:

Reproducibility. Provide environment setup steps, pinned versions, and a quick start script. Note platform differences where relevant.
Data ethics. Use public or synthetic datasets. Never include personal data or secrets. If redacting, confirm you removed metadata and derived identifiers.
Safety. Do not instruct learners to disable security controls or run untrusted scripts with elevated privileges.
Evaluation. Include unit tests for code tasks where possible to provide instant, objective feedback.

Projects and capstones:

Realistic scope. Design a project that can be finished in a weekend by a motivated learner. Prefer integrating skills across the course.
Rubric. Publish a clear 3 to 5 level rubric with criteria tied to the outcomes.
Transfer. Encourage learners to adapt the project to their context. Offer optional extensions for ambition.

Make support discoverable. Tell learners how to get help during assessments. Set expectations for response times and what you can and cannot debug for them. Honest boundaries prevent frustration.

Accessibility requirements and inclusive design

Accessibility is not a nice to have. It is required. Refonte aligns its reviews with common accessibility expectations so everyone can participate and so enterprise buyers can adopt your course without extra audits.

Core requirements:

Captions. Provide accurate captions for all video content. Use sentence case and correct punctuation.
Transcripts. Provide a downloadable transcript for each video lesson.
Contrast. Maintain at least a 4.5:1 contrast ratio for body text and essential UI in your slides and on screen demos.
Color alone. Never use color as the only way to convey information. Add labels, patterns, or icons.
Keyboard access. Demonstrate that interactive code notebooks, lab UIs, and downloadable templates can be navigated by keyboard.
Flashing content. Avoid content that flashes more than three times per second.
Headings and landmarks. Structure written materials with clear headings and lists so screen readers can navigate.
Alt text. Provide descriptive alt text for covers, diagrams, and complex visuals. If a diagram is intricate, include a text explanation in your notes.
Language. Avoid idioms, sarcasm, or humor that depends on cultural context for critical instructions. Keep instructions simple and direct.

We recommend a short accessibility review flow before you submit. Read your captions out loud while the video plays. Run a color contrast checker on your slide deck. Test keyboard navigation in your lab. These quick checks remove the most common barriers we see in review.

If you retrofit an older course, treat accessibility as a versioned update. Call out the improvements in your changelog and in a release note in your course description. Learners appreciate the upgrade, and enterprise clients often require this information.

Policy, IP, and claims compliance

Your listing is a public promise. Refonte protects learners by enforcing clear policy boundaries and intellectual property requirements. The rules are simple. Own what you teach, do not mislead, and do not put learners at risk.

Content ownership and licensing:

Use only assets you created or that you have the right to use. Keep license documents for third party media.
Attribute open source code or images according to their license terms. Prefer permissive licenses like MIT or Apache 2.0 when you embed examples.
Avoid fair use gambles. If a piece of content is essential, secure permission.

Trademarks and brands:

You may reference vendor names and product names for factual purposes. Use the correct spelling and capitalization.
Do not imply endorsement, partnership, or certification status unless you have formal approval.
If your course prepares learners for a particular vendor exam, say prepares for, not is the official.

Claims and scope:

Keep outcomes realistic and specific. Replace get a job in 30 days with build and deploy a production ready API with monitoring.
Disclose version scope. State tool or framework versions used and tested in the course.
Safety and legality. Do not teach techniques that violate terms of service, licensing, or laws. Red team or security content must emphasize responsible use.

Privacy and data:

Never include personal data, secrets, or credentials in your course materials.
If you collect learner data for projects, route it through platform approved forms and disclosures.

Refonte Learning reviews listings against these policies. If we flag something, we will ask for a revision. Keeping a simple audit trail of your assets, attributions, and permissions helps you resolve questions quickly.

Pricing, free listing, and promotions on Refonte

Price communicates value, but it also sets expectations. Start with the learner’s return on investment and the market’s willingness to pay for your topic and level. Value based pricing performs better than race to the bottom discounts, especially for professional and enterprise audiences.

We recommend you model price against three anchors. First, the depth and exclusivity of your content. Second, the measurable outcome you promise, such as a deployable artifact, a certification pass, or a migration plan. Third, the effort required to produce and maintain your course on a current toolchain.

To translate this into a coherent model for Refonte Learning, read the Refonte course pricing guide. It covers catalog wide pricing bands, promotions, and how to think about coupons and seasonal campaigns. If you are evaluating a lead generation strategy or want to seed an audience without a paywall, study the mechanics in free course listing explained on Refonte. Free can work when it has a clear path to paid coaching, cohorts, or advanced modules.

Promotions should not change your listing promises. If you run a discount, keep your metadata and assets consistent. Do not remove labs or projects for sale events. If you add a bonus to drive urgency, put an expiry date in the description and in your changelog.

Finally, bundle intentionally. Related modules can be combined into a program if they share outcomes and audiences. Make sure the bundle listing has its own outcomes and a clear path through the content, not just a playlist of parts.

Live sessions and cohorts: additional requirements

Cohort courses and live touchpoints can accelerate outcomes and improve completion. They also add operational complexity. If your listing includes live sessions, you must publish additional details and meet higher technical standards so learners know what to expect.

Required disclosures for live or hybrid formats:

Session cadence. Weekly, biweekly, or intensive. State the number of sessions and typical length.
Time zones. Publish primary time zone and note alternatives if you repeat sessions for global cohorts.
Recording policy. Declare whether sessions are recorded, how quickly recordings are posted, and how long they remain available.
Participation. Clarify whether attendance is required for a certificate or graded component, and how you accommodate schedule conflicts.

Technical baselines:

Stable internet. At least 10 Mbps upstream measured from your teaching location. Test at the same time of day as your sessions.
Audio chain. External mic, pop filter, and headphones to avoid echo. Mute discipline and backup audio plan.
Lighting and framing. Camera at eye level, soft front light, quiet background, readable name tag.
Screen share. Clean desktop, do not expose private folders, hide notifications, magnify text.

For the full checklist and gear recommendations, read the dedicated guide on live session technical requirements for Refonte. These expectations protect the learner experience, and they reduce no show rates and refunds triggered by avoidable friction like poor audio or confusing calendars.

Cohort operations add copy to your listing too. Include a welcome timeline, onboarding steps, and community norms. Tell learners how you handle breakout groups, office hours, and asynchronous discussion. These small details increase trust and reduce uncertainty.

Pre-publish checklist and review workflow

Your best path to a first pass approval is a deliberate pre flight check. Think like a reviewer and simulate the learner journey end to end before you hit submit. You can accelerate this work by following the platform specific instructions in the Refonte course provider getting started guide.

Pre publish checklist:

Metadata completeness. All required fields filled, outcomes measurable, versions stated, tags de duplicated.
Syllabus coherence. Module titles action oriented, time estimates realistic, assessments mapped to outcomes.
Media quality. Sample three random lessons at full screen and mobile views. Confirm audio clarity and caption sync.
Accessibility. Run a quick audit on captions, color contrast, alt text, and keyboard navigation in labs.
IP compliance. Verify all third party assets and attributions. Replace anything uncertain.
Assessment validity. Pilot quizzes with a small group. Validate feedback text and links back to lessons.
Live session readiness. Template invites prepared, time zones checked, and backup plan in place.

Submission and review expectations:

Initial screening confirms policy and metadata completeness.
Editorial review samples your media and checks alignment between outcomes, syllabus, and assessments.
Technical review validates file integrity, caption formats, and basic accessibility signals.
You receive a pass, a revision request with actionable notes, or a decline with reasons.

If you receive a revision request, focus on the blocking issues first. Resubmit with a short changelog so the reviewer can verify quickly. Use semantic versioning in your listing, for example v1.0 published, v1.1 captions fixed, v1.2 lab rubric clarified. That habit pays off when you maintain your catalog over time.

Post-launch analytics, iteration, and maintenance

Approval is the start, not the finish. The best performing listings are maintained like products. They are updated when tools change, and they are improved when analytics show confusion or drop off. Refonte Learning provides metrics to support this loop. Build a simple operating cadence around them.

Metrics to watch weekly:

Discovery to view rate. How many catalog impressions become listing views. Poor thumbnails or titles can drag this down.
View to enroll rate. Tightly correlated with clarity in your outcomes, prerequisites, and syllabus.
Refund rate. Investigate spikes at the module level. They often point to a mismatch between promises and delivery.
Completion rate. Look for module drop offs and improve pacing, break long lessons, or add quick checks.
Assessment performance. High miss rates on specific questions often indicate ambiguity in teaching, not learner failure.

Iteration tactics:

Thumbnail and title refresh. Small copy tweaks can move conversion without changing your core content.
Add a quick wins path. Early victories keep learners engaged.
Supplement weak spots. Add a short lab or an annotated solution video where confusion clusters.
Update to current versions. Framework and cloud releases move fast. Note the update in your listing so buyers see your course is current.

Maintenance cadence:

Light refresh quarterly. Fix minor bugs, add clarifications, and tune quizzes.
Major refresh annually or when a breaking change lands in your stack. Publish a changelog and email enrolled learners.
Sunset and succession. If a course is obsolete, de list it gracefully and point learners to a maintained successor.

You will also grow your practice. As you expand, you can productize cohorts, create advanced follow ons, or bundle modules into a specialization. Keep the listing requirements close at hand as your catalog scales. They are the contract that keeps quality high and growth sustainable.

Refonte Learning is built by practitioners who teach. When you align your listing with the standards above, you make it easier for us to recognize and feature your work. To join the platform or formalize your existing practice, you can become an instructor on Refonte Learning in a few steps. We look forward to reviewing your next great course.