nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is your TS Press Release Templating Strategy?

nico

I'd really appreciate any feedback in terms of a Templating strategy for typical Press Release scenarios.

It seems the typical scenario is that you have a Press Release Page made up of a Title, date, image, and large body of content.

Then you also have the Press Release's page made up of lets just say one years worth of press releases, comprised of a Title, date, and short blurb.

I would have thought one dct could feed both the Press Release page and the Press Releases page since they share a title and date at the very least.

Where this scenario does not seem to scale is when the editor simply wants to edit one press release and then they would see a years worth of press releases in the dct (okay actually from the dcr but you get it).

Your thoughts appreciated.

TS 6.7.2 on Win (not using data deploy).

Find more posts tagged with

Comments

Bowker

1 DCT for "publications"
That DCT contains fields for:
1) headline
2) long description
3) short description
4) release date
5) You can add others as your needs dictate

The Presentation has two different pieces:
1) Index page -
a) uses a search mechanism (LiveSite Content Services is one choice)
b) sorts the results by release date
c) displays block of data (1-10, 11-20...) consisting of Release date, Headline, short description
d) the headline is a link to the detail page with a parameter of which DCR to display
2) Full details
a) accepts parameter on command line to get appropriate DCR, If none given you can either redirect to index page or find the most recent one and show that.
b) display headline
c) display long description
d) present link back to index page

After dealing with this type of page for some time now, we've come to the conclusion that this same paradigm works for any publication/periodical. Press Releases is just one type of data we uses (or will shortly) this concept.

Adam Stoller

An alternative would be to handle the individual Press Release pages with DCTs (or SP Page files that reference DCRs perhaps) and push the summary data for the Press Releases into a DB - and then have your front-end take care of presenting the "index" of Press Releases to your users rather than trying to manage it on the back-end.

claudiag

I can't imagine why you'd want to make your users manage the Press Releases page manually.

Use one DCT to manage individual press releases as you've outlined, and use the front end to present a list sorted by date. The overhead will be far less on your end users, and less prone to error.

As ghoti mentions, this is a simple thing to do if you're deploying to a DB, and not much more involved if you're deploying straight XML.

Dynamic Crosstab_wip_Label.rptdesign

Rick Poulin

As ghoti mentions, this is a simple thing to do if you're deploying to a DB, and not much more involved if you're deploying straight XML.

This is also the perfect use case for LSCS, if an upgrade is in your future.

Top10MPM_Multi.rptdesign