It’s a popular game to play when sitting around a bonfire while camping: Two Truths and a Lie.
Never played? Here’s how it works: each participant takes turns telling two truths and a lie about themselves. The other’s have to guess which is which.
When it comes to discussions about Drupal site audits, I oftentimes feel like I’m in the middle of a game. Expectations about what is and isn't included varies, as each agency conducting them does them a little differently. So when we talk about site audits, what exactly are we referring to? See if you can pick out the truths… and the lie.
1. Site Audits Uncover Client Pain Points
When a potential client schedules a meeting about a project, they come to the table with a long list of frustrations they have with their current site. Discussing these pain points as a part of the site audit is essential. This conversation helps us understand what is and isn’t working for your team, and what we can do to make sure everything is properly fixed.
2. Site Audits Bring to Life Design Discussions
During a Site Audit we open up the communication channels regarding site design. We assess your current branding and style guide and make recommendations on how to better tell your story visually.
3. Site Audits Pave the Path for Recommendations
Site Audits are an imperative part of a website project because they uncover what elements of a website just need to be revamped and what elements need to be completely redesigned.
So which of these isn’t part of our Drupal site audit process?
If you guessed #2, you win this round. During site audits we don’t talk about your designs or branding. These discussions come later in the process, after the audit is complete and we've determined what the scope of your project looks like.
The purpose of site audits is to investigate what is happening on a site from a technical standpoint. Our findings can be consequential, such as discovering that a theme layer is broken, or less pressing, like uncovering that programs need to be updated.
Here is an example list of deliverables you can expect to receive from an audit:
- Document list of enabled Drupal modules and functionality
- Documentation of Drupal roles and permissions
- List of content types and usage
- Identification of Drupal theming used
- Documented list of customized areas with the Drupal site
- Recommend additional Drupal modules, if any
- Recommend Drupal performance changes, if any
If you’re looking to build a better website that eases frustrations with your current iteration, start your project with a site audit.
- Best Practices for Modern Website Navigation
- First Impressions of Open Atrium 2.0
- 6 Examples of Strong Homepage SEO Optimization
- What To Do When It All Goes Wrong: Using the Try/Catch Structure in Drupal Coding
- How Internal Site Search Works
- Setting Up Postfix to Work with MAMP
- UX 101: Tips for Maximizing Your Homepage's Usability
- Environment Variables, Drush and Settings.php
- 4 Missing Modules for New Drupal Developers
- Amazon RDS Cloudwatch Statistics in Munin