Skip to content
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

Make the infobox expandable #102 #467

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Make the infobox expandable #102 #467

wants to merge 1 commit into from

Conversation

Abbe98
Copy link
Member

@Abbe98 Abbe98 commented Dec 8, 2024

Description

Display official blog URL and official jobs URL (#287) as a start.

Issue Reference

Fixes #102 #287

PR Details

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update
  • Code refactor

Checklist

Please ensure the following before submitting the PR:

  • I have tested the changes locally, and they work as expected.
  • The code follows the project's coding standards and conventions.

Screenshots (applicable to user interface changes)

Screencast from 2024-12-08 17-06-18.webm
Screencast from 2024-12-08 17-05-58.webm

@Abbe98 Abbe98 requested a review from Ainali December 8, 2024 16:13
Display official blog URL and official jobs URL (#287) as a start.
<hr>
<ul>
<li>Official jobs page: <span class="text-grey" id="additional-link-jobs">[missing data]</span></li>
<li>Official blog: <span class="text-grey" id="additional-link-blog">[missing data]</span></li>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: omit the [missing data] from these 2. Because it is not very common those links and if there is something “missing” even if there is none does not come across very well in my opinion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree. This is an invitation to help add the data. And these are just the first few things we add, just with all open issues there may be 3-4 more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a huge fan of this pattern either as a user can see the expand button just to get disappointed. However, people looking to contribute might not even know what they can contribute if we do not indicate this, this is for example a known problem with the call to action buttons. For example if you go to an agency missing an email address there is no way to know from that page that adding an email address will add a button.

For the future I imagine these "missing data" sections(both here and in the existing dialog) to be either accompanied with or replaced by "add"/"+" buttons which would open a modal and let people authenticate with OAuth and paste a new link.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I get the idea, but if there is no data to add. Then there is missing data everywhere, but in reality there is none.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, that's indeed an issue and possibly rather common is certain regions. We should probably get rid of all our [missing data] section and add a new general call-to-action about adding new data, such a call-to-action could then go on to tell the potential contributor of all the data we can display. That would also solve the issues with the buttons without us introducing some new UI-pattern.

Regarding this PR; I will change it so that no button is rendered if there is no data in the expandable section.

@Ainali
Copy link
Member

Ainali commented Dec 8, 2024

I was trying to build locally but got this error:

Building project with 47 views.
Received bad(HTTP: 502 Bad Gateway) response from SPARQL endpoint:
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>

Error: Failed to render page at site/statistics/index.html Error: template: statistics.html:37:35: executing "main" at <query "organization-optional.rq" .qid.String>: error calling query: Received bad response from SPARQL endpoint

@Abbe98
Copy link
Member Author

Abbe98 commented Dec 8, 2024

I was trying to build locally but got this error:

Building project with 47 views.
Received bad(HTTP: 502 Bad Gateway) response from SPARQL endpoint:
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>

Error: Failed to render page at site/statistics/index.html Error: template: statistics.html:37:35: executing "main" at <query "organization-optional.rq" .qid.String>: error calling query: Received bad response from SPARQL endpoint

Looks like WDQS is having a bad day.

Copy link
Member

@Ainali Ainali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worked on the second try!

(Not a blocker, but if in the future the expanded view gets long, we might want to have an option to collapse it again. But let's merge this for now.)

@Abbe98 Abbe98 marked this pull request as draft December 8, 2024 18:57
@Abbe98
Copy link
Member Author

Abbe98 commented Dec 8, 2024

Converted to draft until I have changed it so that the "expand" button only renders when there is additional data to be displayed. I will also create an issue about a generic "[missing data]" (or something positive? "add information"?) replacement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add an "expanded info" button
3 participants