The publication date for publications in the past is determined from the date parameter.
The date parameter is used to rank when the article appears on the website. If the date parameter is set to the future, then the article will be hidden until date is older than the current date.

For publications that will appear in the future, the to_be_published is set to true, and the publication_date parameter is used to display the publication date.

Both layouts/publication/single.html and layouts/partials/publication_li_detailed.html will now display the publication date using the same parameter.

Right now, date and publication_date both serve the same purpose in the end, so we might want to get rid of publication_date in a future version of this repo, and automatically determine whether or not a publication is to be published in the future.

I like the styling of the publications section on the front page. Good font, color etc. Still I have the following requests:

• a publication should get a full reference. Now it is just the paper title. but I think we need as least the following: Authors, title, publication, year where publication refers to the journal or conference. I do like to keep all the URL inks to projects, videos etc..
• The separate publication page (accessible after clicking on more publications) should be styled in the same way. So it will just be a page with a longer list of publications that are styled in the same way as the section on the front page. So, again, please add the URL links.

It's important to also have a visual representation of people that are involved in the project. Thus, the Participants block should also include portraits.

However, sometimes this may not fit in the page flow. We'll also have to make this block configurable.

Add the following three columns (horizontally stacked) to the opening banner:

BIAS_lab_

Bayesian Intelligent Autonomous Systems

About

We are an academic research team in the Signal Processing Systems group (EE department) at Eindhoven University of Technology. Our main research interest is in developing autonomous agents that teach themselves to behave intelligently through interactions with the environment. Typical application areas include (medical) device personalization, automated vehicle control and robotics. [Meet the team ...]

Mission

Learning through environmental interactions also goes by the name Reinforcement Learning. Our research on reinforcement learning is strongly inspired by developments in Bayesian Inference and Computational Neurosciences. Ultimately, we aim to develop a fully Bayesian reinforcement learning framework that is realized by message passing algorithms in highly modular Graphical Model networks. [Read more technical background ...]

Approach

Our research projects are usually selected by our quest to develop (reinforcement learning) technology to support in-situ hearing aid personalization. We 'eat our own dogfood' by immersing ourselves in complex acoustic situations and use our own tools to optimize audio processing algorithms under in-situ conditions. This leads to new problems that drive our next research steps. [Read more on approach ...]

At the moment information about people involved in the project can be specified in the archetype, but it isn't rendered anywhere on the project page.

For now, I would like the following headers/tags in this sequence:

HOME | MEMBERS | PROJECTS | PUBLICATIONS | BLOG | CONTACT

or perhaps

HOME | PROJECTS | PUBLICATIONS | BLOG | MEMBERS | CONTACT

I.o.w., at this point I think we dont need the RESEARCH tag. Research is represented by projects, publications and blog. Later, we may want to add tags for SOFTWARE or TEACHING, but that is not needed at this point.

The tab sequence is home -- projects -- publications -- blog -- members -- contact

the first-page section sequence is home--projects--publications--members--blog--contact.

Make the first-page sequence the same as the tab sequence (move blog up one slot to before the members section).

Hello,

the problem put as the title, how to fix this?

We would like to have an option to select certain key publications for the group.

Current proposal is:

We keep the block on the index page updated with the most recent publications and when a user clicks on Publications heading or All publications link, he first sees the key publications. Below them a list with other publications sorted in chronological order is displayed.

When I run hugo server -w everything works as expected.
But when I run hugo -d /var/html/public/hugo -b http://my-url.org/hugo -w things do not work as expected.

In particular:

1. The background-image: url("/img/header.jpg"); in hugo-academic-group.css doesn't properly add the {{ .Site.BaseURL }}. This can be fixed by commenting out that line of the css file and changing the first line of slogan.html to <header class="space-below " style='background-image: url("{{ .Site.BaseURL }}/img/header.jpg")'>. I haven't tested if this breaks hugo server -w versions of the theme.

2. During the build process header.jpg from the themes folder overwrites header.jpg in content/img/ folder, so that the only way to change the header is to edit the theme. I haven't yet figured out how to fix that one.

Make a proposal to nest the mennu w a submenu (just 1-layer of subnesting deep)

Currently, only three members of the group are being shown in the block on the index page.

We need to choose a way to show all the members in the block. Current proposals include following:

• carousel;
• random members on every refresh of the page;
• a block with all the members of the team.

Other proposals are very welcome.

The website currently lacks the block with information about the courses being taught by the members of the group.

I think there's a mismatch between the vacancy and open_projects. Creating new vacancies don't seem to add anything to the main page, and digging through the code it seems as though it was partially renamed.

For what it's worth, I like the format you use on your website to have a variety of vacancy types (graduates, postdocs, undergrad capstone projects, etc come to mind). It possible to push in the modifications you've made to make that sub-menu viable?

We are technically a sub-group of the SPS group. It would be good to be able to navigate to our parent group. In our case, I suggest to write in the left upper corner

parent_group_name / group_name

which in our special case translates to

SPS / BIASLAB

The parent_group_should be clickable and link to the homepage of the parent group, which in our case is
https://www.tue.nl/en/university/departments/electrical-engineering/research/research-groups/signal-processing-systems-sps/

Amazing template! I having troubles with running this using RStudio (with Hugo/Blogdown). When running the group using R and RStudio there is no CSS. This occurs whether using the RStudio Hugo Blogdown module, Github cloning, or the console commands on your site. See attached image of output.

GCushen's Academic template works using these methods in RStudio. I am currently unable to identify what difference between the Academic and Academic-Group templates is stopping casuing issues using the hugo-academic-group template.

At the moment, we add some features to the theme that might not be useful for other groups. Furthermore, if the groups directly follow the suggested way of maintaining the website (makefile use), it might break the builds of their website.

We have to add proper release management to this theme and update the maintenance guidelines so that use of this theme remains a pleasant experience for all the groups using it.

Going forward we will use the team name BIAS_lab_ rather than SPSbrats with tag line 'Bayesian Intelligent Autonomous Systems'

It seems the toolbar buttons go to anchors, but if you are on the "members" page (for example) they don't work.

At the moment the only way to specify the relationship between project and publication is to provide the project_url parameter for the page.

It would be nice if we could specify key publications for the project that will show up in a participants-like block on the project page.

This is an amazing theme. Thanks! I am using this theme for building a website for my research group. It is only one step from perfection: can publications be displayed automatically on the member page?

I found that the projects appear automatically on the member page (member/xxx), and tried adding the following codes into https://github.com/biaslab/hugo-academic-group/tree/master/layouts/member/single.html#L115 but I failed:

           {{ .Scratch.Add "found" false }}
            {{ $member_id:= .Params.id }}
            {{ $publications:= where .Site.Pages "Section" "publication" }}
            {{ range $publications }}
                {{ $current_project := . }}
                {{ range .Params.authors }}
                    {{ if eq .id $member_id }}
                    {{ if not ($.Scratch.Get "found") }}
                        <div class="row">
                        <div class="col-sm-12">
                            <h3>Publications</h3>
                            <ul>
                        {{ $.Scratch.Set "found" true }}
                    {{ end }}
                    <li>
                        <a href="{{$current_publication.Permalink}}">{{ $current_publication.Title }}</a>
                    </li>
                    {{ end }}
                {{ end }}
            {{ end }}
            {{ if (.Scratch.Get "found") }}
                </ul>
                </div>
            </div>
            {{ end }}
            {{ .Scratch.Delete "found" }}

Sorry that I have little knowledge in these codes.

On the "view all members page", maybe add some padding to the list items so it is clear which name corresponds to which picture. (copy-paste from marco's comment in slack)

The header block now only supports the following structure:

University -> Group -> Sub-group

In some cases certain groups might just want to specify the universities/parties involved in the project and the logo in the left corner doesn't have to be an University logo.

Using hugo version 0.58.0, the example site for hugo-academic-group fails with

a23448:/home/../test [20:22]$ hugo server --watch Total in 12 ms Error: Error building site: failed to render pages: render of "home" failed: "/home/joishi/tmp/test/themes/hugo-academic-group/layouts/index.html:1:18": execute of template failed: template: index.html:10:3: executing "index.html" at <partial "index/publications.html" .>: error calling partial: "/home/joishi/tmp/test/themes/hugo-academic-group/layouts/partials/index/publications.html:1:18": execute of template failed: template: partials/index/publications.html:12:23: executing "partials/index/publications.html" at <partial "publication_li_detailed" .>: error calling partial: "/home/joishi/tmp/test/themes/hugo-academic-group/layouts/partials/publication_li_detailed.html:1:18": execute of template failed: template: partials/publication_li_detailed.html:26:19: executing "partials/publication_li_detailed.html" at <partial "authors" .Params.authors>: error calling partial: "/home/joishi/tmp/test/themes/hugo-academic-group/layouts/partials/authors.html:1:18": execute of template failed: template: partials/authors.html:1:18: executing "partials/authors.html" at <len .>: error calling len: len of untyped nil
I am having this issue with a site of mine that previously worked. However, I was able to reproduce the same error by following exactly the instructions here for creating the sample hugo-academic-theme site using hugo v.0.58.0 on Ubuntu linux.

Currently it refers to /member/name/e-mail, while it should be mailto:e-mail to work properly.

Here is an idea:

the mission page, approach page and project pages should also be registered as blog pages. Perhaps they should be regular blogs and the mission read more, the approach read more and the projects' read more links should forward to the correct blog page.

In near future we would like to have a dedicated page on the website about the software developed in the group.

The layout should loosely follow the layout of Projects section on the index page (a paragraph of description + a picture and a collection of links).

Vacancies submenu contains invalid links if a user is not on the main page of the website.

I would like the following:

• The projects section at the landing page should for each project contain an (optional) image (not defined now) and an (optional) project description ( a few lines as defined in the "description" tag in header, already works)
• After clicking through to the project page, the image (as defined in the "image" header) should not be inserted at the top of the page. One should have the freedom to style this page in any way, use regular markdown. It should also be clear (through) an example where to put optional images and how to link to it. Currently, eg, markdown like ![my image](projects/myimage.png) does not work.
• At the bottom of a project page, there is link to the next or previous project, e.g. at the bottom of the "Deep Learning" project, there is a link to the "Wide Learning" project. Please make this link as "Next Project: Wide Learning", where "Next Project" is in dark blue font and "Wide Learning" in the current light-blue font.
• markdown does not work in the description of the project. (low priority)