software.hifis.net issueshttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues2021-02-28T08:06:08+01:00https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/146A Template for software.hifis.net team member entry - A PROPOSAL2021-02-28T08:06:08+01:00bezayeA Template for software.hifis.net team member entry - A PROPOSAL@software-hifis-net Please add me as a member.
# Request to add Team Member
>>>
This template is a baseline to define the content of the HIFIS Software services website pages for team representation.
>>>
### Family Name(s)
>>>
...
>>>
#...@software-hifis-net Please add me as a member.
# Request to add Team Member
>>>
This template is a baseline to define the content of the HIFIS Software services website pages for team representation.
>>>
### Family Name(s)
>>>
...
>>>
### First Name(s)
>>>
...
>>>
### Organization
* [ ] AWI
* [ ] DESY
* [ ] DKFZ
* [ ] DLR
* [ ] FZJ
* [ ] GFZ
* [ ] HMGU
* [ ] HZB
* [ ] HZDR
* [ ] KIT
* [x] UFZ
### Position
>>>
Enter your current position here
>>>
### Main Entry
>>>
*This will be the body of a page presenting a team member. It contains "About" section containing brief biography of oneself, "Interests" section listing main topics of expertise and interests, and "Responsibilities within HIFIS Software Cluster" section (mandatory) containing a list of key roles each team member has.*
>>>
##### About
>>>
*Introduce yourself briefly in few sentences. This will be useful for anyone seeing your page to match it with the "Responsibilities within HIFIS Software Cluster" section which is visible within the same page.*
>>>
##### Interests
>>>
*List here your key topics of interests*
* Interest A
* Interest B
* ...
>>>
##### Responsibilities within [HIFIS Software Cluster](https://www.hifis.net/services/software/index_ger.html)
>>>
*List here your responsibilities within HIFIS*
* Responsible for this
* Responsible for that
* ...
>>>
### Contact:
>>>
*Contact for individual team member entry should be the general email address hifis-info@hzdr.de. This will maintain all requests to be sent only to the general email address and not to individuals. This way, requests can be collected and filled without missing any.*
>>>
* [e-mail](hifis-info@hzdr.de)Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/85Font size in page titles should be scaled down according to title length2020-02-05T16:49:25+01:00Hueser, ChristianFont size in page titles should be scaled down according to title lengthSome titles for blog posts and events can be quite long and consume a lot of space in the header.
We would like to shrink/down scale the font size for titles according to the length of the title.Some titles for blog posts and events can be quite long and consume a lot of space in the header.
We would like to shrink/down scale the font size for titles according to the length of the title.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/66Recude quality in image variant creation2020-02-05T16:49:36+01:00Huste, TobiasRecude quality in image variant creationCurrently, we create variant image sizes with the script available in the `scripts/` directory. This works pretty fine.
I suggest to reduce the quality level, in order to further reduce the size of images that need to be loaded. I can't...Currently, we create variant image sizes with the script available in the `scripts/` directory. This works pretty fine.
I suggest to reduce the quality level, in order to further reduce the size of images that need to be loaded. I can't see a real difference, but the image size was more than halved for some examples. Something along this way:
```diff
diff --git a/scripts/create_jumbotron_variants.sh b/scripts/create_jumbotron_variants.sh
index b24b7d6..3df4855 100755
--- a/scripts/create_jumbotron_variants.sh
+++ b/scripts/create_jumbotron_variants.sh
@@ -84,12 +84,12 @@ do
else
# Create new version for this breakpoint
echo "Generating $target_file ($target_width px)"
- convert "$source_file" -resize "$target_width" "$target_file"
+ convert "$source_file" -resize "$target_width" -quality 50 "$target_file"
fi
else
- # Instead of upscaling, create a relative link to the original
- echo "Creating link $target_file (Source smaller then target)"
- ln -sr "$source_file" "$target_file"
+ # Instead of upscaling, only reduce quality
+ echo "Reducing quality of $target_file"
+ convert "$source_file" -quality 50 "$target_file"
fi
done
done
```
@hueser93 @erxleb87 What do you say?https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/52Optimize browser caching of Assets2020-02-05T16:49:44+01:00Huste, TobiasOptimize browser caching of AssetsIn our webserver configuration we will activate caching. Currently, this might lead to situations, where the website and the distributed CSS or JS don't fit together anymore. This might lead to weird behavior. Typically this issue is sol...In our webserver configuration we will activate caching. Currently, this might lead to situations, where the website and the distributed CSS or JS don't fit together anymore. This might lead to weird behavior. Typically this issue is solved by adding some hash to the filename of the generated CSS. Example: `hifis.dh45js.css`. Like this, the browser definitely knows, when to load a new file.
In Jekyll there exist multiple solutions. As a beginning, I would suggest to go for the most easy to implement approach by adding the generation timestamp.
```html
<link rel="stylesheet" href="hifis.css?{{site.time | date: '%s'}}">
```
Like this, the browser knows, when to load new assets. An ideal solution would be to add a hash to the file. This would probably require a plugin. One could have a look at https://github.com/envygeeks/jekyll-assets.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/43Hover tool-tips for social media and messengers2020-02-05T16:48:02+01:00Erxleben, Fredof.erxleben@hzdr.deHover tool-tips for social media and messengersImplement hover tool-tips for social media and messenger badges, using the name of the platform/messenger as default. If provided, extend by the `show_as` property defined in the persons contact info.Implement hover tool-tips for social media and messenger badges, using the name of the platform/messenger as default. If provided, extend by the `show_as` property defined in the persons contact info.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/13Web Analytics using Matomo (formerly Piwik)2020-02-05T16:47:56+01:00Huste, TobiasWeb Analytics using Matomo (formerly Piwik)For HIFIS we are required to keep track of KPIs. Matomo can be self-hosted and will help to keep track of visitors and other statistics. Currently, the tool is probably not hosted at HZDR. Discuss, if we should start self-hosting it, or ...For HIFIS we are required to keep track of KPIs. Matomo can be self-hosted and will help to keep track of visitors and other statistics. Currently, the tool is probably not hosted at HZDR. Discuss, if we should start self-hosting it, or find out if it is already hosted at HZDR. If we don't want to do this, find another solution.
Relavant links:
- https://os.helmholtz.de - uses Matomo
- https://matomo.org/Huste, TobiasHuste, Tobias