[yt-dev] Website redesign feedback

Cameron Hummels chummels at gmail.com
Thu Sep 19 20:17:37 PDT 2013


Notebooks would make a great replacement for the recipes, however, I think
the embedded images will be too much for hg.


On Thu, Sep 19, 2013 at 8:10 PM, Nathan Goldbaum <nathan12343 at gmail.com>wrote:

> +1 on copying PyNE's use of notebooks in the docs
>
> Specifically, take a look at this page:
>  http://pynesim.org/gallery/half_life.html
>
> The RST file that generated this page is here:
> http://pynesim.org/_sources/gallery/half_life.txt
>
> How do you all feel about converting all of the existing recipes to
> notebooks and
> then using the sphinx macro PyNE is using to include them?  That means
> checking IPython notebooks that embed images into version control, I'm not
> sure if that will be painful to deal with.
>
> -Nathan
>
>
>
> On Thu, Sep 19, 2013 at 6:51 PM, Cameron Hummels <chummels at gmail.com>wrote:
>
>> Oh, and the "yt-project" link in the upper left of the header does not
>> link to anything.  it might be good to have that link to Home.  In fact,
>> you might be able to do away with the Home link if you were to do this.
>>
>>
>> On Thu, Sep 19, 2013 at 6:49 PM, Cameron Hummels <chummels at gmail.com>wrote:
>>
>>> I think it would be useful to have a link to both the stable docs as
>>> well as the dev docs, if that's an option.  Even with the increased
>>> frequency of releases, there is still some lag time between dev docs
>>> getting pulled into the stable.
>>>
>>> Under the community page, the last link on the Sharing Scripts header
>>> has a typo: pastebine.
>>>
>>> Under the development page, there is a word missing in the second
>>> sentence: "...the development branch, the and even this website."
>>>
>>> I think the gallery is a great idea--now we just have to populate it.
>>>  Is the idea to show off published work?  Does it have to be published?
>>>  Also, I think we should have people submit both a thumbprint (400x400 as
>>> is done) as well as a full-res image which is linked through the
>>> thumbprint.  Or perhaps it's enough that the paper is linked?
>>>
>>> So we'll also have another gallery in the docs with images shown as well
>>> as the cookbook recipes which created them (a la matplotlib)?  I think that
>>> would be useful.
>>>
>>> Overall, I think the page looks good.
>>>
>>>
>>> On Thu, Sep 19, 2013 at 6:35 PM, Geoffrey So <gsiisg at gmail.com> wrote:
>>>
>>>> "Ah, I agree about the doc link; not sure about the other two. What
>>>> about switching blog to being under Quick Links and replacing it with a
>>>> link to the latest stable docs? I don't think a search box will quite work
>>>> on the toolbar."
>>>>
>>>> - Doc would be my first choice, too.  Search is within the doc so it
>>>> would be just one step away, and usually I wouldn't know what to search for
>>>> until after I looked at the Docs, so not having search at the beginning is
>>>> fine.
>>>>
>>>> "Where should the colors be changed? I do want to brighten the text a
>>>> bit, but can you suggest other places?"
>>>>
>>>> - I just thought the color template of the Docs looks pretty nice, kind
>>>> of similar to python/numpy etc, but I also understand the need for the
>>>> black background since we're doing astro, but some addition of bright
>>>> colors would help "lighten" the mood (pun intended), so maybe use a
>>>> brighter shade of grey for the text, and/or color coded section label.  But
>>>> I also noticed my laptop brightness wasn't turned all the way up, so at max
>>>> brightness it is not as gloomy as I thought before.
>>>>
>>>> From
>>>> G.S.
>>>>
>>>>
>>>> On Fri, Sep 20, 2013 at 9:25 AM, Matthew Turk <matthewturk at gmail.com>wrote:
>>>>
>>>>> Hi Geoffrey,
>>>>>
>>>>> On Sep 19, 2013 9:06 PM, "Geoffrey So" <gsiisg at gmail.com> wrote:
>>>>> >
>>>>> > These are just personal preference:
>>>>> >
>>>>> > I usually use the yt website to look things up when I don't know or
>>>>> forgot something, so I would prefer to have one of the following on the
>>>>> tabs on the front page in descending preference.
>>>>> >
>>>>> > 1) documentation
>>>>> > 2) search function
>>>>> > 3) quick start guide
>>>>> >
>>>>> > This would help me at least to find information I want about yt
>>>>> faster and make the site more useful.
>>>>> >
>>>>>
>>>>> Ah, I agree about the doc link; not sure about the other two. What
>>>>> about switching blog to being under Quick Links and replacing it with a
>>>>> link to the latest stable docs? I don't think a search box will quite work
>>>>> on the toolbar.
>>>>>
>>>>> > I think it's great to have a link at the very top,
>>>>> enabling/encouraging people to become developers.  The site looks fresh
>>>>> from some of the new images on the gallery, but I'd like to see more more
>>>>> bright colors to contrast the black background
>>>>> >
>>>>>
>>>>> Where should the colors be changed? I do want to brighten the text a
>>>>> bit, but can you suggest other places?
>>>>>
>>>>> Matt
>>>>>
>>>>> > From
>>>>> > G.S.
>>>>> >
>>>>> >
>>>>> > On Fri, Sep 20, 2013 at 8:23 AM, Matthew Turk <matthewturk at gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> Hi all,
>>>>> >>
>>>>> >> The last week or so, I've been working on a redesign of the website.
>>>>> >> I've gotten some really good feedback from Nathan, Britton and a few
>>>>> >> others, and I think it's ready to be opened up for more general
>>>>> >> comments.
>>>>> >>
>>>>> >> The redesign pull request is here:
>>>>> >>
>>>>> >>
>>>>> https://bitbucket.org/yt_analysis/website/pull-request/11/draft-redesign-using-twitter-bootstrap/diff
>>>>> >>
>>>>> >> and the redesign itself can be viewed here:
>>>>> >>
>>>>> >> http://yt-project.org/index2.html
>>>>> >>
>>>>> >> There were a couple goals here:
>>>>> >>
>>>>> >>  * Make information much easier to get at
>>>>> >>  * Reduce the text and increase the size of the text on the front
>>>>> page
>>>>> >>  * Make the website *way* easier for people to edit
>>>>> >>  * Make the website *way* less javascript heavy
>>>>> >>  * Indicate much more strongly that we're part of the scientific
>>>>> >> Python ecosystem
>>>>> >>  * Emphasize that yt is analysis-focused with visualization built on
>>>>> >> that, rather than the other way around
>>>>> >>
>>>>> >> There are a few visual glitches still (the headings underline when
>>>>> you
>>>>> >> mouse over them, and I'm trying to make the text lighter) but I
>>>>> think
>>>>> >> it's ready for feedback.  I'd appreciate any comments, either here
>>>>> or
>>>>> >> on the pull request.  And, if we decide this is *not* the direction
>>>>> to
>>>>> >> go, that's fine too!
>>>>> >>
>>>>> >> Britton and I have gone back and forth on how to fix up the gallery
>>>>> >> and integrate the hub and the blog more deeply.  That's a much
>>>>> longer
>>>>> >> project, but we see the three all coming together nicely in the
>>>>> >> future.  As it stands, the Gallery will likely include a few images
>>>>> >> linked to scientific papers, link to a few things on the hub
>>>>> >> (notebooks, projects, etc), and is currently handled via version
>>>>> >> control.
>>>>> >>
>>>>> >> Britton's working on expanding it, but if you can read this, you
>>>>> >> should also add some stuff to it!  Ultimately what I think would
>>>>> work
>>>>> >> best would be to solicit contributions directly, solicit
>>>>> contributions
>>>>> >> to the hub, and then flag some things for display in the gallery.
>>>>>  It
>>>>> >> would be nice to include basically all types of contributions here
>>>>> --
>>>>> >> notebooks, scripts, figures, papers -- and I'm coming to really
>>>>> think
>>>>> >> the gallery is essential.
>>>>> >>
>>>>> >> Incidentally, this week as Anthony and I have been working on
>>>>> getting
>>>>> >> support for PyNE interoperability with yt, I've had occasion to view
>>>>> >> their docs and found them to be really nice.  The gallery system
>>>>> they
>>>>> >> have is quite nice and very similar to where we're going with the yt
>>>>> >> docs and the cookbook, but just a *little* bit further than we've
>>>>> >> gone:
>>>>> >>
>>>>> >> http://pynesim.org/
>>>>> >> http://pynesim.org/gallery/index.html
>>>>> >>
>>>>> >> If we decide this website is the way to go, I'll spend some time
>>>>> >> trying to make our docs play look a bit nicer with it, although
>>>>> likely
>>>>> >> not with black background.
>>>>> >>
>>>>> >> Thanks for any feedback,
>>>>> >>
>>>>> >> Matt
>>>>> >> _______________________________________________
>>>>> >> yt-dev mailing list
>>>>> >> yt-dev at lists.spacepope.org
>>>>> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>> >
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > yt-dev mailing list
>>>>> > yt-dev at lists.spacepope.org
>>>>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>> >
>>>>>
>>>>> _______________________________________________
>>>>> yt-dev mailing list
>>>>> yt-dev at lists.spacepope.org
>>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> yt-dev mailing list
>>>> yt-dev at lists.spacepope.org
>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Cameron Hummels
>>> Postdoctoral Researcher
>>> Steward Observatory
>>> University of Arizona
>>> http://chummels.org
>>>
>>
>>
>>
>> --
>> Cameron Hummels
>> Postdoctoral Researcher
>> Steward Observatory
>> University of Arizona
>> http://chummels.org
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>


-- 
Cameron Hummels
Postdoctoral Researcher
Steward Observatory
University of Arizona
http://chummels.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20130919/5979a339/attachment.html>


More information about the yt-dev mailing list