Re: A New Design for the "Congratulations!" Page

Hi Tim, Here are my thoughts: 1. The main message "it worked" has given his placement to a log, leaving the user to focus on the image when the page loads. This can leave the user wondering if it worked until they see the lwords "The Install Worked". Congratulations. reload the

Re: A New Design for the "Congratulations!" Page

That's a great news, let us know if we can help with more feedback. Federico On Fri, Apr 21, 2017 at 9:20 AM Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 18 Apr 2017, at 20:31, Tim Allen wrote: > > Your point on design by committee is spot-on;

Re: A New Design for the "Congratulations!" Page

On 18 Apr 2017, at 20:31, Tim Allen wrote: > Your point on design by committee is spot-on; I think that's the direction > we'll head in. Hello, For the sake of transparency, a group of five people (Tim, Chad, Collin Anderson, Frank Wiles, and myself) is now

Re: A New Design for the "Congratulations!" Page

The links to the tutorial/docs is a good idea. I would design the message like the other messages (404, 500, and current It Works!) to keep it look the same, but I would also accept the good looking version you proposed On Tuesday, April 18, 2017 at 5:44:13 PM UTC+2, Tim Allen wrote: > > I've

Re: A New Design for the "Congratulations!" Page

+1 here too, congrats! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To

Re: A New Design for the "Congratulations!" Page

I also give a big +1 to this. I'll really love to see this in django On 19 Apr 2017 11:05, "Adam Johnson" wrote: > A massive +1 from me too, but I'll not make any comments on design :) > > On 19 April 2017 at 09:58, Federico Capoano > wrote: > >>

Re: A New Design for the "Congratulations!" Page

A massive +1 from me too, but I'll not make any comments on design :) On 19 April 2017 at 09:58, Federico Capoano wrote: > Looks like a great improvement for newcomers! I hope to see this included > to Django. > > Federico > > -- > You received this message because

A New Design for the "Congratulations!" Page

Looks like a great improvement for newcomers! I hope to see this included to Django. Federico -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from

Re: A New Design for the "Congratulations!" Page

On Tuesday, April 18, 2017 at 1:25:36 PM UTC-5, Tim Allen wrote: > > Thanks for the kind words. To answer your questions: > > - It is also my hope to automagically create version friendly links, so we > don't see a commit on each Django release. > This ought to be useful to sub in where

Re: A New Design for the "Congratulations!" Page

I was also reminded of green color the green color discussion. >From the discussion about the admin redesign [0][1]: "makes keeping a visual identity for Django hard to separate from the admin UI" "the admin is part of _your_ site, not ours, and so should have a visually-distinct theme/brand that

Re: A New Design for the "Congratulations!" Page

On Tue, Apr 18, 2017 at 11:27 AM Daniele Procida wrote: > On Tue, Apr 18, 2017, Tim Allen wrote: > > >It struck me that this page is valuable real estate > > Yes it is! Firstly, I think that both your idea and design are excellent > and I approve. > >

Re: A New Design for the "Congratulations!" Page

Your point on design by committee is spot-on; I think that's the direction we'll head in. Thanks for the kind words, and I've noted the issues on the smaller height and smaller screen issues. It is much apprecaited! Regards, Tim On Tuesday, April 18, 2017 at 1:30:23 PM UTC-4, Aymeric Augustin

Re: A New Design for the "Congratulations!" Page

Thanks for the kind words. To answer your questions: - My colleague Chad did the rocket animation. We'll both do git signed commits on any pull request and add ourselves to authors. - It is also my hope to automagically create version friendly links, so we don't see a commit on each Django

Re: A New Design for the "Congratulations!" Page

Hello Tim, Thanks, that's a great initiative! Given the well-documented success rate of design by committee, including our experience redesigning djangoproject.com, there's a risk that an inconclusive discussion on this mailing list will prevent your proposal from moving forwards. Perhaps a

Re: A New Design for the "Congratulations!" Page

On Tue, Apr 18, 2017, Tim Allen wrote: >It struck me that this page is valuable real estate Yes it is! Firstly, I think that both your idea and design are excellent and I approve. Secondly, since that space is valuable, perhaps it could also say: This release of

Re: A New Design for the "Congratulations!" Page

Beautiful. The Google Font should not be an issue. We're already distributing that as part of the admin, which is installed by default. The page could just reference /static/admin/css/fonts.css. Does a license need to be included for the rocket animation, or is that your own work? I hope the

Re: A New Design for the "Congratulations!" Page

Switching to another font is certainly an option. Is the issue with Google Fonts the Apache license versus the Django BSD license? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this

Re: A New Design for the "Congratulations!" Page

I'm not a core developer but I'd just like to say that your redesign looks amazing and is a big improvement. Even if this specific design is not acceptable I think it's a great idea to link to the tutorials/documentation from that page. I'm not a big fan of it loading the fonts from Google Fonts

A New Design for the "Congratulations!" Page

I've had the privilege of introducing Django to many people over the past several years. A recurring theme I have noticed is that once a new Django developer reaches the "It Worked!" page, the inevitable next question is, "now what?" It struck me that this page is valuable real estate for the