You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a description of what it will take in order to accomplish #2125.
For more depth, see p6rkRX-HY-p2.
In summary, we need to modify the frontend displays in Sensei which use full-page templates (e.g. the /courses/<course-slug> page which uses the single-course.php template). These full-page templates do not work properly in all themes.
Instead, we will use a similar approach to what WooCommerce adopted by rendering the content of these pages within the content area provided by the theme (e.g. using the the_content filter). This way, the theme will provide the proper layout, ensuring that the site looks good, and we will be simply adding our content within that layout. Note that we will only do this for themes that do not explicitly declare support for Sensei.
For full support, we will need to implement this rendering mechanism for all of the pages listed below. These may be done in multiple PR's.
Here is the initial PR that provides the architecture to build upon, and completes the Course Page. The Module Page is a work-in-progress and should have a PR soon as well. The remaining pages can be implemented in parallel.
This issue is a description of what it will take in order to accomplish #2125.
For more depth, see p6rkRX-HY-p2.
In summary, we need to modify the frontend displays in Sensei which use full-page templates (e.g. the
/courses/<course-slug>
page which uses thesingle-course.php
template). These full-page templates do not work properly in all themes.Instead, we will use a similar approach to what WooCommerce adopted by rendering the content of these pages within the content area provided by the theme (e.g. using the
the_content
filter). This way, the theme will provide the proper layout, ensuring that the site looks good, and we will be simply adding our content within that layout. Note that we will only do this for themes that do not explicitly declare support for Sensei.For full support, we will need to implement this rendering mechanism for all of the pages listed below. These may be done in multiple PR's.
Here is the initial PR that provides the architecture to build upon, and completes the Course Page. The Module Page is a work-in-progress and should have a PR soon as well. The remaining pages can be implemented in parallel.
/course/<course-slug>
single-course.php
/lesson/<lesson-slug>
single-lesson.php
/quiz/<quiz-slug>
single-quiz.php
/messages/<message-slug>
single-message.php
/courses
/<course-archive-page-slug>
(from settings)/course-category/<course-category-slug>
archive-course.php
/messages
archive-message.php
/lesson-tag/<lesson-tag-slug>
archive-lesson.php
/learner/<username>
learner-profile.php
/course/<course-slug>/results
course-results.php
/author/<username>
teacher-archive.php
modules/<module-slug>/?course_id=<course-id>
taxonomy-module.php
includes/class-sensei-templates.php
, this one is handled inincludes/class-sensei-modules.php
The text was updated successfully, but these errors were encountered: