If your intention here was to suggest something that you think
Django's website should cover, then this *is* the right forum.
However, my reponse would be to ask what is wrong with the overview
that is already there? The front page of Django's website gives a 1
paragraph summary, with a link to a longer overview page:
https://docs.djangoproject.com/en/1.3/intro/overview/
We've also kicked around the idea of writing up some "Django for
non-techs" guides -- the sort of thing you might give to a manager or
boss to convince them that Django is worth adopting. We don't have
anything to show for this, but if you (or anyone else) is interested
in volunteering and has skills in copywrighting and design, this could
be a valuable contribution.
Yours,
Russ Magee %-)
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-develop...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
Hi Julian,
If your intention here was to suggest something that you think
Django's website should cover, then this *is* the right forum.
However, my reponse would be to ask what is wrong with the overview
that is already there? The front page of Django's website gives a 1
paragraph summary, with a link to a longer overview page:
https://docs.djangoproject.com/en/1.3/intro/overview/
We've also kicked around the idea of writing up some "Django for
non-techs" guides -- the sort of thing you might give to a manager or
boss to convince them that Django is worth adopting. We don't have
anything to show for this, but if you (or anyone else) is interested
in volunteering and has skills in copywrighting and design, this could
be a valuable contribution.
I don't think Russell is looking for votes on whether to do it, he's
looking for someone to actually do it :)
Cheers
Tom
Cheers
Tom
https://docs.google.com/document/d/15iJXXKs989cIIvhToa7ttYgToPSyzJN9KL9CCkxka1o/edit?pli=1&hl=en_US
On Wed, Aug 24, 2011 at 6:31 AM, Cal Leeming [Simplicity Media Ltd]
<cal.l...@simplicitymedialtd.co.uk> wrote:
>
>
> On Wed, Aug 24, 2011 at 11:04 AM, Tom Evans <teva...@googlemail.com>
> wrote:I'll
--
Justin Holmes
Head Instructor, SlashRoot Collective
SlashRoot: Coffee House and Tech Dojo
60 Main Street
New Paltz, NY 12561
845.633.8330
https://docs.google.com/document/pub?id=15iJXXKs989cIIvhToa7ttYgToPSyzJN9KL9CCkxka1o
Well said. Language like that goes on anything officially-Django only
over my dead body.
I'm appreciating the effort y'all are putting onto a good high-level
description of Django, but let's stay FAR away from anything that's
derogatory, OK? If Django's as good as we say it is we shouldn't have
to put down other tools to promote ours.
Just so you know, there's an effort underway right now within the DSF
to refresh Django's web presence, so if you come up with something
good here there's a good chance we'll actually end up using it. So --
no pressure :)
Jacob
One thing I always like about django is how the community is peaceful and how the django itself is peaceful and engineer-minded,
not marketing-minded:
There are many big and well-known sites built with django and I think mentioning these sites and providing testimonials from people working on these sites can be better advertisement.
2011/8/25 Mikhail Korobov <kmi...@googlemail.com>
There are many big and well-known sites built with django and I think mentioning these sites and providing testimonials from people working on these sites can be better advertisement.
Yes and no. Advertising on big websites & applications powered by django would be a plus but it can be misleading. I think anybody could agree that this same applications could have been done in PHP or Flask with the same success (see Facebook ?).
Engineers and people that take decisions in general want to know if it gets things done, but also how does it compare to other solutions.
Comparing on features would be more engineer-minded that «How do you feel about Django». Engineering is not about feelings, it's a complex choice that weights pros & cons which can be technical but also social and commercial...
In javascript world is common to compare frameworks based on speed, size, we could extend this to common problems regarding website building like cache management, authentication, authorization, L10N, I18N, db support, professional support, community support and the like... and even do code to code comparison if it makes sens.
I also love the vibe of the django community. I did not mean, when
writing that line, to put down other communities; I was glad when I
found Django to be greeted by language that did not put down other
frameworks or their philosophies. Nevertheless, I think that the
language in question is an empirically testable and true statement.
The inverse is also true: Some frameworks, for some use cases, have
distinct and measurable advantages over Django.
I'm not defending the language as it's written - by all means let's
change it. However, I do think that it's worth mentioning, somehow,
that Django excels in certain areas and that those areas are largely
the result of sensible underlying philosophies. I think that this
point answers a front-running question in the mind of project managers
who are considering framework adoption.
why not the wike?
--
regards
Kenneth Gonsalves