Hey, I start a discussion here on the new bonsai.uno webpage.

Here is the structure suggested by Chris.

  1. Vision (short)
    1. Common ontology for LCA, MFA, and IE
    2. Open data pipeline
  2. By the community, for the community
    1. Getting started guide
      1. Basic technologies
        1. Contribute with data
        2. Build web apps
        3. Using the API
    2. GitHub projects repo
  3. Community management
  4. Data reconciliation
  5. NPO (BONSAI on-profit organization)
    1. Become a member
    2. Archive of official documents

Did i get the hierarchy right?


Maybe easier to split it up into actual URLs:

Note that the following is just one possibility, and will be changed now and in the future. Our aim is to make such changes easy.

  • Homepage
  • Vision (short)
    • Common ontology for LCA, MFA, and IE
    • Open data pipeline
  • By the community, for the community
    • Getting started guide
    • GH projects repo
  • Should be short, more of an appetizer than a meal, with links to more documentation

  • Introduction to core concepts of the ontology, starting with a gentle introduction to linked data
  • Ends with links to other docs/visualization for complete ontology
  • Target audience is people who have never heard "RDF" before

  • Subway-style map with the different data processing steps, and the accompanying repositories / web resources
  • Target audience is people who are used to using the "Excel hammer"

  • Brief page with links to more specific getting-started guides. Help people decide what getting started guide is right for them.
  • Could also contain a toolkit, like http://toolbox.schoolofdata.ch/



bonsai.uno/getting-started/others as we develop

  • Community management philosophy
  • Links to BEPs

  • FAQs to be populated. 
    • How is BONSAI different than other LCA databases?
    • How can I contribute?
    • Who is behind BONSAI?
    • What is the relationship between the project and the NPO?
    • Is anyone paid to work on BONSAI?

  • Archive of official documents
  • Become a member

To do:
  • Look into CSS classes used (everything necessary is in the repo already), decide if we want to keep using SASS as CSS preprocessor, create some more classes (and maybe more meaningful labels for common layouts). Write up brief notes on using the CSS to get what you want.
  • Write some sample content for 1-2 pages, esp. data flow, homepage, and ontology
    • Then do some layout with bright, colorful, and simple graphs (e.g. for links between ontology concepts).