Project Microsite Design for Land Use and Development

A project microsite is a small, self-contained website built around one proposal: a rezoning, a solar farm, a transit corridor, a brownfield cleanup. Good project microsite design starts with decisions, not graphics. It settles who the site is for, the three things those people must know or do, and how residents can respond, and only then moves to layout and style. Done this way, the site becomes the reference point for neighbors, officials and reporters for the life of the project.
This guide walks through those decisions for the people who commission these sites: local government staff, developers, environmental groups, business owners and nonprofit leaders.
TL;DR
A project microsite works best when the project is time-bound, there is one clear call to action, and the story needs more room than a page on your main site can give it.
Define the primary purpose, the three things visitors should know or do, and the primary and secondary audiences before any design work begins.
Put the essentials first, publish a timeline, meeting dates and a simple way to comment, and keep technical documents behind plain-language summaries.
Design mobile-first, in plain language, with translations where your community needs them. In one California pilot, 81% of comments came from phones.
Name an owner, plan the closing date, and track reach and actions so the site keeps earning its place.
Table of Contents
What a project microsite is and when it earns its place
A microsite has its own address, navigation, voice and measurement, and it is focused on one campaign, audience or moment. It differs from a landing page, which is a single page with one action, and from a section of your main website, where the project competes for space with your About page, news and unrelated programs. A project microsite typically runs from about two to five pages, which keeps it focused enough for a visitor to grasp the proposal in a few minutes.
Three conditions make a microsite the right tool:
The work has a defined window. A permitting process, a hearing schedule or a construction phase has a beginning and an end.
There is a specific action you want. Attend a hearing, submit a comment, sign up for updates, or show support.
The story needs its own frame. A proposal with local history, environmental questions and neighborhood effects rarely fits inside a generic organization site.
Public agencies already treat this as good practice. The City of San Diego’s engagement guide directs that external-facing city projects keep a dedicated webpage for the entire duration of the project, using it to inform people across a large area, give context, offer ways to participate, and post adopted documents and next steps afterward. If a city expects that of its own projects, residents will expect it of yours.
A microsite does not replace conversation. It gives your community engagement work a stable home so that every flyer, mailer, social post and meeting invitation points to the same accurate source. For the wider plan the site supports, see our community engagement plan with a 90-day starter.
Start with purpose, audience and three priorities
Most weak microsites fail before design begins, because nobody agreed on what the site is for. The UN Web Guidelines offer a planning template that fits this job well. It asks teams to describe the project, define the site’s primary purpose, list the three things users should know or do in priority order, and name primary and secondary audiences. The same page notes that planning also covers preparing content and writing a budget and timetable, and it reminds planners that the average visitor spends only about two minutes on a site.
Translate that to a land use proposal:
Primary purpose. For example: help residents understand the proposed project and take part in the review before the planning commission vote.
Three priorities, in order. What is being proposed and where; how and when to give input; what happens next.
Primary audience. Neighbors within the notification area, often a mix of homeowners, renters and small business owners.
Secondary audiences. Elected officials and staff, local reporters, advocacy groups, and potential supporters who may not live nearby.
The order matters. If a visitor leaves after two minutes, they should leave knowing what the project is and how to respond. Everything else, including the environmental studies, site plans and traffic analyses, supports those answers rather than leading them.
Also decide how the site will be presented. Organizations that sponsor a microsite should say so plainly, and visitors should never have to guess who is behind the proposal. Trust grows when the sponsor is visible and the information is honest about what is decided and what is still open.
Structure the site so people understand the proposal fast
A small site still needs a clear hierarchy. The Beeck Center at Georgetown’s research on accessible content recommends organizing content so the most important information is the easiest to find. For a project microsite, that suggests a simple structure:
Page | What it answers | Typical contents |
Home | What is this and what can I do? | One-paragraph summary, map or rendering, primary call to action, next date |
About the project | What exactly is proposed? | Location, scale, benefits, changes from earlier versions, frequently asked questions |
Timeline and meetings | When can I weigh in? | Milestones, hearing dates and locations, how to attend or watch |
Documents | Where is the detail? | Fact sheets, draft plans, studies, each with a one-line plain-language description |
Get involved | How do I respond? | Comment form or input tool, email sign-up, contact details |
Five pages is a ceiling for most projects, not a target. A small zoning amendment may need three. A multi-year infrastructure program may need a few more, but its home page still has to do the same job.
Two habits keep the structure honest. First, put participation details in one place, so a resident can find the meeting schedule, the comment form and the contact information without clicking through several pages. Second, keep a visible “what we heard and what changed” area once feedback starts arriving. Residents who see their input reflected are more likely to keep engaging, and it is the clearest signal that the process is more than a notification exercise. Our piece on why permitting outreach must do more than notify explains how to build that loop.
Content and features that inform and invite feedback
The San Diego guide gives a practical inventory of what a project page should carry during the engagement period. It lists a public engagement timeline, fact sheets and draft documents, event and hearing dates and locations, a public input tool where applicable, and an embedded email sign-up form. It also advises posting documents as compressed PDFs rather than native Word or PowerPoint files, so residents can open them with free software and on slower connections.

Choosing an input tool
A comment form is the minimum. If you want richer input, public participation platforms support several question types. The District of Columbia’s PublicInput user guide documents rank options, matrix questions, consensus questions, budget sliders, open-ended comments and interactive map responses. Match the format to the decision:
Open comments suit early scoping, when you need to learn what people worry about.
Ranking or budget sliders suit trade-offs, such as which park amenities to fund first.
Map-based responses suit questions about place: where traffic backs up, which routes children walk, where a buffer would help.
Simple sign-up forms suit projects with a long timeline, where the goal is keeping people informed.
Because it is easy to over-build, ask of every feature: does it help a resident understand the proposal or respond to it? If not, leave it out.
Documents without the wall of text
Technical reports are necessary and rarely readable. Pair each with a short summary stating what it studied, what it found and where to read more. Visitors who want the full study can reach it, and visitors who need a clear answer are not forced through two hundred pages.
Design for phones, plain language and trust
The strongest evidence for mobile-first design comes from a public-sector pilot. California’s Office of Data and Innovation redesigned a community update for a toxic substance cleanup and built a fast-loading, mobile-first project webpage, with a QR code on the printed update. According to the office, the pilot more than quadrupled the average public comment rate, with 81% of comments made on mobile devices and 68% in Spanish. The same project used plain language to lower the reading level and tested its templates with the public to confirm the comment process was easy.
Take these lessons into any project microsite:
Build for the phone first. Use large touch targets, short pages and compressed images, then check how the desktop version scales up.
Write plainly. The Beeck Center recommends plain language at a reading level such as fifth grade, and advises writing the plain-language English first because it translates better.
Choose languages from data. The same research suggests using U.S. Census geographic data, plus underrepresented populations, to decide which languages to offer.
Use visuals that clarify. San Diego’s guide advises graphics, images, icons and simple words, and checking that mobile devices display the page cohesively.
Bridge print and web. A QR code on a mailer or yard sign sends people straight to the page.
Branding that builds trust
A project site that looks like a sales brochure invites suspicion. Residents want to see the place, the people affected and the facts. Use local photography, a restrained palette and a tone that informs rather than promotes. Show the sponsor clearly, but let the project and the community take center stage. Ideas about user-generated content and trust apply here too: when residents see real community voices, such as quoted questions answered on the page or photographs of local meetings, the site feels like a shared resource and not a one-way announcement.
For more on earning credibility with neighbors, read how to build neighborhood trust for a new development project.
Build, launch and maintain: a working sequence
The San Diego guide splits the work into before, during and after. Before launch, it calls for writing in the city’s style guide, selecting images, laying out content, including search terms, and getting review from a public information officer. During the project, teams update information, timelines, documents, events, input tools and sign-up forms. Afterward, they post next steps, close sign-up forms and archive old pages under public records standards.
Adapted for any sponsor, the sequence looks like this:
Agree on goals and owners. Amnesty International’s microsite guidelines require clear goals, key performance indicators, an evaluation process, a promotional plan, a senior project owner and a named person to monitor and update the site. Borrow that discipline.
Draft content in plain language. Write the summary, project description, frequently asked questions and meeting information first. Have someone outside the project read it.
Test with real residents. California’s team tested its templates with the public before relying on them. A few short sessions will reveal confusing labels and broken forms.
Build and check accessibility. Confirm that pages read well on phones, that documents open without special software, and that forms work with assistive technology.
Launch with a promotion plan. A microsite nobody knows about does nothing. Tie the address to mailers, social posts, newsletters, community meetings and press outreach.
Update on a schedule. Assign one person to post new dates, documents and responses. A stale timeline damages credibility faster than having no site.
Plan the close. Decide when the site will move to a “what happened and what’s next” state, who archives it and where adopted documents will live.
California’s team found the plain-language template cut word count by 56%, and the agency later trained over 50 public participation specialists on the approach. Smaller teams do not need that scale, but the principle holds: make the process repeatable so each new project starts with a tested model.
Measure whether it is reaching people
Traffic alone says little. The IMPACT guide for evaluating community information projects separates reach metrics, such as visits per week and new versus returning visitors, from engagement metrics, such as page views per visit, bounce rate, time on site and the percentage of visits that complete a specific action. It also recommends using goal and funnel tracking in your analytics tool to measure conversions.
For a project microsite, the actions worth tracking are concrete: comment submissions, email sign-ups, hearing-information views and clicks from a printed QR code. Pair them with a simple habit the same guide describes: mark your traffic graph with key events such as mailers, newsletters and press coverage, then see which ones produced spikes. That tells you where the next outreach dollar should go.
Also watch who is responding. If comments come mostly from one neighborhood or one language group, your outreach has a gap that no design change will fix. Combine analytics with community feedback, including at meetings and through direct conversation, and adjust tactics as you learn. Our guide to infrastructure public outreach shows how that feedback loop fits a larger framework.
Our perspective
A project microsite is a strong tool, but it is one instrument in a campaign. The proposals that earn public support are the ones where the website, the meetings, the media coverage and the conversations at the kitchen table all tell the same, honest story. That is why we approach land use work in a campaign style. We assess the community landscape first, set priorities, and tailor the plan to the specific project, whether it is a solar array, a rezoning or a stretch of new infrastructure. The microsite’s design follows from that assessment: who needs to be reached, what they care about, and what action we are asking them to take. We also believe tactics should be recalibrated continuously based on real-time community feedback. A site that is launched and left alone cannot do that. One that is updated, measured and connected to community relations, media relations and digital advocacy can. If you take one thing from this guide, let it be this: design for the resident who has two minutes and a phone. Everything else is built on serving that person well. Ignacio
Putting the site inside a larger strategy
AMAUTA Public Affairs works with developers, local governments, environmental organizations, business owners and nonprofits on land use, energy, infrastructure and commercial development projects. Our services include community relations, digital advocacy, media relations, coalition building, branding and marketing, stakeholder relations, permitting support, supporter turnout and campaign management, so the message on your project site is carried consistently across every channel your community uses.

If you are planning a project and want the public-facing side built around real community feedback, review our campaign management and related services or get connected with our team.
FAQ
How many pages should a project microsite have?
Most project microsites run from about two to five pages, built around a single issue. Choose the number by the decisions visitors need to make: understand the proposal, find dates, read documents and respond. If a page does not serve one of those, combine or remove it.
How long should a project microsite stay online?
Keep it available for the entire duration of the project, as the City of San Diego directs for its own projects. After the decision, post the outcome and next steps, close sign-up forms and archive the pages according to your records requirements. Plan that closing step from the start.
Should the sponsor be named on the site?
Yes. Visitors should be able to see who is behind the proposal. A neutral, community-forward look and tone helps, but the sponsor’s name and contact information should be easy to find so the site reads as transparent rather than hidden.
What should the main call to action be?
Choose one primary action that matches the stage of the project, such as submitting a comment before a hearing or signing up for updates. Place it where it is easy to find at the top of the page, not at the bottom or buried in extra text, and keep the wording short.
Sources
Recommended

Comments