Skip to content

Organization of ml5 examples #187

@tlsaeger

Description

@tlsaeger

Hey community,
I'm submitting this issue based on a discussion over on Discord with @joeyklee, @afogel and @shiffman. We talked about how we can make the examples on our page more appealing to new users and all in all more organised.

I'm suggesting a a few things here and did a bunch of mockups so we can discuss this more visually.

Reference Page

First up on the old page we have a lot of recurrences, every examples is there in most cases three times. Once for Vanilla JS once for p5.js and once for the web editor. In my proposal each example is displayed only once with a link to all three »platforms«.

We also talked about writing a short description for each example and adding an image of it in action. I mentioned on discord, that this could be done by our community. One advantage would also be, that we could show the many faces of our community. If they take pictures using one example.
Web 1920 – 4

I think we could also ditch the name of the model from the example on the page. It's the PoseNet page so here are the PoseNet examples, @joeyklee also talked about ditching the underscore and I'm pro that as well. Even though I haven't done it all the designs you see here, I was just lazy.

If we don't have a description or an image this new version would still be beneficial and is easily adapted to that.
Web 1920 – 2

I think the Neuroal Network Examples illustrate this in the best way, if we don't have a description and image and just rework this in the new design, it would save a lot space.
Web 1920 – 3
Web 1920 – 6

Examples Page

@afogel and @shiffman also talked about how to rework the page https://examples.ml5js.org/ I took inspiration off that and worked out a list focused design. That uses that description we made for the reference page. I also links to our reference page, so it is not that much of a dead end.
Web 1920 – 5

We might even be able to squeeze in the image:
Web 1920 – 7

What do you guys think? I have never worked with React only Vue so I might need some help when implementing this into our library.

✌️

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions