The API is ready now. Wasn’t easy but @daniel got it to work on the live site today (yay!). I’ll move the documentation with some updates to our API manual now.
How much of the user interface designed by Natalia’s team would these onboarding sites re-use? If they will look and behave quite differently, you can also make your own brief and look for somebody to create the JavaScript application for this. It will still make sense that the same person is then briefed by @hugi later and does the Biennale site as well. But it could speed things up somewhat. I can add the relevant technical parts to that brief, if you decide to go this way.
Great. Remember to also include the ethics. Everything that ends up on the platform needs to pass through some sort of ethical approval for us to use and analyze the contributions. I suppose @alberto and @matthias know how to formulate this in English?
The wording of the current consent funnel questions is contained in consent.hbs. I propose to include a checkbox with a sentence or short paragraph to the same effect, summarizing what people are supposed to learn from this consent funnal Q&A exercise. We can then show it to our ethical advisor for approval, and modify it if necessary.
Ok, finally, after tumultuous developments we have it - the final tablet version. If it’s ok and everyone agrees, I will tomorrow have the mobile and desktop versions as well:
I hope it’s all clear if not, I am here to answer any question
the Exit button comes at some point - in my mind, it would actually transport you at any point to the final slide, where you have to give your data and submit. So the information that you can finish anytime will show once you hoover over it. Would that work? Very sorry it took so long. TAblet is most important as it will be part of the exhibition, so let’s start with it.
There are some things that need to be added for the design to work with the API.
How should these answers be compiled into a post? How should it look on the platform? Should questions be made into headlines and bunched together? Headlines are quite long.
Where should the age information be stored? API has no place to store it except in the post. Should it be included there, like “Age: 54” at the top of the post?
Check point 6 under “Typical usage” under 3.4. Multisite account creation in API description, the design needs to include that “Account summary” page once a submission is completed.
This design does not include how error messages should be handled. Either include that, or the developer will just use the simplest “out of the box” design which you might not be happy with.
This is the brief I will send out, along with bounty. @matthias: How much money do we have left in the budget?
Brief: Edgeryders questionnaire
We are deploying a new on boarding funnel for edgeryders.eu. Multiple overlapping communities are working on the platform to understand and solve problems. A vital part of this work is to invite new stories and perspectives, and to do so we want to create a simpler and more welcoming first contact with our communities. Our way of engaging people revolves around asking open questions relating to the subject matter we are exploring.
Our new on-boarding interface is a questionnaire where the answers get posted to edgeryders.eu, and the user would then automatically claim that content as their own when they registered on edgeryders.eu.
We are building the first version of it to be used on a tablet at the Biennale of Design in Ljubljana on November 14th. To leave some time for testing, the deadline to have the interface ready is November 1st.
Project scope
Edgeryders have already built the API which creates a user on edgeryders.eu with a given email and makes a post on that users behalf. This API is described in the Edgeryders API documentation, under 3.4. Multisite account creation.
This brief is for creating a fully client-side javascript form which collects:
A users email
Responses to a number of questions from a user
Some additional but voluntary data
It then should then:
Compile answers to questions into a Discourse post
Request a new account to be created with user email
Make post with compiled answers on edgeryders.eu as new user
Requirements:
Design of the app is shown here, and shows how it should look on a tablet. This design shows the actual questions that should be asked and all relevant copy.
App should follow the flow and logic described in API documentation
App should follow error handling recommendations and display relevant error messages when they are returned from API and advice user on how to proceed
Once post has been submitted, app should show the account summary as described on
App should be completely client-side and any code running server side, except for hosting.
The API work used approx. 1500 EUR. So 1500 EUR are left.
Two things I’d add to the brief in order to make the resulting software easier to re-use for our other projects, including by @nadia:
The question definitions should be configurable via a configuration file in JSON or YAML format.
The software should use the Vue.js framework. So that we can settle for that framework as our standard for single-page web application development, and are able to adjust and remix the different pieces of software that will accumulate over time using this framework.
I think you mean “completely client-side without any code running server side”.
I would like the questions to be in bold, starting the paragraphs - i feel like without them many answers will not make sense, so it’s better to have them, esp if someone skips a question for example.
Age - at the bottom of the post
I will add the missing data to the final screen - since there is information like this showing on the final page, after you hit submit, would it be sufficient or I have to add the data you described?
*you will receive the confirmation of your participation and access to delete or edit your data on your email, as well as the updates on the Academy of Life program and events. You can opt out at any time, no spam guaranteed.
I will submit an error-page design asap
Regarding the flexibility - can all the text be adjustable, so I don’t need to design the final page again, but just edit the text in the api when it’s ready?
And would it be possible to leave space for illustrations, visuals, on the side - esp when on desktop/tablet?
The text can be made easily adjustable via a configuration file, as I proposed above. To edit that configuration file, you’d have to edit it somehow, the easiest would be via the web-based editor on Github. After that, it has to be copied to the server from where the website is served (which can be automated, but that’s not always a good idea as it can break the site when somebody editing the Github repo is not aware of that side effect).
For what it’s worth - some of this work has already been done for the festival site. We have a basic component for forms that reads a questionnaire from a JSON file, breaks it down into question/answer instances and sends the response to a server. I can put that component on Github as ‘edgeryders forms’ and we can see where it goes from there, with perhaps an external developer to fill in the missing elements mentioned in @hugi’s post.
do the individual forms have unique urls @owen? It would be great to post links to open the forms directly from posts on edgeryders.eu (topics containing session descriptions) without having to go through the festival website. because that is where people would be coming from in the first place.