What was used to make the site? Django? Flask? Bottle?
Python.org Redesign Preview
81–90 of 165 posts
Re: Python.org Redesign Preview
#82Constructive criticism: The shadow on the logo is too dark and looks wierd. Also, I'd put a call to action, like "Download" or "Learn" in a more visible format (maybe on a button) in a larger font, above all the "blocks", along with the content of the Statistics block. The PSF block at the bottom looks out of place. (I really love the way you show additional information when I hover on the links in the second navbar.…
Thanks for the feedback, good stuff. BTW, please do try the nav on mobile devices, especially tablets. They work there, too, and I think our designers did something especially slick :)
Just checked it out on my tablet (iPad) - I don't see much of a difference (of course, it's responsive!) except for the menu, which works pretty well :)
Minor points:
- When in "mobile mode", the search box changes colour so it doesn't look like a text input any more. I'm not sure if that's a good idea.
- I agree with the others on this one again: the gradients and the shadows are a bit excessive. Maybe you could try a "flat" shadow instead? (ie. a shadow with a 0 blur radius)
- I really loved the old docs search mechanism where the site had a local index of keywords and could search without hitting the server. I hope you don't lose that.
- I'm not sure what the concept of the two navigation bars is. What is the top bar for, and what's the second bar for? I see "Documentation" in two places. Logically speaking, I'd expect the upper bar to be the primary navigation, and the lower bar to be the secondary navigation, but clearly, that isn't the case.
Anyway, is this open source as of now? Where can I contribute?
Re: Python.org Redesign Preview
#83The example should be runnable!
Re: Python.org Redesign Preview
#84Constructive criticism: The shadow on the logo is too dark and looks wierd. Also, I'd put a call to action, like "Download" or "Learn" in a more visible format (maybe on a button) in a larger font, above all the "blocks", along with the content of the Statistics block. The PSF block at the bottom looks out of place. (I really love the way you show additional information when I hover on the links in the second navbar.…
Thanks for the feedback, good stuff. BTW, please do try the nav on mobile devices, especially tablets. They work there, too, and I think our designers did something especially slick :)
It is great on an iPad. Works very well.
Re: Python.org Redesign Preview
#85Earlier quoted context omitted.
Thanks for the feedback, good stuff. BTW, please do try the nav on mobile devices, especially tablets. They work there, too, and I think our designers did something especially slick :)
Just checked it out on my tablet (iPad) - I don't see much of a difference (of course, it's responsive!) except for the menu, which works pretty well :) Minor points: - When in "mobile mode", the search box changes colour so it doesn't look like a text input any more. I'm not sure if that's a good idea. - I agree with the others on this one again: the gradients and the shadows are a bit excessive. Maybe you could try…
The code's not open source yet, but it will be. The idea is we'll deliver what we've promised to the PSF, then launch the site for real (i.e. replace python.org) and open source the code at the same time. We want to make this into a community-maintained thing, but first we got some real work to do :)
Re: Python.org Redesign Preview
#86mainnav element is unnecessarily wide. Also too much of spacing between the elements in top-bar.
The margin to "About" in the mainnav looks a bit odd. Is it required?
The contents of the mainnav is oddly placed. I feel it can be organized from left to right in terms of usability to users. Like Downloads and Documentation first rest should follow in the respective orders.
The latest news can be placed somewhere in the first page itself for better visibility. Users has to scroll down now to see it.
Re: Python.org Redesign Preview
#87Little thought: Wouldn't it be great to lazy load a JS live input console to actually try out the demo scripts on the frontpage? I'm missing those out for several language sites (eg Ruby).
Re: Python.org Redesign Preview
#88Serif font makes the l look like a 1 in the code.
@jacobian - hope you see this - it appears that you were hellbanned 41 minutes ago. I have no idea why - don't shoot the messenger!
I loaded the page in other browsers and saw my comment, but now there are like 20 others saying the same thing but my comment id is the predecessor to the one that's at the top (so i was first ;] ). what symptom tells you I was hellbanned?
Re: Python.org Redesign Preview
#89This redesign is amazing.
Having a snippet of code presented to you is nice.
However, I wonder whether it'd be possible to provide a more hands-on feel, possibly through something like " rel="nofollow">http://repl.it/languages/Python>. That way, one can interact with the snippet of code.
Re: Python.org Redesign Preview
#90The problem with python's website was never that it wasnt "Sexy" enough to attract newcomers. Its that the documentation was never as well written or well organized as other languages/libraries like ruby and jQuery.
Really? I've always found Python's documentation (especially the official tutorial) to be excellent. What do you think could be improved about it?
A navigable list of objects, functions, and methods would be really nice, something like this (preferably complete): http://api.rubyonrails.org
Another suggestion would be to split tutorials/examples apart from object references. For example, take a peek at the Python Decimal module docs: http://docs.python.org/2/library/decimal.html#module-decimal
All the information is there, but it isn't organized very well. There's a tutorial, overview of Decimal and its methods (with tutorials mixed within), and various "notes" sections. It's all mixed together, and confusing for a new user.
Personally, I'm more of a fan of this type of structure:
1. API documentation. No how-to's.
2. "Guides" and How-To's
Guides/How-To's including examples, introductions to use an object, spell out caveats, etc... This should get wordy when needed.
Both could have links to one another. For experienced coders, you'll mostly just use #1 (which fits great in a navigable list). For newbies, #2 will teach you how to do things.
$0.02