software.hifis.net issueshttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues2020-11-10T16:28:02+01:00https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/178Feedback from Guido about the consulting page2020-11-10T16:28:02+01:00Frere, Jonathan (FWCC) - 142176Feedback from Guido about the consulting pageFrom @jucke (thanks for the feedback!)
> A few minor nitpacks/suggestions:
> - it is unclear, how many "pages" I have to click "next" trough - maybe indicating a "page 1/3, 2/3, 3/3" between the previous/next buttons might be helpful
> ...From @jucke (thanks for the feedback!)
> A few minor nitpacks/suggestions:
> - it is unclear, how many "pages" I have to click "next" trough - maybe indicating a "page 1/3, 2/3, 3/3" between the previous/next buttons might be helpful
> - after clicking next on the first page, it took me a while to recognize that I need to scroll back up to the beginning of the form to continue - the second page is also shorter than the first, so that the "next" button was for me almost at the top of the screen. Is the splitting up into multiple pages actually needed for something? Maybe it is easier to just have one (longer) form...
> - I suggest having to type the email address twice (with validation) as this is the primary way of contact and a typo there might lead to a search mission for an alternate way of contact
> - I also suggest to change the first sentence on the webpage to "HIFIS offers **free-of-charge ** consulting" as I continuously encounter an expectation from potential customers that "nothing is free in Helmholtz"
Some parts of these are likely not possible, e.g. scroll issues, but we should at least investigate these things.
* email address validation - possible w/ limesurvey relevance questions/expressions/etc?
* text changes - see feedback from consulting biweekly
* pagination - can we reduce the size of the paginator? Or increase the number of pages to make things smaller on the page?Frere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/57Revisit Mathjax 3 and Kramdown compatibility2020-09-17T16:55:18+02:00Huste, TobiasRevisit Mathjax 3 and Kramdown compatibilityCurrently, a workaround is necessary to make Mathjax 3 work together with Kramdown. See [assets/js/mathjax.js#L5-23](https://gitlab.hzdr.de/hifis/software.hifis.net/blob/325a681505b62141c184265ebe0048abc4eb5798/assets/js/mathjax.js#L5-23...Currently, a workaround is necessary to make Mathjax 3 work together with Kramdown. See [assets/js/mathjax.js#L5-23](https://gitlab.hzdr.de/hifis/software.hifis.net/blob/325a681505b62141c184265ebe0048abc4eb5798/assets/js/mathjax.js#L5-23) and the corresponding [post](https://11011110.github.io/blog/2019/10/17/mathjax-3-jekyll.html).
Revisit the current state to see, if this workaround is still required or can safely be removed.Huste, TobiasHuste, Tobias2020-02-28https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/179Feedback from consulting biweekly about the consulting page2020-08-20T15:17:14+02:00Frere, Jonathan (FWCC) - 142176Feedback from consulting biweekly about the consulting pageSee https://nubes.helmholtz-berlin.de/f/137561693
> * Rephrase “Can provide and configure infrastructure”
> * -> “Help people to help themselves”
> * Tweak this line
> * Ongoing support -> we help you to set the plan of action in place
...See https://nubes.helmholtz-berlin.de/f/137561693
> * Rephrase “Can provide and configure infrastructure”
> * -> “Help people to help themselves”
> * Tweak this line
> * Ongoing support -> we help you to set the plan of action in place
> * “Let’s start/go”Frere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/140Display URL for an event's waiting list if event is booked out2020-03-10T11:11:10+01:00Hueser, ChristianDisplay URL for an event's waiting list if event is booked outAt the moment there is no waiting list in Indico.
We use a second event as waiting list.
We need to specify and display a second URL for the waiting list event.At the moment there is no waiting list in Indico.
We use a second event as waiting list.
We need to specify and display a second URL for the waiting list event.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/54Include short version of HIFIS logo for tablet/mobile2020-03-06T14:54:57+01:00Erxleben, Fredof.erxleben@hzdr.deInclude short version of HIFIS logo for tablet/mobileUse the [short version of the logo](https://nubes.helmholtz-berlin.de/apps/files/?dir=/HIFIS/1%20HIFIS%20Gesamt/Project%20Coordination/Communication/HIFIS%20Logo/HIFIS_Logo/Short/RGB_Web_Digital&fileid=41769827)
to alleviate space constr...Use the [short version of the logo](https://nubes.helmholtz-berlin.de/apps/files/?dir=/HIFIS/1%20HIFIS%20Gesamt/Project%20Coordination/Communication/HIFIS%20Logo/HIFIS_Logo/Short/RGB_Web_Digital&fileid=41769827)
to alleviate space constraints due to overfilled header.
Cropping may be required.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/134Blog RSS feed2020-03-04T10:59:26+01:00Lars BilkeBlog RSS feedPlease add a RSS feed to the blog. Thanks!Please add a RSS feed to the blog. Thanks!Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/115Include Sub-Locations in the Organizations data.2020-01-22T17:19:29+01:00Erxleben, Fredof.erxleben@hzdr.deInclude Sub-Locations in the Organizations data.Some Helmholtz-Centers (especially the DLR) run a bunch of sub-locations which should be included in our data, so they can be easily referenced.
This would require reorganizing the `hifis_organizations.yml` and code that relies on that ...Some Helmholtz-Centers (especially the DLR) run a bunch of sub-locations which should be included in our data, so they can be easily referenced.
This would require reorganizing the `hifis_organizations.yml` and code that relies on that file.
Sub-locations can inherit some properties from their organizations to reduce redundancy.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/103Project Management via a Group2020-01-13T15:20:16+01:00Erxleben, Fredof.erxleben@hzdr.deProject Management via a Group
I just created the group @software-hifis-net which currently contains @frust45, @hueser93 and @erxleb87 as members since we form the core developer team for the website.
My reasoning is that it might be easier for users to address @sof...
I just created the group @software-hifis-net which currently contains @frust45, @hueser93 and @erxleb87 as members since we form the core developer team for the website.
My reasoning is that it might be easier for users to address @software-hifis-net instead of having to call on each of us when they need support.
As fallout, a new _mattermost_-team was generated: https://mattermost.hzdr.de/software-hifis-net/
It is up to us if we move our bot messages there or not. (Or what else we do with it.)Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/83Ordering of events on events page should be done by event start date2019-12-16T15:18:24+01:00Hueser, ChristianOrdering of events on events page should be done by event start dateDue to the fact that events in the future only appear with flag --future set, we put event publication/creation date as prefix of the event page filename. Therefore, ordering is not properly done. We would like to order events according ...Due to the fact that events in the future only appear with flag --future set, we put event publication/creation date as prefix of the event page filename. Therefore, ordering is not properly done. We would like to order events according to event start date given in the "Front Matter" of the event page.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/53Enable browser feature detection2019-11-28T10:36:19+01:00Erxleben, Fredof.erxleben@hzdr.deEnable browser feature detectionInclude [modernizr](https://modernizr.com/) to enable the detection of supported browser features.
This would allow us to detect whether a browser is not capable to support features we use on our website and recommend switching browser...Include [modernizr](https://modernizr.com/) to enable the detection of supported browser features.
This would allow us to detect whether a browser is not capable to support features we use on our website and recommend switching browsers to the user in extreme cases.
Also it can enable the detection of low bandwidth on mobile devices and prevent/delay loading large images if that is the case to improve user experiencehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/58Include Jekyll-Assets2019-11-13T11:43:17+01:00Erxleben, Fredof.erxleben@hzdr.deInclude Jekyll-AssetsJekyll-Assets will help resolve #52 #54 #55.
Since including and configuring it can become a more extensive task I put it into this dedicated issue.Jekyll-Assets will help resolve #52 #54 #55.
Since including and configuring it can become a more extensive task I put it into this dedicated issue.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/38Create a template blog post2019-11-13T11:42:24+01:00Erxleben, Fredof.erxleben@hzdr.deCreate a template blog postWe need a template blog posts that other authors can use as a base for their own posts.
The template should show off the supported features and briefly explain them.
@hueser93 can reference the template in his blog post on how to creat...We need a template blog posts that other authors can use as a base for their own posts.
The template should show off the supported features and briefly explain them.
@hueser93 can reference the template in his blog post on how to create blog posts.
For inspiration see also #37 .https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/48Support the OpenGraph protocol2019-11-13T11:37:41+01:00Huste, TobiasSupport the OpenGraph protocolIn order to properly support sharing of articles/blog posts in social media (e.g. Twitter) with proper metadata we should support the OpenGraph protocol: https://ogp.me/
Example:
```html
<meta property="og:title" content="Title" />
<me...In order to properly support sharing of articles/blog posts in social media (e.g. Twitter) with proper metadata we should support the OpenGraph protocol: https://ogp.me/
Example:
```html
<meta property="og:title" content="Title" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://software.hifis.net/test/test" />
```Initial launch of software.hifis.netHueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/50Make sure title metadata is readable with background image in place2019-10-29T16:05:35+01:00Huste, TobiasMake sure title metadata is readable with background image in placeCurrently, the title metadata is hard to read if the background image has more than one dark color in this place. Find a solution that makes it possible to read the metadata regardless of the background image used.Currently, the title metadata is hard to read if the background image has more than one dark color in this place. Find a solution that makes it possible to read the metadata regardless of the background image used.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/24Allow for Layouts to Include Additional CSS2019-10-29T13:33:02+01:00Erxleben, Fredof.erxleben@hzdr.deAllow for Layouts to Include Additional CSSSo far each page that needs additional CSS has to specify the `additional_css` flag in its frontmatter.
Often pages of the same layout need the same additional CSS due to the layout they use.
Thus it would be sensible to have a mechanic...So far each page that needs additional CSS has to specify the `additional_css` flag in its frontmatter.
Often pages of the same layout need the same additional CSS due to the layout they use.
Thus it would be sensible to have a mechanic to include additional CSS by the layout, so it does not have to be specified by each page using this layout.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/46Create frontpage design2019-10-25T13:37:22+02:00Huste, TobiasCreate frontpage designThe frontpage is one the important parts of the website that is not yet designed. Create a design for a frontpage.The frontpage is one the important parts of the website that is not yet designed. Create a design for a frontpage.Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/45Consolidate CSS2019-10-25T10:20:50+02:00Erxleben, Fredof.erxleben@hzdr.deConsolidate CSSInstead of loading a dozen CSS files per page, create an `everything.scss` that just imports them.
The general header then only has to include `everything.css`
Check whether this implies that the other CSS files then have to be moved to...Instead of loading a dozen CSS files per page, create an `everything.scss` that just imports them.
The general header then only has to include `everything.css`
Check whether this implies that the other CSS files then have to be moved to the __sass_-folder.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/33Code block box is shrinking below code width when reducing window width2019-10-16T11:15:13+02:00Hueser, ChristianCode block box is shrinking below code width when reducing window widthOn mobile phones it is likely that code extends the code block box.
Use a different code highlighting style or fix css of current style.On mobile phones it is likely that code extends the code block box.
Use a different code highlighting style or fix css of current style.Hueser, ChristianHueser, Christian