Website Layout

Matt MacDougall 2016-03-18

Thanks guys, this is a good list of overall ideas.  What are your thoughts on an organizational structure for version 1 of the website? 

Is this all on one page?  If not, what's the first level of navigation?  and what are your thoguhts on sub-navigation that may be under that first level?

Vince Malfeo (Unlicensed) 2016-03-18

Matt MacDougall

We were thinking a static front page that basically populated when you scrolled down. The very bottom being a "Purchase" or "Add to Cart" option. Perhaps even a learn more that brings you to a product page.

If we did it this way, would it be possible to have an expanding navigation bar that is mostly hidden until you click on it? If not, a regular navigation bar would suffice.

On the static front page we would have everything on there that helps with the conversion of Rocket Shopping Feeds.

Some ideas would include:

• Recommended by Google
• User Reviews
• Testimonials from respected people in the industry
• Rewards Badges/Explain Magento Certified Devs on Board

Just any selling point that would help convert.

I think the main menu should be simple, maybe a total of 5-7 links, with the potential of a secondary navigation under them. (The other possibly is using anchor links in the menu navigation to point directly to the sections on the front static page)

Sample Menu:

Home(unless it takes up too much real estate) | About | Recommended by Google | FAQ's | Support | Demo

I think the more simple this all looks, the easier it will be to draw everyone's attention to the sales pitch.

If we want to go with a sub-navigation, we could add things like Videos, How-To, Quick Guides under the "Support" Parent.

 

If we are able to add tons of valuable content, but position the home page and navigation in a way where it doesn't make it seem complicated, I believe that would be our best bet.

Matt MacDougall 2016-03-18

Sounds great.  I think Jakub Kulig (Unlicensed) should have some info to go on to start thinking about the skeleton of the site.

The sooner Jakub Kulig (Unlicensed) has actual content to work with, the easier it will be as he builds out pages.  Vince Malfeo (Unlicensed) and Corey Schmitz (Unlicensed) can you guys start fleshing out content for these pages?  You will have a CMS so you can always make edits later.

 

Matt MacDougall 2016-03-18

Corey Schmitz (Unlicensed) Vince Malfeo (Unlicensed) I added some blank pages under Site Content where you can start dropping content.

Corey Schmitz (Unlicensed) 2016-03-19

Matt MacDougall I talked with Vince Malfeo (Unlicensed) and we are discussing ideas for the site content.  Should have some things added on Monday or Tuesday.

Dorin Mirulescu 2016-03-21

I just remember that one of the selling points for this extension is the openness of extension code, customers can modify it, and I'm thinking to add some instructions on how to modify it on Rocket Shopping Feeds.

Also another selling point could be that it's a one time purchase. We're not processing any customer data, nor functioning of the extension is dependent on our services. On the other hand we do want to price it more as a hidden saas, because of the ongoing support customers need. We don't have tools to enforce people buying support before reaching out to us, but we'll be sending out email notification for expired support. Maybe the site should also better set expectations and lead to customers make informed pricing decisions.

Matt MacDougall I let you decide if any of this should do with this site. 

Jakub Kulig (Unlicensed) 2016-03-22

Matt MacDougall Corey Schmitz (Unlicensed) Vince Malfeo (Unlicensed) My advice is to contain all the sales pitch related information on the homepage rather than break it into multiple pages. We should also be concise while presenting marketing information so as try not to overwhelm the user with content. Grav CMS allows us design and build modular pages, where a single page consists of multiple sections, that can be easily managed. That way we can add/remove sections as we see fit and even reuse them on multiple pages.

Sample homepage structure:

• product introduction section (including short description, main CTA), 
• list of key features, 
• Recommended by Google + badges, 
• support overview with link to documentation/tutorials, 
• user reviews or testimonials

Additional pages (About/Features, Support, FAQ, Demo) would then contain more detailed product information including screenshots, video tutorials, premium support options etc. 

 

Dorin Mirulescu 2016-03-23

+1

Jakub Kulig (Unlicensed) 2016-03-30

Matt MacDougall Corey Schmitz (Unlicensed) Vince Malfeo (Unlicensed) Please review my proposed website structure above and update as you see fit. I'll start creating the skeleton of the site using blank pages/placeholders for now and I'll adjust once we have the final structure.