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; } } }

Event Template Strategy

nico

I am trying to come up with a strategy so my biz users can create company event pages within teamsite. Events are made up of an info, agenda, contact, and optional registration and bio's pages.

My dilema is if there are multiple events, what would be the best strategy in terms of templating?
one form with multiple presentation templates?
but then how do you handle navigation linking (assuming this may be hardcoded in your tpl?) to your info, agenda and other pages? the names would need to be unique so as not to overwrite i.e. agenda.asp in another event.

I guess I could require them to create a unique directory within the "events" directory to start from each time but I was trying to avoid that requirement from them.

Thanks,
Nico

Find more posts tagged with

Comments

reddyl

How about tagging the event DCR's with event name as a metadata to distinguish event's.

Adam Stoller

Events are made up of an info, agenda, contact, and optional registration and bio's pages.

My dilema is if there are multiple events, what would be the best strategy in terms of templating?

What are the commonalities between events that need to be retained? E.g.:

just because multiple events have the same contact doesn't necessarily link them
dates are most likely used for sorting in terms of presentation, but doesn't necessarily link events to one another either
bio pages might be something that should be commonly linked though

The more details you can provide regarding the project - the better chance you have of (a) figuring out how to do this yourself and/or (b) getting informed suggestions from the masses.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

axis_sample.rptdesign