-
Notifications
You must be signed in to change notification settings - Fork 173
templates: separate record detail content #2954
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
This PR was automatically marked as stale. |
| <div class="ui container"> | ||
| <div class="ui relaxed grid mt-5"> | ||
| <div class="two column row top-padded"> | ||
| {% include "invenio_app_rdm/records/record_content.html" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the idea to make record_content.html overridable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say embeddable instead of overridable. If you take a look at #2953, having the record content be separate would facilitate a tabbed interface for the landing page. There is probably more discussion needed on the specific interface....but I think this template change makes the templates more flexible in general.
|
This PR was automatically marked as stale. |
|
This PR was automatically marked as stale. |
❤️ Thank you for your contribution!
Description
This PR splits the record detail template into the page template and a new template for the actual record content. This makes the template cleaner and more reusable, and is in preparation for being able to enhance the landing page in #2953
This PR does not make any changes to the templates, just splits the content into two.
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:
Frontend
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that: