D3D Website: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
=Requirements v2=
=Requirements v2=
Rationale: the focus of the site should be the Distributive Enterprise message + Extreme Manufacturing + Construction Set + Open Source Solar Microfactory vision. Should probably have my TED talk somewhere. As the workshops gain traction, they will be covered by media outlets, which should be notes with As seen on... listing all the venues.
Rationale: the focus of the site should be the Distributive Enterprise message + Extreme Manufacturing + Construction Set + Open Source Solar Microfactory vision. Should probably have my TED talk somewhere. As the workshops gain traction, they will be covered by media outlets, which should be notes with As seen on... listing all the venues.
==Details==
*Use a map like Prusa i3 uses for map of their customers - [http://shop.prusa3d.com/en/3d-printers/59-original-prusa-i3-mk2-kit.html]
==Server, Wordpress, Federation==
==Server, Wordpress, Federation==
#Documentation of Wordpress install on Centos Server, including documentation of directory structure
#Documentation of Wordpress install on Centos Server, including documentation of directory structure

Revision as of 05:21, 16 July 2017

Requirements v2

Rationale: the focus of the site should be the Distributive Enterprise message + Extreme Manufacturing + Construction Set + Open Source Solar Microfactory vision. Should probably have my TED talk somewhere. As the workshops gain traction, they will be covered by media outlets, which should be notes with As seen on... listing all the venues.

Details

  • Use a map like Prusa i3 uses for map of their customers - [1]

Server, Wordpress, Federation

  1. Documentation of Wordpress install on Centos Server, including documentation of directory structure
  2. Documentation of Wordpress theme and consistency with OSE Specifications: scalability, modularity, easy edit, modification. That is - design with website modification in mind
  3. Documentation of how to modify the different parts of the website
  4. Embed code or another mechanism for federating websites (ie, main metrics feed between websites - such as number of machines built feed from other D3D enterprise websites
  5. Fully open source code hosted on Github
  6. Site is scalable to 100 workshops per month, and thousands of Builds featured (see below)

General

The website should be as easy as possibly to maintain/modify - consistent with our Construction Set approach.

Content

  1. Front page: # of machines built and workshops held should be prominent. Signup for the next workshop/s should be clear. Flashy pix etc. OSE FB page should be linked from front page. Donate to OSE. Sign up as a True Fan to get 25% discount from Build Workshops. Squeeze page to capture email to provide workshop updates.
  2. Main 5 content areas: Develop - Workshops - Builds - Enterprise - Shop.
  3. Develop is join the Development Team - THE place where we send people to learn about becoming an OSE Developer. Embedded Team Graph, Developer Profiles should be included. It would be nice to have a world map that shows the locations of our Developers.
  4. Workshops is registration for the Workshops. This should also have downloadable e-Book which is the manual that people who attend the workshop use to build the 3D printer. This means this e-Book should include up to Language Agnostic instructionals. I would also love to add a map of worldwide locations that have held D3D workshops - but that could be added later. We should also have a form where people request a workshop in their location. If enough people do this - we declare that we will host a workshop near that location. This would be a great way to help market. This feature should put people on a map - so you can see interest clusters easily - and possibly set our workshop schedule accordingly.
  5. Builds should be a gallery of all people who do various replications and derivatives. Automatic submission form with specific requirements for submitting (picture, location (to be put on a map), link to their blog etc, some info about the machine features - like which specific features were used in the build (size, extruder type, frame size, build platform size, etc). We want to think about structuring the template for a gallery entry nicely - so it's informative and meaningful - and would encourage sharing of design files if available. Their image size should be reduced so we don't get into memory issues once many people start uploading their builds... The Builds Page should have a 3DPCS design Guide to help people create derivative machines. Builds should also include a community discussion for support. This could be a D3D discussion group on the OSE Network, and a link to the OSE Workshops FB page.
  6. Enterprise - Focuses on communicating the vision of Distributive Enterprise - ie, that we want to collaborate on creating billion dollar enterprises (ie, the cumulative revenue of open source products from all the players is billions, like for example the market size of cordless drills is over a billion in the USA alone). That means - OSE captures some value - but most value is over time captured by many other entrepreneurs - where we all develop the products and their marketing collaboratively... Page ncludes and e-Book for how to run a 3D Printer Construction Set Workshop. It should include an e-Book for setting up a print cluster, with a Gallery of curated print files for high value products, or products otherwise useful to the 3DPCS + GVCS. Such as parts for D3D, the rainwater system leaf eliminator, rubber tracks, etc. It should be a 'Hall of Fame' of useful printed parts, and later we may create incentive competitions giving rewards for the best 3D print files for product - such as the cordless drill. This can evolve to an automated 3D printing service - where the small industrial robot picks parts off the build platform - but for now, we don't have to worry about that. The parts that people could buy would only be the parts that we feature - as it is frequently challenging to get something to print correctly without prior experience with that part. Using only our parts assures we have the experience.
  7. Shop - this should be swag and kits. Swag= OSE Sticker, D3D sticker, D3D T-shirt, OSE T-shirt, OSE Developer T-shirt, on-demand printed books for all the e-Books mentioned above. Kits= first, a BOM with recommended links (for OSE, we can include Amazon Smile - which gives a small kickback to OSE for people buying through the Amazon Smile link). Later once we set it up we can actually ship ourselves. Note that all of the Shop is first automatic fulfillment. We are not shipping anything ourselves - we outsource that to various on-demand printing/t-shirt/sticker services. That means the price will be higher, but we just don't have the time to run a store, as our focus is education and R&D.

Design Doc v1

edit

More

First image:



  • I like the clarity on metrics. I would also add Total Value of Enterprise Created. Please prioritize the devs pipeline and recuiting.