Questionnaire digital iPhone.pdf (67.9 KB)
Questionnaire digital iPad 01.10.19 FINAL(1).pdf (68.3 KB)
Once again, final versions (we changed the progress bar for smaller, leaner dots) for tablet and mobile
I expect to have the domain registered by the end of the week as well
It looks very nice @natalia_skoczylas.
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.
@nadia I can implement this.
Ideally we’ll set up an address - something like forms.edgeryders.eu to host all the forms we use. Will ask @matthias.
I have posted the bounty here.
I have cross-posted it in the Discourse Meta forum, and I will also cross-post in NGI conversation.
Oliver will also send it to his devs at WorldBrain.
The domain could be retirement.edgeryders.eu or bio26.edgeryders.eu @owen - we will also have a domain provided by the museum, we can use it as an alias
I made the domain bio26.edgeryders.eu and set up DNS with CNAME edgerydersbio26.netlify.com. @owen, this should already allow you to use it via Netlify by choosing that edgerydersbio26.netlify.com subdomain for the site you’d host there.
This is our setup for the general forms across different ER projects: https://edgeforms.netlify.com/
I’ve kept things simple, only taking the necessary elements to build a form from scratch, all stored in a single json file for now.
There are a few basic customisation options to get started, background colours or images can be set for the introduction page, the navigation elements adopt custom colours too.
Here’s an example of the festival ticket questionnaire:
festival_ticket: {
title: 'Festival Ticket',
slug: 'festival_ticket',
id: 'registration',
description: 'Sign up to the Edgeryders Festival, November 19-29th 2019!',
background: {
splash: '#1AA4B8',
standard: '#EDF2F7',
confirm: '#EDF2F7'
},
color: {
splash: '#fff'
},
link: {
name: 'festival.edgeryders.eu',
url: 'https://festival.edgeryders.eu'
},
splash: [
{
text: "<h1>So, you want to join the Edgeryders Festival in November?</h1> <p>Great! Your skills and knowledge are valuable.</p> <p>Participation does not cost money. You secure your ticket by filling out this form and following the instructions for some small and easy tasks that will be sent to you by email afterwards.</p>",
}
],
questions: [
{
question: "What is your email address so we can contact you?",
small: "Don't worry, we're not going to spam you.",
type: 'email',
id: 'email',
required: true,
},
{
question: "Your name or alias so we know what to call you?",
type: 'text',
minLength: 2,
id: 'name',
required: true,
}
]
I like it, it’s a nice to-the-point definition of what a form would need. We can take that format as a starting point for form-related software infrastructure that would also include the post-to-Discourse system that will be made by @gdpelican, initially for Natalia’s Biennale usage.
Can you publish it please? Best time is asap 
as it is relevant for @gdpelican as input for his development work.
Yes, it’s here
What is the final consent funnel version for this? Do we have one, or should I prepare it? (as brief as possible)
I’d be happy to make one based on the Field Study Template Kit books, I just got them from a friend and they have basically everything for ethnographic research in them.
Questionnaire digital desktop MAP VIEW.pdf (24.7 KB)
The map is to be changed at the end @gdpelican - let me know if it works
Also, will you use “live” text for the interface or the designs directly - because we also have a version in Slovenian language and I’d like to implement it as well, let me know what’s more convenient for you
Can you explain what you mean a bit more? Not sure I get it.
there;s text in the design, and I need it to be available in two languages - do I send a whole interface design for both options, or would it be enough to just send the text in both language versions? Not sure if I explain myself well, brace with me 
Ah, no. Just make the text available in two languages. @gdpelican is making it so that it’s easy to adapt.
Here they go, both texts in English and Slovenian: (the 3rd one is adapted for print version, ignore it)
My first attempt ended with an error and I couldn’t submit, picture in attachment
The Age should be optional
The text in Latin is for the consent funnel - I was trying to understand which text do we use, should I prepare one or we use the one that is in github?
Also, we need the SLO/EN button on top of the first page and the access to Slovenian version (I shared the slovenian language version of the text above in a google doc)
These are first issues I saw @gdpelican@matthias @hugi - hope it’s not too much to change. Otherwise, looks great and does MAGIC! Thank you all, @gdpelican - I haven’t thanked you yet, I am incredibly grateful! Happy to take you out for a drink in berlin sometime! 
Being able to switch between two different languages on the new installation is a new requirement that was not in the original specification. The project is already bogged down because of the unforeseen issues with Discourse. @gdpelican can keep it in mind if there is time? What we can do otherwise is to have two installations - one in each language.