On Sat, Jul 9, 2011 at 9:19 AM, Josh <jos.carpente...@yahoo.com> wrote:

> I want to switch my sites from Drupal to Django. I already read a lot
> about Django and made a few sample apps. I think Django is better
> suited to my needs, but I do have a few questions that I couldn't find
> an answer for. So I thought of a few solutions that might do the
> trick. <snip>



> I'm not really a web designer or a programmer, <snip>


Then stick with Drupal.

Drupal is a CMS. Django is a framework. There's a *big* difference.


> so the
> terminology I use might be wrong.Some hints, references to sample-apps
> (so I can look at the code) or other resources on the internet are
> welcome.
>
> 1. URL generation
> The sites will have a substantial number of pages that will be
> generated. The content is stored in a database. I was thinking of
> creating a seperate table for page-names. E.g.
> pagename - database_id ( page-about-something.htm, id12345 ; category/
> page-about-something.htm, id12345).
> I'll store these in a dictionary (name:, database_id) and use this to
> avoid duplicate names and keep track of already present names. This
> way I can also alias pages.
> Basically this is a question about how to handle a large number of
> different pages?
>
> 2. Layout of webpages - main content area
> I think I understand the templating system of Django. In Drupal there
> are a lot of ways to generate layouts and depending on the content
> ( areas such as head, above-content, content, left-column, right-
> column etc can be defined and depending on the context blocks of
> content can be displayed). The header/footer part isn't that
> difficult, but I'm having problems how to do the main content area.I'm
> not sure how to do this in Django (or start with it).
>
> For example:
> main content area
> - frontpage 3 columns with different components (widgets/blocks) in
> each column
> - normal page 2 columns (but may contain different outcomes depending
> on content)
> -- main content area
> -- column with different components (widgets, blocks)
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

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

Reply via email to