blogwithoutalibrary.net
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
- technology
- , library
- , libraries
- , blogging
- , Stuff
- , lis
- , librarians
- , blogposts
- , library2.0
- , TechBlogs
- , library blogs
- , &
- , web2.0
- , blog
- , RSS
- , education
Bookmark History
Saved by 14 people (-3 private), first by anonymouse user on 2006-10-26
- Loud_librarian on 2008-10-10 - Tags technology , library
- Jhannaford on 2008-10-07 - Tags technology
- Katepourshariati on 2008-09-04 - Tags library blogs
- Disobedientlib on 2008-07-12 - Tags Library , Stuff , RSS
- Serendipitina on 2008-03-11 - Tags blogs , librarians , libraries
Public Sticky notes
Highlighted by janus_sa
Right. Sorry about the delay in getting back to this series of posts. You might remember that in part two, I talked at length about the wonders of CCK. The one thing I wanted to pick up on in this post (to round of the CCK discussion) is how CCK makes site administration a lot easier.
If you’re already sold on Drupal, I probably don’t need to tell you how advantageous it is to separate your site’s content from other elements like design, architecture, and navigation. Indeed, this is the promise of most content management systems. CCK facilitates that by allowing you to build input forms that your content folks can use to create pages really easily. So, when a content editor logs into the site, he/she sees a form with clearly defined fields to fill in, which is so much better than being confronted with one large input box in which to dump the entire contents of a page.
Highlighted by jhannaford
Highlighted by jhannaford
Highlighted by jhannaford
Highlighted by jhannaford


Public Comment