search

V-Squared / V-Squared.github.io

Initiative for Modular and Upgradable Mini and All-In-One PC. Standards — Know How — Blueprints — Trailblazer Products
http://v-squared.github.io/
Other
2 stars 1 forks source link

Alternative method to creating references #206

Open bcaswelch opened 8 years ago

bcaswelch commented 8 years ago

References for Competing Products

Currently, the way we are showing the specs of the machines is stitching together several pages of technical specs. This is detailed but very lengthy.

Alternative Reference Sheet

Pretty much (I'll have to double check this) every computer buy page has a summary that shows all of the different components you chose. Lets just take a screen capture of this instead of 5 pages of options. This shows the information needed to prove we aren't lying in the comparison and its much less intrusive when people want to look at it.

Heres an example of what it would look like:

imacreference

VillageHubertChen commented 8 years ago

@bcaswelch

Thinking about a cleaner presentation to the customer is always good.

  1. I am not exactly sure however where you are want to use this?
    1. If this is for the Workstation comparison page, then we already use a table with about the same amount of specs as your example. How is what we have longer than what your snap shot shows?
    2. If this is for the Configs page. Can you hold off on it. I have a completely different and new approach on how to do configs. I want to share with you after the Comparison Pages are completely finished.
  2. Shortening Spec Comparison Tables in Comparison Reviews
    • Please note that current tables contain:
      • Spec Comparison AND
      • Usability Comparison
    • Once you split the Article into the three main chapters ...
      1. Spec Comparison
      2. Price Comparison
      3. Usability Comparison
      4. ... then each table will be much shorter and it is easy to focus on the essential.

Note: I moved this issue it into the developing column, as you are developing on it right now. Spring Now is short for Backlog of Sprint that we are developing now.

P.S. I like the formatting of your example very much. We should keep this in mind when we design the product pages :-)

P.P.S. I read this whole thing again to think it over. What confusing me the most is the title: "References for Competing Products". Right now we have tow levels that would fit this description:

  1. Spec Comparison Table (Need to be split into spec and usability comparison tables)
  2. Snap shot of configuration of the respective configurator