publication_date, date, to_be_published - too many cooks?

[abpolym]

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.

[abpolym]

The easiest solution would be:

• use publication_date always to be used for the actual date of the publication
• automatically detect when a publication is to be published, and get rid of to_be_published
• optionally use publication_date to rank the publications chronologically

Edit: We also have to add/update all publication_date in all publications, once we use publication_date

[abpolym]

Fixing this issue should fix biaslab/biaslab-hugo#160