As with any website project, you will need to first think about your website architecture and the ways people are going to be able to discover your content.

If you haven't already done so, make sure you've read our article choose a template before you start to map your site because EngagementHQ utilizes a fixed set of homepage templates, project page layouts, and tools. It's quick and easy to plan for your site architecture by drawing a wireframe of your homepage.

How do I wireframe?

Start with your chosen template for the homepage and visualize the content for your site.

On a piece of paper draw out the wireframe for your selected homepage and start to mark in the projects and pages you would like to feature.

The images below show two different wireframes for each of our templates and you should use these to draw out a plan for your site. You can find your project wireframe by visiting the Appearance > Homepage Editor section of your EngagementHQ site.

Use these wireframes to guide the building of your site.

Things to consider

It's best to think holistically about your projects when trying to decide how best to map your site. Below are some things to consider when you are drawing out your site plan.

  • Your site header/footer should include static pages describing your site and detail information on how to get into contact with you.

  • Think about how you want to categorize your collection of projects using your header/footer.

  • Use your project cards to link to either a project page, hub, static page or directly to an engagement activity/tool.

  • Think about the supporting widget content that will appear on your homepage. Are these Faq's, documents, images, timelines? What pages will you put this information on? 

Mapping your site makes it easier to share site plans with your project teams and also cuts down the time required to build your site. It will also help you determine how many images you need for your initial site launch.

What's Next?

Learn about how to get the right sized images for your site.

Did this answer your question?