-
Notifications
You must be signed in to change notification settings - Fork 594
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
fix: links are direct to asset #2593
base: main
Are you sure you want to change the base?
Conversation
{% for asset in provided_assets %} | ||
<li><b>{{ asset.label }}</b>: <a href="{{ asset.user_view_url }}">View asset</a>.</li> | ||
{% endfor %} | ||
{% for asset in provided_assets %} |
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.
We're effectively displaying all the same information here now that was previously available in the users:view_provided_assets
view.
Should we just replicate the template logic from
pythondotorg/templates/users/sponsorship_assets_view.html
Lines 21 to 32 in ccbc9e4
{% for asset in provided_assets %} | |
<p><b>{{ asset.sponsor_benefit }}</b> benefit provides you with {{ asset.label }}:</p> | |
{% if asset.polymorphic_ctype.name == "Provided Text" %} | |
<pre>{{ asset.value|urlize }}</pre> | |
{% elif asset.polymorphic_ctype.name == "Provided File" %} | |
<a href="{{ asset.value.url }}">View File</a> | |
{% else %} | |
{{ asset.value }} | |
{% endif %} | |
<small>{{ asset.help_text }}</small> | |
<br><br> | |
{% endfor %} |
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.
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.
It did add a chunk of text if that is a concern. Keeping the core dashboard leaner feels better imo but @loren-c may like the all-in-one approach :D
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.
@ewdurbin Suggested:
As an aside I think this could use some rearranging or love because its very squished and would look better some other way
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.
Seems one of my main issues comes from
pythondotorg/templates/users/base.html
Line 13 in 301bfe2
{% block content_attributes %}with-right-sidebar{% endblock %} |
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.
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 do like the 'all in one' approach provided we can make it more manageable and not just a giant list, and I do like Jacob's second version.
Looking at the dashboard with all the information on one page, an ability to sort the required assets by due date or by incomplete/complete would be nice, but that seems like a whole other functionality and just a nice to have.
Changes in e53f422 Although I am not 100%, my checks into the various user views for the removal of How it looks ish (latest changes I removed excessive padding as you can see in image 1 but further images have it in screenshot.. has since been fixed) |
static/sass/style.css
Outdated
transition: background-color 0.2s ease; | ||
} | ||
|
||
.btn-link { |
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.
could maybe make this more fancy
Description
Closes
funny