who makes up your audience
while your designer is more likely to care heaps about who is using the site, your WordPress developer can take this information to a more technical side of building a site.
for example, if your audience is primarily 20-somethings, they will use a different browser than an audience of folks in their 70s.
armed with the information, your developer could also suggest integrations that would not only benefit your site visitors, but you as well.
speaking of integrations…
what integrations are required
it is mission critical that you clearly communicate your tech requirements to your developer before they start coding the site.
this can be things like “I use Infusionsoft” or “we are going to use pop-ups on almost every page.”
as long as your developer knows what to plan for, everyone will be spared a lot of time troubleshooting issues when features + functions are added at the eleventh hour.
where you are most concerned
maybe you aren’t the least bit worried about your new site, which is awesome! kudos to your team for getting you there.
if there is something leaving you with the nervous sweats, even if it doesn’t seem like a huge concern, tell your developer at the start.
when i’m setting up a new project + i hear that my client is nervous about how the forms will work, or if leaving a comment will be easy as pie, i factor that in to my process. how so? i tend to start with the point of concern.
that way i am able to calm nerves well in advance so they don’t eat away at my client. if your developer can do the same, you get to feel that worry lifted from your mind + be less distracted heading into your new site launch.
when your team needs access
not every project takes a village to set up. but if you have a team of individuals running your online business, let your WordPress developer know when those team members need access before coding starts.
let’s say the Infusionsoft expert you adore needs to check forms on the new site, but your developer didn’t know. they might save those forms for the last step the day before launching…when your expert is unavailable to help. yikes!
send over a list of email addresses + dates of any team members that need access before the launch date. it might be a very short list, and that’s ok! your developer can then create the necessary accounts + ensure the areas your team is checking on are ready for review.
why you’re launching on the date you picked
odds are you have your launch schedule mapped out — or at least the date you want to throw your online party. why did you pick that date?
if we (as online business owners) are being honest with ourselves, 90% of our launch dates are picked arbitrarily.
there’s no shame in that game. however, it’s important to note when a launch date is arbitrary versus picking a date that falls 3 days before you are set to be interviewed on The Today Show. an event that could send hundreds of thousands of site visitors your way (on a single day) is important for your developer to prepare for.
plus, if your launch date is arbitrary, your developer knows that they might be able to launch in advance if they finish early OR they could spend an extra day really nailing the functionality you requested before launching.
how many pages you have
is your designer designing a layout for every page you need set up? i’m guessing not. imagine them handing the files off to the developer + your dev getting to work on the site. only you know how many pages are being missed in this scenario.
simply listing out your pages in an outline can set your developer up for knowing how all pages are connected + what needs to be created before your new site goes live.
you can go a step further by providing them with a document of the page content for each page on your site — since having content before development starts is always a great idea.
i’m currently in the process of revamping the tiny blue orange site + wanted to share behind the peel! you can follow along on instagram as i post new stories when i work on the updated site.