Hi all,

first off - to differentiate between naming content and technical
structure, I will use the following conventions:

*Content*

Rubric = a group of related subjects, e.g. "Culture"
Subject = a singular item, e.g. "Museums" or "Books"

Both "museums" and "books" are singular fields of interest, which
together usually are sorted under a main rubric called "Culture".

*Technical Structure*

Section = a grouping of written articles, no tiered navigation
possible
Topic = a grouping of written articles, tiered navigation possible (?)
Article = can belong to only one section, but several topics

This apparently is the current sorting structure of Campsite. I'd wish
it was the other way round, as logically I'd sort a site the other way
around (sections tiered, topics not necessarily tiered), because in
the backend we get only sections as a means to sort articles. That
means that any sorting I do with topics won't automatically be
represented in the backend. Also, subscriptions appear to be handled
per section, not per topic!

Now, to achieve a tiered sorting, I could duplicate the sections as
topics, e.g.

Section = Culture
Root Topic = Culture
subtopics = museums, books

I'd then need to build the navigation (and also the templates) using
only and exclusively the topics and entirely do away with the
sections. The sections, in this case, will only do some rough sorting
in the backend.

Apparently, at least I understood Slobodan that way, I would need to
build special templates for this mode of sorting. This makes me
wonder, whether e.g. such a topic-centered template would enable me to
use the "feature story", which - if I understood this correctly -
works within the section index template only. Or, the other way round,
whether a tiered navigation would inherit content properly, if I used
section and the section index template for the first tier of the
navigation and switched to topics in the second tier. Especially
interesting here seems to be the question whether content and dates
are properly inherited using this method. Or wether the tiered nav
needs to be topic centered on both tiers.

With yet another set of topics attached to articles I could then sort
them by an independent navigation (e.g. the 2-tiered horizontal and
the independent one vertical in a column) to display these articles
per different sorting. This for example should create a navigation
sorting them like

- feature stories
- editorial
- columns
- country A
- country B
- country C

This should however display all articles (past and present issues).

And lastly, the archives themselves also should be sorted in two
different ways:

- per issues (only showing the content of one issue)
- per rubric (only showing all articles belonging to the same rubric,
sorted by date)

Soooooooo ...

Right now I only want the Campsite experts here to tell me whether or
not this sort of sorting content is possible.

Please, don't throw code at me yet , as I don't understand the kind
of code you write. The code I need eventually of course, but I am
afraid you'll truly have to spell each instance out for me, I can't
work just from reading samples (yet) and reading the manual so far
hasn't helped me either. Sorry.

So, I only want to know whether or not the above can be done and
whether it will give the results I want. Because if yes, I can at
least already set up sections, root topics and topics and assign
articles correctly, even before the templates are built.

Also, such a navigation would need to be hardcoded, right? There's no
way to change it dynamically, or is there?

Cheers,

Pippa