-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
the newsfeed url should point to a feed visualisation, not the url of the news itself #477
Comments
I agree with this. For now, the link to the feed from the main website is not easy to find. I think it would be useful to add the "All news" link to the navigation bar (inside the "Project" menu, for example). For the details page for each entry, I'm thinking about the same design as in the feed form. It will show either when clicking on the link on the news bar for qgis.org or from the feed list on feed.qgis.org: We are working on the separated Hub, Planet, from the Plugins with a branding update to match the current QGIS.org. Perhaps we should also add the new links once migrated. What do you think? |
we also have our venerable blog.qgis.org hosted on WordPress that partially overlaps newsfeed. I would vote in favor of using Hugo native blogging capabilities, only once the CI will be able to publish on merge. This would imply a content migration too. |
Hi @haubourg Please find the proposed fixes for this issue at #489, qgis/qgis-feed#96, and qgis/qgis-uni-navigation#20. Regards, |
URL
No response
On what type of device(s) did you see this bug?
No response
On which operating system(s) are you seeing the problem?
No response
Other OS
No response
On which browser(s) are you seeing the problem?
No response
Other Browser
No response
Summary
The link pointed in this image will use the url of the newsfeed itself.
This will not let user read the whole feed entry and redirect to a strange url. The QGIS for peace URL redirects to the code of conduct page for instance.
my suggestion would be :
@timlinux @Xpirix @anitagraser any opinion here ?
The text was updated successfully, but these errors were encountered: