Skip to content
SYNTRA
FAQ

Frequently asked questions

Once enrollment is set up through your own backend or checkout integration, each course page links directly to its curriculum. On this template, the course detail page shows the full curriculum structure so you know exactly what's included before connecting a real access flow.

Self-paced courses can be worked through on your own schedule. Cohort-based courses combine self-paced material with scheduled live sessions alongside a group of peers. Live Sessions courses are built primarily around scheduled sessions with an instructor.

Foundation courses assume no prior background in the topic. Intermediate courses assume you've completed a foundation course or have equivalent experience. Advanced courses assume real working experience and focus on judgment in ambiguous situations, not basic technique.

No. Paths are recommended sequences, not requirements. Many people complete an individual course without the surrounding path. The path exists for people who want a fuller, deliberately sequenced body of knowledge in a specific area.

Instructors on SYNTRA continue practicing in their field, which shapes how courses are updated over time. This template doesn't include a live messaging system between students and instructors — that would need to be built on top of it.

The course detail page includes a full curriculum breakdown, and the homepage's learning experience preview demonstrates a chapter-based progress interface. Persisting real completion data across sessions requires connecting your own backend or database — this template intentionally ships without one.

This template doesn't include a support ticketing system. The Contact page provides a working inquiry form you can wire up to your own support workflow or inbox.

Yes — SYNTRA is a frontend template built specifically to be adapted. Content lives in a small set of structured data files, so replacing courses, instructors, learning paths, and journal articles doesn't require touching page layout code. See the project's setup documentation for details.