As the brief was so varied, I had to research existing page design to understand the scope of possibilities for the page. To begin the process by creating a content list to include in the template, then sketching lowfy wireframe designs trying to consider the best way of organising the information, to be informative and purposeful. I wanted to utilise the boundary free scope of the brief to explore more expressive design choices, through copy size and colour.

When mocking up the pages digitally I took layout inspiration from my sketches, transferring them to Photoshop. Taking care to group and name my layer’s efficiently, as the build team would use the file as reference. I wanted to keep a simple layout which would be intuitive for users.

​

In order to decrease site-drop-off, I wanted to include a messaging module to enable users to email without leaving the site. I discussed functionality capabilities with the platform specialist, to gain awareness of the available capabilities, to aid my design choices. I decided to prioritise this as the first module on the page.

The second module has the brands logo next to their email address, for people who want the option to manually email the company. The third module uses a pattern that was reutilised from another page on site, to keep consistency through the pages. Here, I included copy that I’d written as a call to action to give the suggestion for people to write into the company.

​

When sending the spec over to build I created breakpoints for both mobile and desktop, as well as written descriptions of the module feedback functionality. Specifically, the customer feedback after they click the CTA and send a message through the messaging board, so they know their message was successful. I sent this over with the Photoshop file containing the designs and content. I sent over a PSD with the exportable files, and the build team were able to generate the webpage.