Hey Bryan,

> So basically when I roll it out, the website would have no blogs on
> it, just a front page welcoming me and possibly displaying some
> statistics or news on it and allowing register/login.  So if I were
> the first to create an account, I would gain access to 
> www.mysite.com/bbeaudreault
> or whatever and the corresponding apps therein.  If my friend
> registered they would get the same, www.mysite.com/friend1
If you want to create a blog host, your central database model will be a
blog entry. This will contain fields for the title, the content and a
foreign key to the user model.

So the URL for a blog is something like
www.mysite.com/username/

There has to be a pattern in your urls.py which extracts the username
from the URL and passes it to a view to display the blog. More info on
URL config:
http://www.djangoproject.com/documentation/url_dispatch/

The view has to check that the username exists and if so, read all blog
entries for that user from the database and display them.

> The kicker is I want them to be able to completely customize the look
> of their blog.  From positioning of the different modules (like recent
> posts, calendar, etc being moved from left to right to top) to color
> scheme, to images on it, and of course disabling certain modules (if
> they don't want a calendar).  Sure this may be more complicated than a
> blog has to be, but these will be added over time and will present a
> nice little project for myself in adding them as I go.
> 
> I guess now that I think of it more (if I am hopefully gaining a
> better grasp), when a new user is created I would have to automate an
> adding of a new url to the urls.py file.  And I could probably store
> the resulting CSS from moving modules around, as well as flags for
> enabled/disabled modules in the DB for each user as well.
The look is defined by templates. While in most of the examples, the
templates are stored in files, nothing keeps you from storing them in
the database or generating dynamically depending on some
configuration.

HTH,
Daniel


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to