Add some blocks to course_about.html - #96
Conversation
There was a problem hiding this comment.
Why do we need an empty block right before the next block? Can we not include the content we want to add to course_info_before_header to the top of the header block?
There was a problem hiding this comment.
We will have to be careful with the naming. The main.html template (which this template inherits from)also (indirectly) contains a
element. It is currently not wrapped in a named block, but it could be in the future and would clash with theheaderblock from this template. We should name this one something likecourse_about_header`.
There was a problem hiding this comment.
Maybe it would make sense to prefix all blocks introduced by a template by the template name.
There was a problem hiding this comment.
I renamed blocks to use course_about prefix.
|
This looks good @clemente, but we still need the template block overrides commit. The commit has been merged to edx/edx-platform/master, but not into opencraft-release/ginkgo.1-pearson. It might make sense to do it in a separate PR though. This is good to go after you squash the commits. 👍
|
|
We will also need to open an upstream PR with the same changes (unless the structure of the course_about.html page has changed significantly on master as compared to ginkgo). |
5798bbf to
5913516
Compare
|
Now that the new template inheritance was merged (https://github.com/edx/edx-platform/pull/16856) we can redefine specific blocks.
This adds some block names to existing code so that themes can redefine this blocks easily (without having to redefine the rest of the page).
This handles just course_about.html
JIRA tickets: None
Discussions: None
Dependencies: None
Screenshots: None
Sandbox URL: None
Merge deadline: None
Testing instructions:
lms/templates/course_about.htmlwhich redefines one of the blocks, e.g.<%block name="course_about_header">Reviewers
Author concerns: None
Settings: None