Some question to do with multilingualism/localisation for these forms (note: this is not a request for any changes @owen and @matthias - also @hugi you might be interested to know this ):
Let’s say we want to produce translations of a form page so as to direct it to different audiences
Is it possible at the moment in the current state of the code to have multiple instances of the actual form bit that have the same functionality, but have different language texts on the actual form sections, questions and buttons? More specifically these:
Using Edgeryder Forms for events - Step by step guide:
1. What are Edgeryders Forms used for with events?
Edgeryders Forms provide an easy access to join the platform and a specific conversation both for new and sporadically present community members who still have problems navigating the platform.
The idea is that the link to the “form” is the only instruction needed to get them onboarded to the event, conversation and platform.
Therefore an event form needs to include a description of the event that would serve as an introduction to the topic by itself and states that it is an event organised by Edgeryder + x collaborators.
Filling out the form does two things:
creating a new or logging into an existing account
Posting a comment in a thread defined in the form template
The goal of the form is not to generate a list of participants for the event. Registered event participants are everyone who has commented in the thread the form links to for the output posts. The link for the call will be sent via pm to everyone who has commented in that thread, which automatically includes all the ones who filled in the form as well as those who already were on the platform.
Therefore it is important to make sure to link the participant information sheet from the beginning in the post header that is linked to the outputs of the form (question here @nadia, should we link that output directly to the event page on the platform (like this one for Messina) or create a new thread? A new thread could generate confusion, linking directly back to the event page would prob best?)
2. The Output Thread:
The form generates comments for a thread of your choosing.
Make sure this thread includes:
The lines:
* “All who comment on this post will receive the link for the event call.”
* “Note that by attending that call you will consent to the recording and transcribing of the call for research purposes as described in the participant information sheet.”
* “Do not share the link to the call directly but rather share this link if you want to invite someone (put the link to the form).”
Redirect the output of the form:Change the “topic” number in the configuration (for example “topic”: 14202) to the number on the end of the URL of the Output Thread you created.
Edit, copy, delete or adjust the texts in the different fields as you need and check the results in the preview. Remember to include an event description that could stand on its own on the top and mention the organisers (edgeryder + collaborators)
Once you are satisfied with your form, you can edit the WebKit page (like this one Messina District Webinar - Webkit [XML]) to include the form. > Enter edit mode in the WebKit post of your event and add/edit towards the end of the post.
What I’ll do is make the button text configurable (this is already the case for the account and confirmation text) - this way a form can be translated into any language - with each translated version saved in a standalone topic.
I’ve added an option to include logo(s) - multiple ones along with the Edgeryders logo if needed.
The footer is now there, and there is an optional partners section - the example form includes all these.
Also the login text is now configurable, so theoretically you can change the entire form language - the only things that would stay in English are now the footer and the error messages.
you modify this part of the configuration, as it describes here:
"publish": {
"topic": 14202
}
You can either put “topic” to specify the topic_id where you would like the answers to be posted in a single thread - or replace “topic” with “category” and put the id of the category you want the responses to be posted in.
In the latter case each answer will be posted as a separate topic in that category.
Here is an example where the responses will be posted in the campfire category (id 237):
But Edgeryders Forms doesn’t work when I put the topic name in the script…
No worries if not, it will be public after all, so maybe it doesn’t matter. Just wanted to be sure that the answers to the form don’t need to go to the page with the script, but can go to any platform topic you instruct them to!
Question for @owen and @MariaEuler: in the new account creation through the form, is the user taken through the original platform consent funnel? (for participating in research?) I suspect that is not the same as the consent for participating in webinars and online events,
{
“type”: “consent”,
“required”: true,
“text”: “The call will be recorded for research purposes. Please read details about that process in this information sheet and confirm that you understand and consent to the recording of the call. This is required to register and attend the call”,
“label”: “I agree”
},
Just with your particular form of the consent sheet linked
@owen, there is no pressure at all on this request, but I was wondering how these forms could be used in other edgeryders affiliated forums such as Blivande (https://forum.blivande.com/). Might be interesting down the line when we are organising regular workshop events at blivande for example. But we can absolutely also use something else.
Asking just in case it only means to copy in a different line. Otherwise just ignore this
We definitely need to do this. I’m administering the Blivande forum, so I can do it.
@owen, do we need our own branch or can we somehow use https://tell.edgeryders.eu but have it post on Blivande? If not, just point me to the right repo and what variables I need to change, and I can deploy with Netlify.
Ok this will require quite a bit of configuration:
Set up the multisite_account.json API endpoint, with the plugin James built
Check that “Allowed user api auth redirects” is enabled in the Admin and configure the redirect URL to return to after the user has logged in. This should be the domain of the form site + ‘/auth_redirect’. So tell.edgeryders.eu/auth_redirect in our case.
Add the site domain to the CORS whitelist (both for the platform and for the edgeryders-multisite-accounts.json endpoint)
Configure the .env file at the root of the repository (create one if it does not exist) and you will need to add the following values (examples shown when possible):
There are some more instances where the code to post a topic is hardcoded to edgeryders.eu, I’ll have to update this to rely only on the .env variables - until then do a search and replace on any ‘edgeryders.eu’ strings inside src/App.vue to point the requests to the Blivande platform.
