Tony J. Marvin and I have known each other for a number of years and have worked a couple of small projects together in the past. He is an excellent storyteller and well read in many subjects! Many of his friends have encouraged him to explore this skill and a few years back, he took the steps to self-publish his first novel, “Betrayal: Darkness Engulfs the Knight.” Knowing my background as a graphic artist and book designer, Tony initially asked me to illustrate his first book cover and to illustrate some of the characters in the novel. As the project came closer to completion, he realized that he needed a larger presence online from which to sell the book. I was asked to build his author website.
His goals were to have a platform to not only talk about and sell his novels, but also to explore his hobby in blacksmithing. Blacksmithing was intended to be a sister subject to the Knights Templar chronicles, providing a hands on experience to learn about the time period by building weapon and armor that would have been employed.
I took this opportunity to put a new skill that I had been learning to the test. My plan was to streamline users from introduction, to novel brief, to point-of-sale. Each page achieves this through keyword links that lead to the Amazon sale or by offering a call-to-action at the end of each page. This assures that a user will never have to navigate more than 1-2 pages before having the option to outlink to the sale, which hopefully cuts down on bounce rate!
The website was created with a mobile-first approach. Meaning that I designed the layout to work specifically with small devices, such as cell-phones, first, by using media-queries and setting the viewport to device width. Using this method, as each query stepped up in device size, I was able to make minor tweaks which would adjust the layout and function of the design which optimized the experience for those specific users.
Tablet Portrait Screen showing touch drop-menu
A lot was learned after the first generation of the build. Originally, I had created a separate CSS document for each of the pages. Talk about an organization nightmare! With better planning and more experience, I would have been better off to use less class attributes and more parent/child properties. By the second (current) generation of the site, I had re-organized the CSS documents into one master document and cut back on redundancies.