== IMPORTANT UPDATE 25/3 ==
Several bugs have been identified in the final submission. Please follow these updated instructions:
As the Android app is not working (except to open up a link to the website containing the web demo), please skip this part of the submission and instead to proceed directly to joinacademia.org using a desktop or mobile. (While the demo works on mobile, there are currently sizing issues with some components.)
At joinacademia.org, navigate to "Get Started" and click "Go!" on the School card. Then, enter in the following code:
548329
Please now be advised that it is NOT better to sign in to the website in order to complete the walkthrough. Also note that, at present, the information you enter during the walkthrough will be available to people on subsequent visits so entering dummy data is recommended (although you are also free to go back through and delete the data you've entered if desired).
Also (known bugs):
**** The link to the Academia whitepaper in the demo appears to be non-functional. Go to http://upontheewe.eth.link to access.
*** A couple of ancillary buttons show a notification that says "Sent" when clicked instead of doing what their label indicates. In particular, the button at the end that says "Show whitepaper" doesn't work. Use the link to the whitepaper in the introduction instead.
*** A few typos (including in the supplementary materials). Especially, on the final page, it talks about a "DQC DIAGRAM" twice. The first of these should be a "DIRECTIVE RACE DIAGRAM."
And additional notes:
*** The publicly available template for the demo may be found here: https://go.glideapps.com/app/1EdstsN5Du5Wm8LSqojZ-template. Please be advised that it is better to go through the walkthrough using the live website rather than the template (as the template is populated with messy testing data).
*** There is a dummy DQC Diagram included at the end of the demo although on reflection it may not be entirely obvious how to use it. In short, there should be an area to the right of the diagram that says "List" and people should be able to drag the Commands into the list to give them an order, and then edit them further (i.e. add funding if desired and then publish publicly). Indeed, the tasks could simply have been shown as a list on that page to illustrate this, but a DQC Diagram was packed in there as they (a) become increasingly useful as one progresses with one's projects, giving a high-level overview of one's state of progress, and (b) are useful to view and manage a different said of tasks, namely the tasks one is engaged in as a worker. They can also be transformed at a click into a traditional wiki-style site or so that all commands are organised (by priority) into the centre of the diagram. Hopefully that makes things clearer and makes a case that, far from being "a diagram for the sake of being a diagram," its inclusion is well-earned.
*** A few days ago, I spent a few hours on getting School ready for simple practical use (for my own personal tasks and for dev tasks related to Academia/School). I've been attending to other matters since then but its close to me posting my first live task (i.e. that anyone get paid to complete).
David Hopkins Claque
Log in or sign up for Devpost to join the conversation.