Improve petition configuration forms: labels / hints

[fallen]

On petition configuration / edit page, most of the text is very "raw" and hard to understand for non-expert users.

• Most form field labels should be rewritten for something more clear
• Some hints should be shown that explain what to write and what the field is for.

[martinlehoux]

Is it ok if I work on this this weekend ? Or is there something more critical to do ?

[fallen]

That's an important point.
Something I should create a ticket for: I am writing a prototype for a new "edit" process.
The new edit page would be like the final petition page, but with embedded "inline" TinyMCE editors (like over there: https://www.tiny.cloud/docs/demo/inline/)
So in the future I guess we will get rid of field labels for the petition content.
However there would still be formulars, fields, labels for the remaining options (colour stuff, meta data)

[martinlehoux]

I started looking at this, I think I need some time to figure out what the fields actually do ^^ Maybe we could need the help of a non dev user to tell us what is not clear enough.
I also tried to add tooltips to labels to add more info text, I don't know which is the best, between the tooltip and the grey text below.
I think it might be cleaner when we have several fields below each other

[fallen]

To me, things like "Twitter xxx" need to be renamed since they are not about twitter in particular but social network in general.
Except maybe the "Org twitter handle" which is really just about Twitter.

Basically those settings are what is ending up into "OpenGraph tags" in the petition page that will most probably be shared on social networks.

I use two sets of open graph tags, those that are "standards":

• og:title
• og:description
• og:type
• og:site_name
• og:image

And those that are "Twitter non-standard" ones:

• twitter:card
• twitter:image
• twitter:description
• twitter:site
• twitter:creator
• twitter:title

All those tags are here to provide metadata for both search engines and social networks.
Specifically, it allows Twitter and Facebook (and others?) to create "cards" and previews to show when someone posts the petition's link on social network. Instead of just showing the link.

It makes the post way more attractive because of the title/small description/image.

For instance this link https://petition.antipub.org/petition/org/rap-paris/stop-a-lecran-de-800-m2-a-boulogne-billancourt posted on social network will generate a card a bit like this:

You can play with the validator: https://cards-dev.twitter.com/validator

• The only option in email setups helps to show the organization email in the confirmation emails sent, and if some signatory wants to reply to this email it will go to the organization's mailbox.

• Newsletter setup is to setup how the petition is linked to a newsletter, which allows to automatically subscribe those who check the checkbox to some mailing list.

If you have questions don't hesitate :)

[fallen]

Hey @martinlehoux
I hope you are well and had nice holidays!
I'm pinging you here because this is the last item flagged for v2.3.
Do you have some piece of code (even if Work-In-Progress) to share as PR?
That could be a basis to improve or comment on :)

[martinlehoux]

Hey there !
It looks bad from my side ... I remember I had done a few things, but I changed my laptop and it doesn't seem I pushed anything on the repo regarding this issue...
When is v2.3 expected to be released ?

[fallen]

No hard deadline really, I was just thinking "let's do a release once last item is done".
It just happens that this is the last item targeted for v2.3 ^^