-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow supporting organisations/people to show support by adding their names to reform area pages #135
Comments
To make contact, find out more, or express support for one or more areas that the government should take action on, and include in the first Australian Open Government Partnership National Action Plan:
Not all members (3) will be available the whole time. Is there another way we can facilitate this (in the short term).
|
One way to do this initially could be: Add a button to the reform area page, “Add your support”. That links to Google Form with Name, email, and organisation name if it's on behalf of an organisation. We can ask them to email us their logo then. There’s probably petition WordPress plugins that might make the experience more seamless for people, but this is an initial pass to get started. |
It would be nice to have a way for people to add an image. |
When people sign up we need a way to continue to contact them about the OGP and the network. |
We now have this in action on this page https://opengovernment.org.au/the-case-for-action-on-a-national-integrity-framework/
|
The form here https://drive.google.com/drive/u/0/folders/0B67Y_SEZzwGvUW42TXBBNk1NXzA can be copied and adapted for each reform area. When you make a new page for a reform area, you can copy the markup at the bottom of this page https://opengovernment.org.au/the-case-for-action-on-a-national-integrity-framework/ and change the link to your new form. |
When the "case for action on reform on X" open letters are published, potential supporting organisations need a way to add their name to that issue. Also see #134
The text was updated successfully, but these errors were encountered: