Re: Django Admin Revamp - Any updates?

[Brett H]

Now that django is on github the best thing that could happen is to
set it free and split it out as a separate django-admin repository
that people can build on, and making site something like site =
load_admin_site(settings.ADMIN_SITE) so that people can do drop in
replacements. Not just that but splitting out the templates and static
assets into a django-admin-originaltheme repository.

In this fashion projects like grappelli can proceed in an opinionated
fashion on making changes to the admin as they see fit but remaining
compatible with the ModelAdmin specifications, and django can pull
back in the consensus commits. Grappelli does a lot of things right,
but now I'm wanting to drop twitter bootstrap in on top of it, and
tomorrow something else might be flavour of the month.

Increasing the flexibility for development and integration is more
important than trying to 2nd guess where we are going to be in 5 years
time.

On Apr 29, 6:13 am, Idan Gazit  wrote:
> As I wrote, I'd like to have a clear idea of what a new admin will accomplish 
> before starting to bolt on enhancements, even great enhancements like 
> grappelli.
>
> The admin was an impressively future-proof design, given that it is still so 
> useful years after it was designed. We should aim to make an admin that will 
> be relevant and useful five years from now; we can't design for that without 
> a couple of clear, simple goals. Grappelli may or may not align with those 
> goals.
>
> -I
>
>
>
>
>
>
>
> On Saturday, April 28, 2012 at 12:55 AM, Daniel Sokolowski wrote:
> > On that note, why can't the fruits of Grappelli be used as a starting point?
>
> > -Original Message-
> > From: h3
> > Sent: Friday, April 27, 2012 4:01 PM
> > To: Django developers
> > Subject: Re: Django Admin Revamp - Any updates?
>
> > I don't know the status of this project, but my guess is that you
> > shouldn't hold your breath for it.
>
> > Fortunately, there is Grappelli:
> >https://github.com/sehmaschine/django-grappelli
>
> > We are currently working on making it compatible with django 1.4 (see
> > the "grappelli_2_4" branch)
>
> > Alternatively the branch on my fork works pretty well with 1.4:
> >https://github.com/h3/django-grappelli/tree/grappelli_2_4
>
> > Cheers
>
> > On Apr 26, 7:06 pm, Victor Hooi http://gmail.com)> 
> > wrote:
> > > Hi,
>
> > > Is there any news on the Django Admin rewrite front?
>
> > > I remember around a year ago, there was quite a bit of talk on revamping
> > > the Django admin UI - I think Idan Gazit was heading that, right?
>
> > > Is that still on the Django roadmap? Any idea of whether it'll be in 1.5,
> > > 1.6, 1.7 etc?
>
> > > Cheers,
> > > Victor
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com 
> > (mailto:django-developers@googlegroups.com).
> > To unsubscribe from this group, send email to
> > django-developers+unsubscr...@googlegroups.com 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > For more options, visit this group at
> >http://groups.google.com/group/django-developers?hl=en.
>
> > Daniel Sokolowski
> > Web Engineer
> > Danols Web Engineering
> >http://webdesign.danols.com/
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com 
> > (mailto:django-developers@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > django-developers+unsubscr...@googlegroups.com 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > For more options, visit this group 
> > athttp://groups.google.com/group/django-developers?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Adnane Belmadiaf]

Yeah sorry about that, i wasn't sure my email was sent.

2012/4/30 Dana Woodman 

> You already posted that earlier today Adnane.
>
> --
> Dana Woodman
> d...@danawoodman.com
> http://www.danawoodman.com
>
> On Sunday, April 29, 2012 at 12:25 PM, Adnane Belmadiaf wrote:
>
> Hi all,
>
> I would like to introduce myself, here is my proposal
> http://i.imgur.com/bnf2e.png
>
> Best,
> Adnane Belmadiaf
>
> 2012/4/29 Juan Pablo Martínez 
>
> http://imgur.com/a/186fh
> nice :)
>
> On Sun, Apr 29, 2012 at 4:07 PM, Giovanni Collazo wrote:
>
> I liked what Dana Woodman did, so I did a design based on that.
>
> Here: http://imgur.com/a/186fh
>
> --
> @gcollazo
> gcoll...@24veces.com
>
> On Sunday, April 29, 2012 1:32:13 PM UTC-4, Dana Woodman wrote:
>
>  This is my take: 
> http://cl.ly/**0U2C1O20133i0U3d1s3X/o
>
> --
> Dana Woodman
> d...@danawoodman.com
> http://www.danawoodman.com
>
> On Sunday, April 29, 2012 at 9:23 AM, Alec Taylor wrote:
>
> Here is a design I just pulled up: http://i.imgur.com/wIkel.png
>
> Thoughts?
>
> On Mon, Apr 30, 2012 at 1:34 AM, Alec Taylor 
> wrote:
>
> Contact me for UX once you have forked the repo, I'll throw something
> up and place it on the wiki (or in an issue) of that new repo.
>
> Email: alectayl...@gmail.com
>
> On Sun, Apr 29, 2012 at 10:33 AM, Dana Woodman 
> wrote:
>
> Great info Russ, thanks!
>
> My thoughts at this point would be to focus on the main content sections,
> including the home page and documentation overview pages.
>
> For the home page I'd see something like this working well:
>
> -Logo and brief project description (fork on Github as well?) - Answers the
> "What is Django?" and "Why should I care?" questions. (for example, Twitter
> Bootstraps's home page: 
> http://cl.ly/**3R0d1X300S0S0f0A0j0S
> )
> Link to download and docs - Answers the "How can I start?" question
> "Who uses Django?" section - Answers, well... the "Who uses Django?"
> question. BTW, is there a reason that there isn't more of the larger users
> of Django on here?  Eg Disqus, Instagram, Pinterest, Google, Mahalo,
> addons.mozilla.org, etc... This alone would get people excited to use
> Django
> and would convince a lot of the business types that Django can scale and is
> worth the investment.
> A graphical site navigation area, eg: 
> http://cl.ly/**3B1N2h3E2x3x0f3V091K-
> Give people a an easy way to get around to the core content on the site.
>
>
> Thinking a layout along the lines of Node.js (http://nodejs.org/) homepage
> would be effective. Node does a good job of keeping things minimal and easy
> to navigate.
>
> Some sort of "blogroll" type feature would satisfy the need to update the
> community of interesting or useful links. This could work in concert with
> the documentation as well. Not sure what the exact needs for this are, what
> would be an ideal process for this?
>
> How would the style guide be presented? Would it be a page on
> djangoproject.org, Github Wiki, a PDF, or...?
>
> I assume it would be fairly straightforward to give Spinx a new skin?
>
> Do you feel an incremental approach would be best or should it be a
> complete
> overhaul in one go?
>
> --
> Dana Woodman
> d...@danawoodman.com
> http://www.danawoodman.com
>
> On Saturday, April 28, 2012 at 4:49 PM, Russell Keith-Magee wrote:
>
> Hi Dana
>
>
> On Sunday, 29 April 2012 at 1:45 AM, Dana Woodman wrote:
>
> Very true Chris. I'd love to see the documents that were put together when
> this was discussed last time, if they're still around.
>
> I've included the design brief in my response to Ned. If you're looking for
> something else in particular, let me know and I'll see if I can find (or
> produce) something that is suitable.
>
>
> In regards to what needs improvement, there are some core issues as I see
> it.
>
> 1) the home page does a poor job of conveying what someone should do if
> they
> want to try out Django. It also could do a much better job of making Django
> a bit more "sexy".
> 2) the documentation itself, while thorough, is a bit difficult to
> navigate,
> especially for new users. I think this could be partially remedied by some
> modifications to headers and color choices.
> 3) the project could do a better job of selling itself, especially in
> regards to showcasing why it is so great: automatic admin, large active
> community and plugins, large sites and organizations using it, active
> development, lots of built in security, etc...
> 4) it just looks old and outdated, which is a problem in its own right.
>
> Should I just fork the project on Github and hack away or do I need to work
> on subversion?
>
> As of yesterday, we are a SVN-free organisation -- everything is on GitHub.
> However, djangoproject.com has been on GitHub for a while:
>
> https://github.com/django/**djangoproject.com
> If you want to work on code directly, that's the pl

Re: GitHub migration done!

[Daniel Sokolowski]

Adrian, excellent job and thank you! Curious what five open-source on 
Subversion you are referring to?


-Original Message- 
From: Adrian Holovaty

Sent: Friday, April 27, 2012 11:08 PM
To: django-developers@googlegroups.com
Subject: GitHub migration done!

On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty  
wrote:

We're going to do the migration to GitHub today. This means we'll no
longer be committing code to our Subversion repository. Committers,
please hold off on making commits until the migration is done.


OK, it's live!

https://github.com/django/django

A few quick points (though this definitely deserves a more in-depth 
writeup):


* I renamed the old (mirror) repository to
https://github.com/django/django-old. We had talked about deleting it
outright to avoid confusion, but I realized at the last minute that
doing so would have deleted all the pull requests. I didn't want to
throw all of that out, and I think we can figure out a way to use
those pull requests in the new repository.

* I only migrated trunk (now called "master"), rather than including
all of the branches. This was the result of a bunch of discussion on
IRC with Brian R., et al. The thinking is that it kept the migration a
lot cleaner/simpler, and we can always add branches later. Of course,
we'll need to create the latest release branches. Otherwise, we can
consider the SVN branches on an individual basis.

* As expected, all forks of the old repository are now broken. Can
somebody volunteer to write some documentation on how to upgrade your
old fork to use the new upstream repo (rebase? simple patch?)?

* We're going to keep the Subversion repository around indefinitely,
but it'll no longer be updated.

* We're going to keep using Trac for tickets, but pull requests on
GitHub are also welcome.

* Clearly there are lots of bits of process that need to be updated
now, from the django-updates mailing list to our "contributing"
documentation, etc. We'll take care of all of that in the coming days,
and we should all expect some degree of confusion and unsettlement in
the community. That's totally fine, and we'll get through it. :-)

* Finally, big thanks to the folks on IRC today who helped me through
the process and contributed good ideas.

I'm planning to write up a blog post on how the process went, for the
benefit of the five open-source projects still using Subversion.

Adrian

--
You received this message because you are subscribed to the Google Groups 
"Django developers" group.

To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.



Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/ 


--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django Admin Revamp - Any updates?

[Idan Gazit]

On Monday, April 30, 2012 at 10:16 AM, Brett H wrote:

> Increasing the flexibility for development and integration is more
> important than trying to 2nd guess where we are going to be in 5 years
> time.

Fair enough, but that sort of flexibility is available now. Nothing is 
preventing you from starting your 3rd-party admin app today.



The issue is Django's officially-blessed, officially-documented admin. I'm not 
sure it's better to have admin in contrib (or contrib at all, but that's a 
separate ball of wax). I have a feeling that this issue will probably be 
addressed once again now that we're on github.

All the same, if there's going to be an official django admin, I'd like it to 
give some thought to the issues I've raised. I have no problem (read: would 
love) to draw upon existing solutions for an admin revamp, but right now I 
don't have a fitness function to guide my decisions, and I think that is 
necessary. Not a spec, just an attempt to step back and think about what the 
admin should do.

-I


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Idan Gazit]

Lovely to see fresh talent and energy applied to a long-stalled issue. :)

I think Giovanni's proposal has a strong, simple page structure, and it does a 
good job of IA for our varied audience. Putting on my BDesignerFL hat, let's 
use that as a starting point.

Let's set aside the issue of restyling docs for now; we can't run in all 
directions at once.


Homepage Structure
===


News


The major element elided from the proposal is some display of news. The current 
homepage shows the most recent four entries; I think one is sufficient for the 
homepage, but it does need to be somewhere on the page.


Header nav


There is no header nav in the proposal. I'd like to have some minimal list of 
primary nav links, like the ones at the top-left of the page fat-footer. On the 
homepage, they can appear very de-emphasized, I like the spare look of the 
masthead and I don't want to break that by boxing it in with a visual bar from 
above.


Header actions
~~~

While I like the "quick start" mechanic, those buttons require some love:

* There's no obvious "get django" or "download" call-to-action. "Quick start" 
is good but we're burying the download information in there.
* The quick start drawer doesn't make mention of the other ways you can get 
Django, for example downloading a tarball or a link to github.
* There's no quick display of our most recent released version. It belongs 
somewhere at the level of these buttons.

My proposal is a button layout like:

[ Get Django 1.4  v ]  [ Quick Start v ]  [ Documentation ]

The get-django button can show a drawer like quick start, but show the three 
common routes (pip, tarball, github) and supply a link to a page with more 
details if need be.


Who's Using Django
~~~

I don't know if we'll have case studies. If not, an attractive display of some 
logos wouldn't go badly. If we do, then we can fade out the other logos upon 
click and show a bit of teaser text about the company with a link to "read 
more…"


Footer
~

I like the structure. Need to give some thought to the six large elements and 
make sure they're the best choices for what to show there.


Responsive Structure


A requirement for the new dp.com is that it be responsive or adaptive. I'm not 
going to get hung up on the technicalities—something which looks and works well 
on a variety of common screen geometries. The proposed page layout would 
linearize well for smaller screens, which is excellent.




Non-homepage templates
===

I'm not sure what other pages we have in our current site, ignoring trac for 
now. I suspect that we'll need one or two templates for non-home pages.



Look & Graphic Design
=

I don't want to get off course with the IA work. Color and design stuff can 
wait until we're feeling that the structure is mostly baked.

If you have ideas and you want to get them down, I'd recommend you make 
something like style tiles (http://styletil.es/).




Thanks all for your brains on this matter. I am excited to see this underway, 
and I can't wait to see what comes next. :)


 -I

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Jacob Kaplan-Moss]

On Monday, April 30, 2012 at 3:41 PM, Idan Gazit wrote:
> Non-homepage templates
> ===
> 
> I'm not sure what other pages we have in our current site, ignoring trac for 
> now. I suspect that we'll need one or two templates for non-home pages.
> 
> 
> 


Docs are the big one -- more than half of the traffic to djangoproject.com is 
to the docs site. A good docs layout and theme that fits into the rest of the 
site is a pretty big deal IMO.

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Christian Metts]

As of the previous failed attempts to make something happen here I
want to get what I have out here for everyone to consider/use/ignore
as desired:

First some images of where I got:
http://dl.dropbox.com/u/10320/djangoproject/dp.com-home.png
http://dl.dropbox.com/u/10320/djangoproject/homepage-scrolled.png
http://dl.dropbox.com/u/10320/djangoproject/documentation.png

And my illustrator source file. The font I was using for almost
everything was Adelle which is available from typekit and possibly
other places.
http://dl.dropbox.com/u/10320/djangoproject/dp.com.xian.redesign.ai

IA wise:
* My plan was for a simple top nav that could be minimized further on
interior pages.
* sections of the site could such as the homepage could be fairly long
and use a side nav that followed/showed your location similar to:
http://bonsaiden.github.com/JavaScript-Garden/ (see second screenshot)
* The homepage could have a couple of places for time based updates up
in the banner/nav area. In my screen shot it shows a few blog post
titles and upcoming events.

while I completely stalled out I'm totally excited about DP getting a
much needed refresh and growing further.

glhf!

—Xian

On Apr 30, 3:41 pm, Idan Gazit  wrote:
> Lovely to see fresh talent and energy applied to a long-stalled issue. :)
>
> I think Giovanni's proposal has a strong, simple page structure, and it does 
> a good job of IA for our varied audience. Putting on my BDesignerFL hat, 
> let's use that as a starting point.
>
> Let's set aside the issue of restyling docs for now; we can't run in all 
> directions at once.
>
> Homepage Structure
> ===
>
> News
> 
>
> The major element elided from the proposal is some display of news. The 
> current homepage shows the most recent four entries; I think one is 
> sufficient for the homepage, but it does need to be somewhere on the page.
>
> Header nav
> 
>
> There is no header nav in the proposal. I'd like to have some minimal list of 
> primary nav links, like the ones at the top-left of the page fat-footer. On 
> the homepage, they can appear very de-emphasized, I like the spare look of 
> the masthead and I don't want to break that by boxing it in with a visual bar 
> from above.
>
> Header actions
> ~~~
>
> While I like the "quick start" mechanic, those buttons require some love:
>
> * There's no obvious "get django" or "download" call-to-action. "Quick start" 
> is good but we're burying the download information in there.
> * The quick start drawer doesn't make mention of the other ways you can get 
> Django, for example downloading a tarball or a link to github.
> * There's no quick display of our most recent released version. It belongs 
> somewhere at the level of these buttons.
>
> My proposal is a button layout like:
>
> [ Get Django 1.4  v ]  [ Quick Start v ]  [ Documentation ]
>
> The get-django button can show a drawer like quick start, but show the three 
> common routes (pip, tarball, github) and supply a link to a page with more 
> details if need be.
>
> Who's Using Django
> ~~~
>
> I don't know if we'll have case studies. If not, an attractive display of 
> some logos wouldn't go badly. If we do, then we can fade out the other logos 
> upon click and show a bit of teaser text about the company with a link to 
> "read more…"
>
> Footer
> ~
>
> I like the structure. Need to give some thought to the six large elements and 
> make sure they're the best choices for what to show there.
>
> Responsive Structure
> 
>
> A requirement for the new dp.com is that it be responsive or adaptive. I'm 
> not going to get hung up on the technicalities—something which looks and 
> works well on a variety of common screen geometries. The proposed page layout 
> would linearize well for smaller screens, which is excellent.
>
> Non-homepage templates
> ===
>
> I'm not sure what other pages we have in our current site, ignoring trac for 
> now. I suspect that we'll need one or two templates for non-home pages.
>
> Look & Graphic Design
> =
>
> I don't want to get off course with the IA work. Color and design stuff can 
> wait until we're feeling that the structure is mostly baked.
>
> If you have ideas and you want to get them down, I'd recommend you make 
> something like style tiles (http://styletil.es/).
>
> Thanks all for your brains on this matter. I am excited to see this underway, 
> and I can't wait to see what comes next. :)
>
>  -I

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

[Vinay Sajip]

On Apr 28, 4:08 am, Adrian Holovaty  wrote:

> * We're going to keep the Subversion repository around indefinitely,
> but it'll no longer be updated.

That means that any mirrors using that repository as a source are also
not worth using any more. There's the official BitBucket Mercurial
mirror of Django:

https://bitbucket.org/django/django/

Is that going to be changed to be a mirror of the GitHub repo, or will
it disappear altogether?

Regards,

Vinay Sajip

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

[Carl Meyer]

Hi Vinay,

On 04/30/2012 07:11 PM, Vinay Sajip wrote:

On Apr 28, 4:08 am, Adrian Holovaty  wrote:


* We're going to keep the Subversion repository around indefinitely,
but it'll no longer be updated.


That means that any mirrors using that repository as a source are also
not worth using any more. There's the official BitBucket Mercurial
mirror of Django:

https://bitbucket.org/django/django/

Is that going to be changed to be a mirror of the GitHub repo, or will
it disappear altogether?


Good point. I think which of those happens now depends on whether a 
motivated someone steps up to figure out how to convert the mirror to 
use hg-git and source from Git, and then maintain it as needed. I 
originally did the current mirror, and it really hasn't needed any 
maintenance over the past two years, but I no longer use Mercurial or 
the Mercurial Django mirror, so that "motivated someone" is not likely 
to be me this time around.


Carl

--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Julien Phalip]

Hi everyone,

It's really exciting to see the community offering to help in this
endeavor. I myself spent quite a bit of time last year driving a
redesign effort for djangoproject.com, so I thought I'd share my work
with you now while the momentum is picking up again.

So, using some initial briefing and feedback from Russell, Jacob, Idan
and Christian, I had designed a new IA and then built a working
prototype:

http://www.djangoproject.dotcloud.com/
Login details: preview/ihud8t4k

I'd like to emphasize that this is a *prototype*. The visuals were
intentionally left rough and unpolished, and even the IA itself was a
work in progress. I've seen many great ideas so far in this thread, so
please feel free to rip this prototype off, or to just get some
inspiration from it, or to simply ignore it altogether.

Technically-speaking, the front end uses Sass and Compass and it
implements the responsive Less framework [1]. To see an example of the
responsive behavior, try resizing your browser window on the homepage
[2]. I had also spent a lot of time tweaking the documentation's
layout and styles to make it easy to view across screen sizes [3]. For
example, the sidebar collapses into a clickable button on small
screens. Another example is with large images as in [4]; as the window
gets smaller, the image shrinks along with the window and becomes
clickable on small screens — this is to allow mobile users to access
the full-width image without breaking the layout. However, will all
that said, it might eventually be worth considering to move the
documentation entirely to RTD one day (with some special branding).

The prototype's code is available on github [5]. I hope this is of
some help to the person or team that will be driving this project.

Kindly,

Julien


[1] http://lessframework.com/
[2] Prototype homepage: http://www.djangoproject.dotcloud.com/
[3] Documentation prototype: http://docs.djangoproject.dotcloud.com/en/dev/
[4] 
http://docs.djangoproject.dotcloud.com/en/dev/internals/contributing/triaging-tickets/#triage-workflow
[5] Prototype's code: 
https://github.com/jphalip/djangoproject.com/tree/visual-redesign

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Joe Tennies]

A lot of these mockups are good, but I have a couple comments.

I'd like to see more "interesting" grid layout. Django comes from the world
of newpapers. I think that should be honored with an power 12/16 column
layout. I'm seeing something like "Power Grid" from
http://designshack.net/articles/layouts/10-rock-solid-website-layout-examples
Other prior art to look at:
http://demos.dojotoolkit.org/demos/fonts/demo.html
I think http://dl.dropbox.com/u/10320/djangoproject/dp.com-home.png did a
decent job of this. I love the sections on the top looking like sections of
a newspaper.


Another thing I like to see in every decent site is something to direct
people into where they want to get by categorizing them. I'm seeing
sections like "Considering Django" w/ the sales pitch, case studies, who
uses it, etc. I'll have to think about how to categorize the rest, but I am
usually annoyed by ending up on someone's site and not exactly knowing
where to go.

I've been messing with Adobe Proto lately. I'll see if I can put more
showin' and less jibber-jabberin' ;)

- Joe Tennies

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Redesign of djangoproject.com?

[Alec Taylor]

The http://proxart.co/ design on that page is quite a good one

On Tue, May 1, 2012 at 2:50 PM, Joe Tennies  wrote:
> A lot of these mockups are good, but I have a couple comments.
>
> I'd like to see more "interesting" grid layout. Django comes from the world
> of newpapers. I think that should be honored with an power 12/16 column
> layout. I'm seeing something like "Power Grid" from
> http://designshack.net/articles/layouts/10-rock-solid-website-layout-examples
> Other prior art to look at:
> http://demos.dojotoolkit.org/demos/fonts/demo.html
> I think http://dl.dropbox.com/u/10320/djangoproject/dp.com-home.png did a
> decent job of this. I love the sections on the top looking like sections of
> a newspaper.
>
>
> Another thing I like to see in every decent site is something to direct
> people into where they want to get by categorizing them. I'm seeing sections
> like "Considering Django" w/ the sales pitch, case studies, who uses it,
> etc. I'll have to think about how to categorize the rest, but I am usually
> annoyed by ending up on someone's site and not exactly knowing where to go.
>
> I've been messing with Adobe Proto lately. I'll see if I can put more
> showin' and less jibber-jabberin' ;)
>
> - Joe Tennies
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: GitHub migration done!

[Vinay Sajip]

On May 1, 2:19 am, Carl Meyer  wrote:
>
> Good point. I think which of those happens now depends on whether a
> motivated someone steps up to figure out how to convert the mirror to
> use hg-git and source from Git, and then maintain it as needed. I
> originally did the current mirror, and it really hasn't needed any
> maintenance over the past two years, but I no longer use Mercurial or
> the Mercurial Django mirror, so that "motivated someone" is not likely
> to be me this time around.

I don't mind doing it, if it's sufficiently low-maintenance, and I do
use Mercurial as well as Git. Did you implement it using a local repo
and a cron job, or was there something else you used which was more
purpose-built?

Regards,

Vinay Sajip

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.