Once you have finished populating your site, the next step is the quality assurance (QA) review.
Please review the list below to ensure your site is ready for launch. If so, notify your Customer Success Manager that you're ready to go live.
Please allow a three working day window between notifying your CSM and your actual go-live date - this allows us to complete our checks as well.
Avoid using jargon (like βmodal filtersβ) or acronyms - they make your content difficult to read and understand. If you must use acronyms, ensure the full meaning is spelled out too.
Too much text can make for an unpleasant experience that requires lots of scrolling for mobile users. Use the mobile preview to check the amount of text.
A mix of different question types helps to keep things interesting. Using images helps to add visual flair to your project. Also consider using tools such as accordions, page breaks or two column text to create more interesting layouts.
You must have permission to use any images that you upload to Commonplace - either by producing the image yourself, obtaining permission from the image's author, or by using royalty free images from sites like Unsplash. You may not use images you have found on Google Images, as these may be copyrighted.
Keep an eye out for placeholder images/text you may have missed when building your site.
Check your links to ensure they lead to the correct place.
A snappy title and an attractive, recognisable hero banner image grab a user's attention and make them more likely to read on.
A 'contact the team' section allows users to contact you directly with queries and concerns - you can populate it with an email address, phone number and/or social media links.
Tiles can be switched on or off on the home page - ensure that any tiles you want people to comment on are visible.
Milestones help your users understand the context behind your project - what's happened so far, what's happening now, and what will happen in the future.
Every organisation that will have access to the dashboard must be listed on the team page, in order to inform users who their data will be shared with.
This helps users understand who will have access to their data and how it will be used.
Demographic questions cannot be edited after launch.
For instance, questions such as ethnicity or disability should be marked as Special Category Data. For more information, click here.
Benchmark questions use options that align with ONS/Census data, allowing you to benchmark your project against local data and identify gaps in the community you've reached.
The preferences page allows users to opt in to various contact preferences. There are three default options - Project news, Comment replies and New Commonplaces in your area. Custom consents can also be added (such as a prize draw to incentivise users to comment).
Survey questions cannot be edited after launch.
Check out our best practices article to view some top tips for good survey design.
Remember, survey responses are public - so any personal information should be asked for in the demographics section instead. The only exception to this is Hidden Comments engagements.
Survey questions cannot be edited after launch.
The centroid and zoom level controls help guide your users towards commenting on the areas you're interested in feedback on. They can be set in map edit mode.
Boundaries and info points make your map more informative and engaging.
Alt text is an important part of making your site accessible for people with visual impairments.
Headings help create a hierarchy of information on your page, making it much easier to navigate using a screenreader.
Text within images cannot be read by a screen-reader, making it inaccessible. Make sure the text included in the image is written on the page too.
You can check contrast levels using this tool: https://webaim.org/resources/contrastchecker/.
Links should clearly state what should happen when you click them - e.g. βYou can also read our latest news updatesβ, rather than just βclick here to read our latest news updatesβ.
The interactive nature of maps means that they can't be operated using a screenreader. Instead, we advise creating an 'alternative map tile' including the same questions, but asking respondents to identify the location they're commenting on through a text field instead. This tile can be hidden so that it doesn't appear in your tile lists on the homepage or all tiles page.
These can be set via the branding page.
If you'd like to customise the text and image that appear when your project is shared on social media, send them to the support team.
If you're printing your URL on leaflets or signage, or creating QR codes that link to your URL, make sure you test the URL before finalising to avoid any potential issues.
Still unsure about anything? There's lots more information here on the Commonplace Help Centre - alternatively, contact the support team and we'll be happy to help π