Below are non-negotiable processes that help us deliver consistent, high-quality work. Please follow these steps for every task to ensure accuracy, performance, and professionalism.
- Check your work…then check it again
- Thorough self-review prevents avoidable issues and ensures the highest standard of delivery.
- All development work must look and function perfectly on mobile, tablet, and desktop.
- Use your browser inspect tool to check mobile, tablet and desktop resolutions. Better still, go into responsive mode resize window manually to go from desktop resolution to mobile, and make sure everything breaks down gracefully.
- Clear all caches (Cloudflare, RunCloud, Rocket, etc.) before reviewing changes.
- Use incognito mode and make sure you are logged out of WordPress to test as a fresh visitor.
- Never leave work partially completed on live production. If you need more time, create a staging URL to refine your updates.
- Review Tasks & Instructions Thoroughly
- Read every task carefully…twice.
- Make sure you fully understand the instructions, requirements, and expected outcomes before beginning.
- If anything is unclear, ask questions early to avoid misunderstandings or missed details.
- Optimize images
- Resize images to the largest size they will appear on the frontend e.g. if on the front end the image displayed will be 500×500, and the source image is 2500×3000, we need to crop and resize the image to 500×500 before uploading.
- Compress images using tools like Compress or Die and save them in .webp format. Other formats are fine for specific uses, like .svg for logos etc.
- Rename image files clearly, describe the image and include keywords naturally. Keep it to a max of 3 to 5 words, with hyphens, and describe the photo and try to add a keyword naturally. e.g. if we have an image of a dog on artificial grass, we might use an example similar to the below:
- dog-running-artificial-grass.webp
- dog-on-artificial-turf.webp
- german-sheppered-synthetic-grass.webp
- Webform updates
- If we change anything on a webform, or anything that may affect a webform, we must send test through the webform and make sure we get a reply.
- If it’s a client that is using WhatConverts or any other tracking script, we need to make sure that those leads are still getting received in the tracking software. Send a test to confirm.