Safety Board: We could have a two columns layout, like support.tpo.org. You could keep the toggle always open.
Research Groups: I think this content will works better if we use cards!
Something like
<div class="col-md-6"><div class="card"><img class="card-img-top" src="/.png" alt="University College London"><div class="card-body"><h4 class="card-title">Information Security Research Group, University College London</h4><p class="card-text text-muted">The group comprised expertise across all filed of security, cryptography and privacy, including the study of anonymous communications, traffic analysis, censorship resistance, measurement studies, and privacy related cryptography. In related areas the group studies human factors and usability of privacy systems, genetic privacy, infrastructure privacy and abuse in online communities and media.</p></div><ul class="list-group list-group-flush"><li class="list-group-item"><mark>Location:</mark> London, UK </li><li class="list-group-item"><mark>Key People:</mark> Emiliano De Cristofaro, Steven Murdoch, George Danezis.</li><li class="list-group-item"><mark>Additional Links: </mark> <a href="#">Publications</a>.</li></ul></div></div>
Technical Reports: Could we have a border-light line between each <p>?
I see there is a Romanian translation already, so I guess you don't need help with the lektor-i18n-plugin.
"translation" is perhaps an overstatement. Only the menu items are translated.
I'm hoping to pick this up again next week, either Wednesday or Thursday. There is not currently a repo as I am waiting for hiro to build the workflow for how we build and deploy these sites.
If I make the changes that antonela has suggested and put everything in a git repo, perhaps you can take a look to get it translatable?
This is not a large site, and it also does not require translation (as discussed with other research team members in Brussels, much of the world's academic community is presenting at conferences/in journals in English).
I found I was fighting with Lektor more than I was working on the content so I have instead ported the styleguide to Hugo (in an evening) and now have something that should be ready to deploy next week.
Deployment will require a single static binary to be available on the continuous deployment machine (for hugo) and no other dependencies.
Once this is done, we can move forward with curating these research ideas and adding the other content we discussed for the research portal.
Trac: Summary: Port the research portal content to Lektor to Port the research portal content to Hugo Description: This will allow easy update to conform to the styleguide and make it easier to edit the content, and provide translations if desired.
to
This will allow easy update to conform to the styleguide and make it easier to edit the content. Cc: antonela, hiro, mikeperry to antonela, hiro, mikeperry, chelseakomlo