Next Step
- Product Team & IT to work on the technical built-up for the site
- At-Large staff & community to develop content strategy and curate written content
- We may reuse some of the existing content, but will need to rewrite and create other content
- At-Large community need to take ownership of the site & get more community members involved
- The Website Revamp Taskforce will lay the foundation for the content development phase:
- Involve core communications staff
- Develop two types of outlines
- Broader outline that covers topics of each page
- Detailed outline that describes each individual topic
- Develop guidelines and templates for each individual topic
- Create example pages
- Critique existing content
- Form focused and selected editorial working group consisted of community members under the guidance of ICANN Comms Dept
- Finished product to be edited and polished by ICANN Comms Dept
- Launch beta site during ICANN 52 and give ample time to receive community feedback
Potential Workload
This table illustrates the potential workload for developing written content for the revamped At-Large website. The pages highlighted in yellow have most of the written work to do.
| Page Title | Type of Content | Approximate Length |
|---|---|---|
| Homepage | Hero Text | 1 - 2 sentences that reiterate the mission of At-Large in a catchy manner |
| "Get Started" Buttons | 1 short phrase that point newcomers to each must-read page | |
| Section Introduction | 1 short phrase that introduces each section/row on the page; the sections include Policy Advice, Regional Activities, Outreach Activities, Capacity Building, Calendar, and Social Media | |
| Topics | Page Introduction | 1 paragraph (3-4 sentences) that introduces visitors to the policy topics matter to end-users and important to At-Large |
| Section Introduction | 1-2 sentences that gives a helicopter view of each policy topic and prompts visitors to 'read more' | |
| Topic Details | Topic Background | Several paragraphs that explains the policy topic in a beginner friendly manner, |
| (may need to develop 10-15 topic details pages) | Concrete Example | 1-2 paragraphs, preferably info-graphic that gives newcomers a concrete understanding about this policy topic |
| Topic History | Several paragraphs that delineates the evolvement of this policy topic over time and highlights key milestones related to this topic | |
| End-User Interests | Several paragraphs that describes why end-users should care about this policy topic | |
| At-Large Impact | Several paragraphs that tells a story about how At-Large has influenced this policy topic and advocated for end-user interests | |
| Policy Advice | Page Introduction | 1-2 paragraphs that help visitors understand what this page is all about and how they can conduct facet search to find ALAC Statements |
| Taxonomy List | Several taxonomy lists that are organized in logical and comprehensive manner to help visitors conduct research on ALAC Statements effectively | |
| Policy Advice Detail | ||
| About | ICANN Structures & At-Large | 250-500 words |
| Our Mission | 250-500 words | |
| At-Large History | 250-500 words | |