i see what you mean.
my ideas was somehow different though.
let´s say my content-area looks like this:
<div id="content">
<div class="contentbox_2column">
<div class="contentbox_2column_left">
{% block film %}1237{% endblock %}
</div>
<div class="contentbox_2column_right">
{% block star %}97{% endblock %}
</div>
</div>
<div class="contentbox_1column">
{% block banner %}{% endblock %}
</div>
<div class="contentbox_3column">
<div class="contentbox_3column_left">
{% block recent_entries %}{% endblock %}
</div>
<div class="contentbox_3column_middle">
<div class="title">a title</div>
<div class="subtitle">a subtitle</div>
<div class="body">some text</div>
</div>
<div class="contentbox_3column_right">
{% block star %}98{% endblock %}
</div>
</div>
</div>
with using dom4j (for example), i could walk through this document and have
an output like (very abstract now):
box 2 columns
left: filmblock: id=1237
right: starblock: id=97
box 1 column
banner
box 3 columns
left: recent_entries
middle: my own stuff
right: starblock: id=97
now this elements could for example be dragged around by using AJAX (which
would be cool, i think).
the difference to your suggestion is (if i´m right):
when an editor wants to create a NEW page (which should be possible), he/she
could simply "build" this page just by selecting content-boxes and
content-elements.
well, maybe i´m just thinking it wrong somehow, but your approach seems
limited to me.
patrick
>
> On 11/16/05, patrick k <[EMAIL PROTECTED]> wrote:
>> the content-ares should consist of small blocks (film, star, interview ...).
>> the site-editor should be able to MOVE these blocks around (change the
>> position of the block), EDIT the block (e.g. assigning a different film-ID)
>> and DELETING the block. this should be done within the ADMIN-INTERFACE (not
>> touching any code).
>
> Hi Patrick,
>
> Welcome to the Django community -- thanks for the introduction. :)
>
> What you're describing is definitely possible with Django. We've
> solved that exact problem on lawrence.com and ljworld.com, which have
> been powered by Django for some time now. I assume this presentation
> "moving" would be limited to the home page, right? If so, here's the
> strategy I'd recommend:
>
> Create a "home page" object, which would just store the presentation
> decisions for the home page for a given date/time range. This could be
> editable in the admin. Then just write a view that grabs the
> appropriate home page object and renders the home page.
>
> Alternatively, if every page of your site has *separate* logic about
> presentation, which is required to be editable in the admin, then
> you'll want to create a "page" model, which has foreign keys to the
> types of content it's displaying, a field for the URL, and fields
> representing the order.
>
> This is a bit hard to explain, but I hope this has helped.
>
> Adrian
>
> --
> Adrian Holovaty
> holovaty.com | djangoproject.com | chicagocrime.org
