Sent by Tony Byrne - CMSWatch on 5 January 2004 21:09
Howdy folks-
Experienced CMS hands may wish consider applying to speak at the Gilbane
Conference to be held late March in Los Angeles, Calif., USA.
http://www.gilbane.com/CM_conference_LA_04.html
I'm chairing a new "technology" track -- which we may expand in a future
event after testing the waters in L.A. The purpose of the technology
track is to explore cross-cutting themes of interest to CMS & DAM
architects and developers regardless of the product they're
implementing.
We're presently vetting solution-neutral speakers from consulting and
end-user communities for this track. ***Appended to this message
you'll find a list of the specific topics we seek to address.*** We
think this represents a core of typical "hard problems" in major CMS
implementations, but remain open to other speaking ideas proposed in a
similar vein from experienced consultants.
If interested, please review carefully the session descriptions below
and reply directly to me by Tuesday January 13th, since we're looking to
firm up the roster by the end of this month. The application process is
fairly informal: ~100 word abstract plus outline. Draft presentations
will be due in late February. Target 20-25 minutes in length.
Note to CMS vendors: please feel free to refer suitable end-users to
apply.
Many thanks,
--------------------------------------------
Tony Byrne
Founder, Principal
CMSWatch http://www.cmswatch.com
Silver Spring, MD USA
V: 301-585-7004
[EMAIL-REMOVED]
"Content Management Matters"
***********************
Technology Track
T1. CMS Impacts on Systems, Networks, and Security
In considering content management system design, many enterprises
examine the impact on developers and editors. But system and network
administrators -- often brought into CMS projects belatedly -- are
significantly affected too. Learn in advance how a content or asset
management project is likely to place new demands your systems,
networks, and security infrastructure, so you can plan early for
success.
--------------------------------------------------------------------
T2. Content Delivery - The Devil is the Deployment
Synchronized content deployment -- of data, documents, and media -- from
a management environment to a delivery environment is perhaps the
technically most demanding task of any content management system. Not
surprisingly, this is where many CMS projects fail to live up to
expectations. Learn how to properly architect this challenging task.
--------------------------------------------------------------------
T3. So You Want a Metadata-Driven Website?
Information Architects quite properly point out that solid metadata lies
at the heart of any major content management system aspiring to reap the
business benefits of greater content reuse and findability. But using
metadata to drive navigation, content channels, search, and display can
be deceptively tricky and complicated, and will confront the developer
with some fundamental architectural choices. Learn different approaches
to harvesting, storing, and using metadata for maximum return.
--------------------------------------------------------------------
T4. How CMS Products Address Templating
A templating engine traditionally lies at the core of any Web CMS
product. But different products approach templating in very different
ways. Some are technically easier but less robust than others. Certain
templating systems may implement faster but risk greater vendor lock-in.
Join us for a tour of some archetypal approaches.
--------------------------------------------------------------------
T5. Using Web Services to Improve Content Management
In theory, Web Services should solve thorny asset and content management
interoperability problems. In practice, early results from the field are
mixed. Not surprisingly, Web Services is not a universal panacea.
Nevertheless, there is some low-hanging fruit for those who architect
carefully.
--------------------------------------------------------------------
T6. What Constitutes XML Compliance?
Nearly all CMS and DAM systems claim they are XML compliant, because
they use or can output XML in some form or another. But different
packages leverage XML in very different ways. What should a buyer really
look for? Come away with a checklist for how to evaluate XML compliance
in a CMS and DAM product.
--------------------------------------------------------------------
T7. Let a 1000 Contributors Bloom: Technical challenges of
super-distributed Content Management Systems
Many content and asset management products can theoretically scale to
hundreds and even thousands of users who work from diverse environments
across multiple time zones. But system scaling is rarely linear, and
super-distributed content management systems bring unique technical
challenges. Join a panel of CMS administrators from major enterprise who
will share how they had to architect and tweak their systems for mass
adoption.
--
http://cms-list.org/
please trim your posts.
