Instead of input/output it could be more like "doing this" and "produces this", or something similarly more user friendly...

On Fri, Aug 12, 2016 at 4:01 PM Jeffrey S. Oishi <> wrote:
Hi Matt,

The website looks outstanding. I really like it. One small thing: in the examples code/output part, perhaps under the menu bar it could list the current example name (so, "Quick Calculations" for the default) and label the panes "input" and "output". It might help people understand what the website is showing, since code examples like that are not super common.

Otherwise, it's really great. Nice work!


On Fri, Aug 12, 2016 at 2:33 PM Matthew Turk <> wrote:
Thanks for the feedback, folks.  I've pushed up a new version with all the examples that were previously placeholders filled out:

I think this is the part of the front page that needs the most help.  If you have ideas for pithy examples, I'm happy to either add them, or pull from your repo/pull request.

I'll send out again once I've added the extensions and other bits, but I think folks seem to be generally in favor, so I'll keep working on it off and on.


On Fri, Aug 12, 2016 at 9:45 AM, Matthew Turk <> wrote:
Hi folks,

A while ago, was converted to a "generated" site.  Templates are used to generate each page, so it's much easier to modify.  I've also moved the calculation of contributors into a function, and the gallery and the members list are in .yaml files, so they can be updated without writing raw HTML.

I took some time this week to experiment a bit with the website.  My fork is here:

and a build is here:

The big changes:

 * Light instead of dark background ("cyborg" theme to "flatly")
 * Made the text more normal-sized most places
 * Changed the masthead on the front page to *not* be a carousel and have the new logo, along with a more punchy intro
 * Added a set of "examples", which come from a .yaml file.

I've been experimenting with the examples and the theme in particular, and I personally like it a lot more.  

If you fork my repo and make changes (especially if you want to add examples, which can take *either* text output *or* images) as soon as the changes go in, it auto-builds on .  Feedback here or on slack would be very much appreciated, and if folks like it, I'd like to deploy it.

A few other things it would need before it's ready:

 * Add an extensions page, with extension information drawn from .yaml file
 * Make the blog look like this thing, and maybe figure out if the blog could be part of the repo
 * Update the text and images wherever appropriate (i.e., update references to the hub)
 * Streamline navigation a little bit
 * Fill out the examples, maybe even have them link to the hub


yt-dev mailing list