Skip to main content

Home/ BCU Library/ Group items tagged CMS

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Sara Thompson

Making the Case for CMS! - 1 views

www.slideshare.net/...making-the-case-for-cms

webdesign webtools presentation

shared by Sara Thompson on 29 Oct 11 - No Cached
  • Sara Thompson on 29 Oct 11
     
    Reasons to use a CMS for library website, with supporting arguments for IT, Admin, and Staff concerns
Sara Thompson

COPE: Create Once, Publish Everywhere - 0 views

blog.programmableweb.com/...create-once-publish-everywhere

webdesign design API CMS workflows interface to-blog

shared by Sara Thompson on 11 Apr 12 - Cached
  • With the growing need and ability to be portable comes tremendous opportunity for content providers. But it also requires substantial changes to their thinking and their systems. It requires distribution platforms, API’s and other ways to get the content to where it needs to be. But having an API is not enough. In order for content providers to take full advantage of these new platforms, they will need to, first and foremost, embrace one simple philosophy: COPE (Create Once, Publish Everywhere).
  • COPE is really a combination of several other closely related sub-philosophies, including: Build content management systems (CMS), not web publishing tools (WPT) Separate content from display Ensure content modularity Ensure content portability
  • But to truly separate content from display, the content repository needs to also avoid storing “dirty” content. Dirty content is content that contains any presentation layer information embedded in it, including HTML, XML, character encodings, microformats, and any other markup or rich formatting information. This separation is achieved by the two other principles, content modularity and content portability
  • ...1 more annotation...
  • In my next post, I will go into more detail about NPR’s approach to content modularity and why our approach is more than just data normalization.
  • Sara Thompson on 11 Apr 12
     
    "This guest post comes from Daniel Jacobson, Director of Application Development for NPR. Daniel leads NPR's content management solutions, is the creator of the NPR API and is a frequent contributor to the Inside NPR.org blog." As I look at this beautiful flowchart (beautiful in function) of the NPR web publishing process, I wonder what libraries could learn from this method of information management.  This NPR process is designed to get the content out in a variety of ways, with options for the end user. How are libraries and library systems making this possible for our end users? 
1 - 2 of 2
Showing 20▼ items per page