Let me know if any of this sounds too weird and requires a
swift kick in the head. Consider this the journal entries of
a madman...or someone trying to grasp the posibilities of
Midgard. You choose.:


Our new home page has three major content sections,
highlighting breaking/lead stories, regular features, and
etc.

The site is currently up (componetized, but static only for
now) via Midgard at: http://web03.radiodigest.com. (Code
still needs tweaking for the Windows platform.) (By the way,
the current live site is at http://radiodigest.com.)

�

In Content Admin, I have three basic topic trees set up,
each with subtopics:

Markets (Our 40+ radio markets we cover, like San Francisco,
New York, etc.)

Features (Columnists, profiles on personalities, etc.)

Departments (About Us stuff, privacy policy, newsletter
registration, etc.)

�

Don't forget that there are home pages for each market. An
example is
(again, just a static page right now)
http://pittsburgh.radiodigest.com. The home page has to be
able to feature whatever we want across all the markets and
features.

First challange is coding the articles in such a way (and
with the proper
PHP code) that determines where the article goes. ("Today in
RadioDigest.com", "Other Articles", "Regular Features..."
etc.)

Also the editor needs to be able to choose how the articles
are ordered.

I was thinking about using IDs to determine placement and
Score to determine wether a document is to be displayed and
in what particular order (in addition to just plain "newest
first").

Also, for the Extra's I thought about this:

Extra 1: Byline
Extra 2: next article ("page") link for those articles too
long for one
page.
Extra 3: Link to a relevant conference in a message board.


An example would be: If I wanted a blurb to appear in the
"Today in
RadioDigest.com" box as a highilght (link in the list of
links) then I would code it as 4 and 2. That would be 4th
row of the page, and 2nd column. I could even use the third
digit to designate what specific area in row 4,  column 2.
It would then be 4, 2, 2. Like 1 for LEAD story, and 2 for
highlights (list of links).

So I would design some PHP code to scan the three major
topic trees:


"Read through topic tree's designated to find current (non
date expired
articles)."

"If the score is zero, skip it, else..."

"Read IDs to determine placement."

"If first number in ID is 4, and second figure is 2 , and
third figure is 1,
then post blurb, and pull the picture URL from...(one of the
Extra's
perhaps?)"

"While count does not equal 7..."

[Insert ordering mechanism based on score # assigned.]

"If first number in ID is 4, and second figure is 2, and
third figure is 2,
then post title and link."

And then on through all the sections...

You get the picture...

I'm thinking that scanning through the topic tree's once is
better than scanning three or four times just for one page.�
However, it sounds like HUGE code to me.

�

And the question comes up...If I'm highlighting something on
the main home
page via date and score, etc., then how do I control expiry
and placement on one of the market home pages, which may be
different? What ages off of the main home page doesn't
necessary mean it should age off the market home page.


Last question. Is "approval" of articles something that I
need to enable (just like Score) in PHP code myself?


Thanks...I'm checking my sanity.


Todd Daniel Woodward
Technical Consultant
RadioDigest.com Inc.

http://radiodigest.com

     "Radio you can READ!"

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]

Reply via email to