A fair representation of the contributors at the website using and modifying the all-contributors allowing the tasks specific to the Brainhack proceedings such as

• Reviewers
• Editor in Chief
• Handling Editors
• PR Team (presentations etc.)

instead of directly linking to submit issue template, link to info about what we expect from submissions

Please check that the svg of the web page banner is displayed correctly according to window size. The svg is calculated on the fly based on number of points, their displacement and their radius.

• with info about submission scope/expectation
• links to Hugo template files that need to be changed by authors
• links to readme that describes the all-possibilities-template
  readthedocs maybe a very well suitable integration for that

PDFs rendered by this repo have the following header design:

I can work on a new design to indicate which year do they belong or omit this from the PDF, if the template iframing the PDF is going to contain the header.

This http://proceedings.brainhack.org/submit/ has redundant information with the docs. We should remove this redundancy and simply add a few summary lines with links to the most important sections of the docs.

• with instructions for submitting authors
• link to list of possible reviewers they may suggest

including

• field of research
• coding language
  very much like in joss

Please check all links that they actually work, and link to the correct repo (instead of test templates)

Use the json files from Hugo workflow instead of regexp we use so far for content inclusion to the proceedings webpages

as part of the doc
could be provided as an md file checklist the reviewers could copy paste into they answers to the editor in the issue thread of the submission

and i have to check if there is a written workflow somewhere where these should also be linked :) lovely material!

Their names should appear on the Webpage as well as in the pdf

• A FAQs at the main website that is answering the initial questions curated throughout the presentations.
• FAQs will contain brief explanations about the content at hand and will have pointers to the comprehensive guidelines and tools.
• Will be written in a markdown file

Hi all!

The website looks really nice, but while working in PR #17 , I've found it scales the page for mobile, making texts really small. It may impact the general experience and it is not accessible.

I was wondering if you discussed to support mobile platforms at some point, and if it is on the roadmap and no one is working on it, I volunteer for the task! One possibility is to follow the structure from the template, which is responsive already.