We don't have chapters written yet but now would be a good time to create the infrastructure for them so we can just drop in the content when they're ready.
I'm working with a designer to create the look and feel, which should be ready by July. Meanwhile we can get started on the backend routing and templating in preparation.
We should create the following templates:
The Almanac is an annual report and I expect to do this again next year, so we should be proactive and separate the annual content from the static content. In this case, the home page is static to the project while things like table of contents, chapters, methodology, and contributors may change year to year. These should all be organized in a 2019 template directory.
The contributors page will be based on the data in this sheet. It might be a good idea to create a JSON metadata file of all contributors and generate this page dynamically. This way we can also dynamically add authors/reviewers on the bylines of their respective chapters.
Any volunteers from @HTTPArchive/developers who can take part or all of this issue?
I part want to help.
Isn't it a problem to create a public web API use Google SpreadSheet script?
I made the next simple script. (I can not add this script to the original because I have no authority)
https://gist.github.com/MSakamaki/795b4c947fb0fdfc8e41d320e6e5ddc1
This points to my sheet where I copied the contributors page.
https://docs.google.com/spreadsheets/d/1DB0dhdgRiWfAeH5gTEd7nd3zsEuaNCMqp0gA1IGVzUA
When you hit the following API, you get json of name and hyperlink.
https://script.google.com/macros/s/AKfycbzuHDBRkaOlOi_iioNVKYQxVpQ4mZJy2V8xVS_l9FJM0eF3zhPq/exec
If there is no problem, we will start producing json API including the role.
I can take care of the scaffolding
To clarify, I meant using a server side JSON file to maintain the contributors list. The Sheet was just an example of the current list 馃檪
@rviscomi
Oh, I understand. Thank you for your explanation!
The templates exist, but we still need to write content for them. We can do that in follow-up issues.