A redesign of the Django websites(djangoproject.com)
djangoproject.com
A redesign of the Django websites
https://www.djangoproject.com/weblog/2014/dec/15/announcing-django-website-redesign/
99 comments
They're not using Bootstrap.
Whether they are or not, it still looks like it. I think that's what he meant by "vibe."
As someone who looks at the docs every day, I think the redesign is refreshing :D To each their own.
I really, overall, love the redesign. It's much cleaner, better organized and it's awesome to have better support for width based scaling. As someone who uses the Django documentation very often, I'm happy to see this redesign.
I must plea, though, that if anyone responsible is reading, it would be extraordinarily helpful if the green highlight color is set back to the system default, or at least a darker color. I have quite a bit of trouble following through blocks of text on a screen or reading black-ish colors on bright white backgrounds, and often use my highlighting tool to help me keep track of location and to distinguish the text from the background. The almost invisible green makes that very difficult for me.
I must plea, though, that if anyone responsible is reading, it would be extraordinarily helpful if the green highlight color is set back to the system default, or at least a darker color. I have quite a bit of trouble following through blocks of text on a screen or reading black-ish colors on bright white backgrounds, and often use my highlighting tool to help me keep track of location and to distinguish the text from the background. The almost invisible green makes that very difficult for me.
Done! https://github.com/django/djangoproject.com/pull/192
Will be deployed soon :)
Will be deployed soon :)
Thanks for the update, looks quite a bit better!
This is a very interesting redesign, and it shocks me that they chose to do it. On the one hand, this update is beautiful with a tasteful front page and familiar-yet-fresh documentation pages. On the other hand, the old design was also fantastic.
Despite kicking around for just under 10 years, the old Django look never felt old, ugly, or clunky. It had a clean, thoughtful layout with good color contrast and an unmistakable Django identity. To me, it never gained the "cruft" that similarly-aged designs seem to take on. It always felt modern.
Loving the new design, but I would have never guessed that there were plans to ditch the old one.
Despite kicking around for just under 10 years, the old Django look never felt old, ugly, or clunky. It had a clean, thoughtful layout with good color contrast and an unmistakable Django identity. To me, it never gained the "cruft" that similarly-aged designs seem to take on. It always felt modern.
Loving the new design, but I would have never guessed that there were plans to ditch the old one.
Absolutely, the previous design tenure of 10 years is quite a feat. There are very few websites that can last this long without feeling old-fashioned.
I'd personally disagree, if only because the actual text space columns were so thin that it made everything I was reading feel very, very busy. It took me weeks to get comfortable regularly going to their documentation instead of looking at SE, even though their documentation was very, very good.
No matter what web stack I end up using down the road, I will always have a special place in my heart for Django. It taught me the fundamentals of MVC in web app context, and in some ways got me a job that led to many good things in my life.
Redesign looks nice, the old site was beginning to look dated.
Redesign looks nice, the old site was beginning to look dated.
Funny how, even after a redesign, I can still recognize the layout of the docs after occasionally looking at them a few times a year :) https://docs.djangoproject.com/en/1.7/
This is an important point I think. People have been referring to these docs for years and got very comfortable with the layout. I'm glad they kept this part so similar.
This is a lot more readable and approachable - nice work! Cool to see that the designers managed to stick to the green template while making it work for a bunch of different content types. Thanks for the update!
I think it has too much empty space ...
Yeah, there's a lot of whitespace - I'm not the biggest fan of all that padding on the blog / archive dates template, or the L-R padding on the home page, but I hear "more space" is all the rage :)
Mostly I noticed the difference in the Docs. The elements are called out more explicitly and it's easier to find things on the docs, which have considerably less whitespace: https://docs.djangoproject.com/en/1.7/intro/tutorial01/
Mostly I noticed the difference in the Docs. The elements are called out more explicitly and it's easier to find things on the docs, which have considerably less whitespace: https://docs.djangoproject.com/en/1.7/intro/tutorial01/
Yes, even I thought the same. I hate that the home page has a lot of content that I have to scroll down to view (at 1440x900 resolution).
http://ibin.co/1kret3oW7caZ illustrates whitespace wastage in the blog
Edit: Added an illustration
http://ibin.co/1kret3oW7caZ illustrates whitespace wastage in the blog
Edit: Added an illustration
> whitespace wastage
there is no such thing. Think more whitespace equals more focus around the content and less clutter.
there is no such thing. Think more whitespace equals more focus around the content and less clutter.
Overall I like it, but it could really do with a max-width set for the content. I use my browser full screen on a 24" monitor and some of the line lengths are far in excess of readable.
The max-width has been deployed, thanks for the feedback.
Ahhh that's much better. Amazing responsiveness!
I like the new design but IMHO there was nothing wrong with the old one.
There was something very warm and reassuring about the old colors and I feel there was more information filled.
There was something very warm and reassuring about the old colors and I feel there was more information filled.
The old design was/is awesome, I'll miss it.
I didn't fell comfortable with the new one, looks too bright to my eyes.
I didn't fell comfortable with the new one, looks too bright to my eyes.
I totally agree.
First impressions:
- Increased whitespace makes it feel less informationally dense.
- The colors are a bit too light. As someone with sensitive eyes, it makes reading the docs for long periods of time harder. This is going to be tough to get used to.
- For whatever reason, my eyes keep skipping over the light green bar that's between the nav and the content. I didn't even see the download link on the getting started page until I took a second look at it. I wonder why this happens?
Overall, I'm not adverse to it. I like the clean look, but one reason why I liked the old site is because I could see all the information I'd want to know on the first page without scrolling. You can't get that here, and it makes me wonder how much information I'll miss out on over time.
- Increased whitespace makes it feel less informationally dense.
- The colors are a bit too light. As someone with sensitive eyes, it makes reading the docs for long periods of time harder. This is going to be tough to get used to.
- For whatever reason, my eyes keep skipping over the light green bar that's between the nav and the content. I didn't even see the download link on the getting started page until I took a second look at it. I wonder why this happens?
Overall, I'm not adverse to it. I like the clean look, but one reason why I liked the old site is because I could see all the information I'd want to know on the first page without scrolling. You can't get that here, and it makes me wonder how much information I'll miss out on over time.
I love the new design, it encompasses many modern design patterns, it's clean, flat and all the elements have room to breath. My biggest issue with the redesign it that I and many others have huge difficultly reading black text on a white background. If anyone would like to find out more about visual stress then this link provides a quick, easy to digest overview http://www.crossboweducation.com/articles/visual-stress-symp....
I hope it's a problem they acknowledge and provide a solution in a future iteration. Until then, I'll have to install a browser extension to modify the background colour.
I hope it's a problem they acknowledge and provide a solution in a future iteration. Until then, I'll have to install a browser extension to modify the background colour.
I've never heard of this actually, I would have thought black on white was the best way to read text.
What would be a better choice? Would black on off-white be better?
What would be a better choice? Would black on off-white be better?
Honestly on a backlutz screen, grey on navy is hard to beat. There's a reason all of those 80s mainframe apps looked like that. They did studies.
While most printed materials are "black" on "white," when the range is compared to a light-emitting screen that's more like "dark gray" on "light gray." Looking at something with too much contrast for a long time can cause eyestrain.
I liked, have only two criticisms:
Content seems sparse, maybe due to line-height and/or font-size.
I also get a "too much green" feeling in my eyes.
The overall change was positive, imo.
I zoom the page down to 75% to browse the docs, it gives the same spacing as the old layout.
Good! This gives a much more comfortable visualization.
I also get the "too much green" feeling, which is odd because the old website had far more green.
Yeah, the font-size and line-height are a bit much.
It must just be me, but it feels that the site is optimized for mobile browsing. There is very little content and my eyes have to move massively just to read the page. I actually prefer the old layout. :/
Documentation websites actually have some pretty good use-cases to being scalable to mobile, either because people will view documentation on a tablet or phone while developing, or due to people using smaller browser widths when developing to be able to display their IDE or terminal windows next to the documentation windows.
Yeah, no.
Smaller browser widths I agree
But using a phone/tablet to navigate the docs? Might as well use notepad for coding too, since the objective is to suffer.
Smaller browser widths I agree
But using a phone/tablet to navigate the docs? Might as well use notepad for coding too, since the objective is to suffer.
Well, the nice thing about mobile first is that the benefits extend to smaller browser widths as well. And just because you don't find a method appealing to use doesn't mean it's not a valid use case. I, for one, like to have all my documentation offline in ePub on a tablet, but that doesn't mean I assume it's the best method for everyone else (or even anyone else).
Plus, though it amy be an unintended consequence, mobile first shouldn't at all hurt the desktop experience, just make sure that mobile is not an afterthought once the design patterns are engrained and it's too late to modify a responsive experience.
Plus, though it amy be an unintended consequence, mobile first shouldn't at all hurt the desktop experience, just make sure that mobile is not an afterthought once the design patterns are engrained and it's too late to modify a responsive experience.
It seems there's a range of opinions on this - no surprise. I find myself frequently, though not exclusively, using my phone (current, iPhone 6+) or tablet for docs while I use my laptop for coding. I know others who do this too. It's all anecdotal, but I don't think of having good mobile support on a docs site as being an edge case.
Also, I work a lot in Django, and love the new site.
Also, I work a lot in Django, and love the new site.
Good job on the redesign. I think it looks great.
How about getting rid of Trac now? There's really no worse issue tracker...
How about getting rid of Trac now? There's really no worse issue tracker...
I think that there's too much historical data in Trac for them to ditch it. Migrating would be difficult.
We migrated from trac to jira a couple years ago and it actually wasn't that bad. So glad that we did. Trac works fine for little tiny projects (although these days I would just use github or bitbucket issue tracking). Jira really shines on larger projects though.
[deleted](1)
I liked the old site better. This is clearly a case of, "If it ain't broke, don't fix it." The purpose of documentation is utility, not to look modern. It does nothing that I can see to improve the utility. In fact, all of the white space makes it harder to use. It would be nice if there were an older "theme" users could continue using.
Agreed. The site now... looks more like every other site. But why's that a good thing? Old design had a more unique personality -- new one looks very much like a Bootstrap deploy with tweaked colours.
Anecdotally both django and rails maintained the same aesthetics in their respective sites for more than nine years (rails still does).
https://web.archive.org/web/20051214180106/http://www.rubyon... https://web.archive.org/web/20050801014309/http://www.django...
https://web.archive.org/web/20051214180106/http://www.rubyon... https://web.archive.org/web/20050801014309/http://www.django...
It's amazing what a facelift can do to the perception of a project. There are some really great projects that look abandoned or the docs are really difficult to use that prohibit me from giving them a fair shake.
It's amazing how many people measure a project based on the amount of time it spends redesigning the website to follow the trend-du-jour.
Yep, that's exactly what I'm saying. It's not fair, but it is the case.
This isn't as crazy as it might seem - using a modern home page design proves that someone has been investing time in the project since that design became popular.
Using the "trend-du-jour" for a homepage quickly communicates to viewers that the project is alive & active. It's a much more accessible signal than mailing list or commit history (although those are clearer, more accurate signals of project health).
Using the "trend-du-jour" for a homepage quickly communicates to viewers that the project is alive & active. It's a much more accessible signal than mailing list or commit history (although those are clearer, more accurate signals of project health).
My take aways: too much white space, the highlight colour when you select text within code wells is really hard to distinguish & as others have mentioned black on white is hard on the eyes.
The highlight color has been fixed and will be deployed soon. Thanks for feedback!
The docs have been made a bit denser, thanks for the feedback guys!
I was in the middle of checking the docs, so that was a little odd, but I like it so far. It is different without being TOO different in terms of layout so the familiarity sticks.
It looks slightly blurry on Chrome for me, seems to have been tested primarily on Safari? Also, the redesign may be a bit bland, but overall it's a pretty good job. Now if someone could apply those design cues to Django-Admin that would be awesome!
It looks slightly blurry on Chrome for me, seems to have been tested primarily on Safari? Also, the redesign may be a bit bland, but overall it's a pretty good job. Now if someone could apply those design cues to Django-Admin that would be awesome!
It looks nice! I do agree with others who are saying that a page with docs shouldn't have this much white space as it makes it harder to read.
I may just be noticing an old feature, but did the search feature on the prior site return source code in the results?
I think that is a great feature, but it's going to confuse beginners. The first three results for the query 'models' are links to source code.
Maybe the search results could be tagged with a type icon and name (Documentation, Tutorial, Source...) in addition to the document excerpt.
I think that is a great feature, but it's going to confuse beginners. The first three results for the query 'models' are links to source code.
Maybe the search results could be tagged with a type icon and name (Documentation, Tutorial, Source...) in addition to the document excerpt.
Wow, I always love redesigns. But as another commentor says, I'm a bit worried how long it will take for my eye memory to adapt ...
Considering that the layout of the documentation hasn't changed in any significant way. Not long at all.
Overall I think it's good
Things I don't like:
* #6A0E0E is too dark for links, the color from hover effect would be much better (#BA2121).
* Front page right sidebar has too much links. I feel the latest news section should have "more priority". I often visit Django's website just to check whether there is a new release and blog post associated to it.
Things I don't like:
* #6A0E0E is too dark for links, the color from hover effect would be much better (#BA2121).
* Front page right sidebar has too much links. I feel the latest news section should have "more priority". I often visit Django's website just to check whether there is a new release and blog post associated to it.
Looking great. Thanks for great Christmas gift :D
On the other hand, I feel like I am going to miss old design - is there archive somewhere?
On the other hand, I feel like I am going to miss old design - is there archive somewhere?
I'm colorblind and some links on the documentation https://docs.djangoproject.com/en/1.7/ don't look different enough from normal text. Mostly I'm having a hard time identifying links that aren't underlined.
I'm not colour blind, but I had to look at them for a moment to see they were even different colours, man that's a subtle difference.
Are you Red/Green colour blind? Personally I would have picked a colour closer to the green used in other places of the site to highlight links, but I suddenly became curious as to whether or not that would be any better for you.
Not that I can do anything about it, I'm just really nosy about it since you mentioned it.
Are you Red/Green colour blind? Personally I would have picked a colour closer to the green used in other places of the site to highlight links, but I suddenly became curious as to whether or not that would be any better for you.
Not that I can do anything about it, I'm just really nosy about it since you mentioned it.
I'm sure they'd appreciate any feedback & examples on accessibility issues. If you've got some time consider raising it on the issue tracker.
Thanks for the feedback, this is invaluable! We would love to hear more from you on our issue tracker: https://github.com/django/djangoproject.com/issues
looks great - doc site is cleaner yet still very familiar. Everything else aside, I'd kill for better doc search - or just simply allowing () to search for functions. Trying to refresh my memory on how the .first() or .latest() method works, for example, requires browsing. no real way to search for it.
There are two issues I have with the redesign: the use of Palatino as the body typeface, and the dark green body text, which I think would've been better as a dark grey.
Other than that and a few spacing issues, it's good!
Other than that and a few spacing issues, it's good!
If you miss old Docs UI, here it is on ReadTheDocs http://django.readthedocs.org/en/latest/ :)
[deleted]
Is there a word for muscle memory but for your eyes?
After so many years it's going to take a while to get used to but first impression is that it looks nice and readable. Code snippets look much better.
After so many years it's going to take a while to get used to but first impression is that it looks nice and readable. Code snippets look much better.
> Is there a word for muscle memory but for your eyes?
Memory?
Memory?
Visual memory, I guess. http://en.wikipedia.org/wiki/Visual_memory
One thing I haven't seen mentioned is the addition of an option to download the docs in .epub, which is great and previously was a pain point (at least for me).
The new design reminds me of mint ice cream. In a good way.
You should really fix the selection color. I usually select text while reading it, and I can barely see the selection here. Otherwise, good job!
This has been fixed by andrevvm and will be deployed soon: https://github.com/django/djangoproject.com/pull/192. Thanks for feedback!
OT:
I know that Django 1.6+ can be used with Python 3.4 but is Django 1.7.1 written in Python 2.7 or 3.4?
I know that Django 1.6+ can be used with Python 3.4 but is Django 1.7.1 written in Python 2.7 or 3.4?
Both.
It is possible, and not too difficult in fact, to write a single codebase that runs under both Python 2 and Python 3. Which is what Django has done. The same code runs the same under 2.7 or 3.3 or 3.4.
It is possible, and not too difficult in fact, to write a single codebase that runs under both Python 2 and Python 3. Which is what Django has done. The same code runs the same under 2.7 or 3.3 or 3.4.
Thanks for the reply.
Are there any guidelines or "best practices" for writing code for both 2.7 and 3.4?
Are there any guidelines or "best practices" for writing code for both 2.7 and 3.4?
http://python-future.org/compatible_idioms.html
This is a pretty comprehensive guide. It does rely on the future lib, which is a wrapper around six and a few others to make it easier, but you can also just write your own minimal lib for things that need to have:
This is a pretty comprehensive guide. It does rely on the future lib, which is a wrapper around six and a few others to make it easier, but you can also just write your own minimal lib for things that need to have:
if py2:
pass # Py2 specific line here
else:
pass # Py3 stuff here
Here is Django's documentation, including notes on the compatibility stuff we ship:
https://docs.djangoproject.com/en/1.7/topics/python3/
https://docs.djangoproject.com/en/1.7/topics/python3/
I was actually browsing the docs when the change went through and did a triple take.
That must have been oddly disorienting.
Looks good! Maybe I should start a new Django Project again.
That font is terrible. Please bring back sans serif.
I like new design, but I think it's quite bright.
I like this redesign
I love it, I have a thing for pastels.
Nice work!
It's always difficult and probably unfair to express an opinion right after having seen the redesign.
As with any complete overhaul that keeps close to nothing from the previous version, it's very hard to improve the experience without losing any sense of identity. In this case, the Bootstrap vibe is quite prominent.
It does makes sense for the documentation, but the main page is less appealing. I'm not a developer, but the previous design actually got me intrigued by the framework and encouraged me to look deeper.
I guess a redesign was probably needed. I just hope it's a design they will iterate over.