O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Drupal for Publishers: How to Build a Better Newsroom CMS

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
Decoupled (Headless) Drupal
Decoupled (Headless) Drupal
Carregando em…3
×

Confira estes a seguir

1 de 17 Anúncio

Mais Conteúdo rRelacionado

Anúncio

Semelhante a Drupal for Publishers: How to Build a Better Newsroom CMS (20)

Mais de Acquia (20)

Anúncio

Mais recentes (20)

Drupal for Publishers: How to Build a Better Newsroom CMS

  1. 1. Drupal for Publishers
  2. 2. Kevin Basarab ● 7+ years of newspaper experience. ● Built newspaper sites on Drupal 5, 6 and 7. ● Drupal Developer at Mediacurrent ● Drupal = 5+ years @kBasarab
  3. 3. Who We Work With 125+ Drupal Implementations
  4. 4. Today's Mission: Provide a baseline architecture for a newsroom site from which publishers can customize from.
  5. 5. Why? ● Make editorial processes simpler ● Don't rely on user decision ● Allow customization @Mediacurent
  6. 6. Options ● Editorial Workflows ● Image Management ● Taxonomy Architecture ● Automation with overrides ● Responsive Advertising ● Caching @Mediacurent
  7. 7. ● Rules ○ Quickest and easiest way to speed up workflows ○ Scenarios ■ E-mail select editors when story is added ■ Automate default values Editorial Workflows @Mediacurent
  8. 8. ● Workbench Moderation ○ Advanced state changes and transitions ○ Reporter > Editor 1 > Editor 2 > Published ○ Keep workflow streamlined ○ "Don't abstract workflow so that it's a barrier to publication" ○ Avoid Workbench Access ○ Use more broad roles: ■ Reporter, Line Editor, Editor, Site Admin, Admin Editorial Workflows @Mediacurent
  9. 9. ○ Default allows 7 links ○ Quick access to frequently used links ○ Shortcuts by Role: Contrib Module ● Shortcuts Bar Editorial Workflows @Mediacurent
  10. 10. ● Custom Panels/Dashboards ○ Create for role ○ Menus ○ Custom Views ○ Announcements ○ Frequently used links ○ Frequently asked questions ○ Direct user to this page upon login Editorial Workflows @Mediacurent
  11. 11. ● Core Drupal doesn't work ● Requirements ○ Reusable images ○ Metadata ○ Individual content overrides ○ Two image fields ■ Main image ■ Lead image Image Management @Mediacurent
  12. 12. ● Taxonomy is bread and butter for all news sites ● Base vocabularies: ○ Topics ■ News, Sports, Entertainment, etc... ○ Authors ■ Fielded data of authors ○ Tags ○ Location ○ Automation Taxonomy Architecture @Mediacurent
  13. 13. ● One of the hardest goals ● Options ○ Flags ○ Promoted to front page ○ Sticky ○ Draggable Views ○ Subqueues ○ Nodequeue Rules Automated Overrides @Mediacurent
  14. 14. ● No standards for this yet ● Custom module ● Use iFrames to change positions and variables on breakpoints Responsive Advertising @Mediacurent
  15. 15. ● Publishers are not fans of caching ● Caching is needed in Drupal ● Module options ○ Flush Page Cache: http://drupal.org/project/flush_page_cache ○ Cache Actions: http://drupal.org/project/cache_actions ○ Cache Tags http://drupal.org/project/cachetags ○ Display Cache http://drupal.org/sandbox/Caseledde/1970904 Caching @Mediacurent
  16. 16. @Mediacurent http://bit.ly/AlaskaCaseStudy
  17. 17. Thank You! Questions? @Mediacurent Mediacurrent.com kevin.basarab@mediacurrent.com @kBasarab slideshare.net/mediacurrent

×