Sounds good to me.

On Mon, Aug 22, 2016 at 5:34 PM, Nathan Goldbaum <> wrote:
We're having a PR hangout on Wednesday, maybe we can chat then about how to merge it?

If this Wednesday is no good, we could schedule another hangout next week or the week after.

On Monday, August 22, 2016, Matthew Turk <> wrote:
Hi folks,

I've issued a PR:

This includes all the feedback I've received (except for the new examples to add, which I have issued a separate call for suggestions to this list) and I think is a pretty good improvement.  If I have forgotten some of your feedback, it's because I've forgotten, not because I'm trying to ignore anyone.

I can't figure out how to make the yt logo not be obnoxiously large when it's viewed on mobile, but I think that the mobile presentation is a bit better with the way I've shifted things around in the example section.  Maybe not perfect, but better.  Suggestions would be welcomed, but on the PR might be easiest.

The demo website gets updated with some regularity:

We don't really have a process in place to decide when it's OK to accept a big change like this, so please let me know if you have some feedback and we'll see if we can keep it moving along.  Thanks for your feedback, all!


On Sat, Aug 13, 2016 at 6:04 PM, John ZuHone <> wrote:
Hi Matt,

I should point out that you added my unit system example but the field you have there (“kT”) is forced to keV units unless you change it with `slc.set_unit`. So if you want it to be a unit 
system example maybe you should choose “density” or “temperature” instead. 


On Aug 13, 2016, at 7:01 PM, Matthew Turk <> wrote:

Hi folks, I have fixed up a couple things on mobile; not totally satisfied with how it looks on mobile yet, but working on it.  I've also added "extensions" and consolidated a few things under "About" but I fear the navbar is getting unwieldy.

Cameron, I think that's a good idea, but I am not sure which to change.  I filled out some of the examples I set out to do, but I think there's room to do more, so I think I'd be happy with folks contributing examples.  They're all defined in a .yaml file that's pretty easy to add to or edit:

and the extensions are likewise:

So updating this stuff should be easy.  Anyway, the website is rebuilding with the recent changes and should be up here in about ten minutes:


On Sat, Aug 13, 2016 at 12:17 AM, Cameron Hummels <> wrote:
I think in general it looks good, but I'm not sure we want all of the examples to use the alternative method of indexing data.  Would it be possible to show a slice plot or projection plot using the traditional method for generating these objects (e.g. SlicePlot and ProjectionPlot)?  The current examples only mean something if people are familiar with numpy indexing.  Alternatively having both data objects as well as the region examples might be OK since they are equivalent.  Other that than, it looks good!

On Fri, Aug 12, 2016 at 10:06 PM, John ZuHone <> wrote:
I'm with Nathan--it needs probably a little work to show up right on mobile. Some screenshots are attached. Otherwise I think it's fabulous.

Sent from John ZuHone's iPad

On Aug 12, 2016, at 7:47 PM, Nathan Goldbaum <> wrote:

On Friday, August 12, 2016, Matthew Turk <> wrote:

Hi Jeff, thanks for the suggestion -- I tried a bunch of ways to make the text work, but couldn't quite make it.  I've added a big arrow; do you think that is sufficient?  If not, I'll keep trying with the text. (It's a bit off on mobile, but can be fixed if it's worthwhile.)

I've also added a preliminary extensions page, which isn't linked from main navbar but is at .

Hmm, just looked at this on my phone, the examples are kinda confusing there. The arrow also appears below the output.

On Fri, Aug 12, 2016 at 3:02 PM, Jeffrey S. Oishi <> wrote:
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

yt-dev mailing list

yt-dev mailing list

yt-dev mailing list

Cameron Hummels
NSF Postdoctoral Fellow
Department of Astronomy
California Institute of Technology

yt-dev mailing list

yt-dev mailing list

yt-dev mailing list

yt-dev mailing list