Presentation by Jo Wouters at Drupalcamp Stockholm in 2009

1. 3 Drupal use-cases
for newspapers

2. Outline
Case 1: NRC Boeken (Books)
Case 2: Debatagenda (Debates) (20'')
Case 3: Free websites for schools (20'')
DrupalCamp Stockholm: Drupal use cases

3. Who are we?
Krimson
● Drupal Architects (Antwerp, Belgium)
● Drupal only
● Team of 10 people
Focused on
● Tech. challenging projects
● Non profit market
● Media
DrupalCamp Stockholm: Drupal use cases

4. Outline
Case 1: NRC Boeken (Books)
Case 2: Debatagenda (Debates) (20'')
Case 3: Free websites for schools (20'')
DrupalCamp Stockholm: Drupal use cases

5. Case 1: Books – The client
Client: NRC Handelsblad
Quality newspaper
Very dedicated readers:
200.000 – 250.000 papers/day
95% subscriptions
read the paper 40 - 60 min/day
Culture, books, debating, ...
DrupalCamp Stockholm: Drupal use cases

6. Case 1: Books – Newspaper
Traditional newspaper:
● 1x week
● Huge hidden archive
... and huge articles
DrupalCamp Stockholm: Drupal use cases

7. Case 1: Books – Layout newspaper
Layout newspaper
● whitespace
● titles, (subx2)
subtitles
● “ankeilers”
● “streamers”
● extra info (bio, etc)
... still huge articles
DrupalCamp Stockholm: Drupal use cases

8. Case 1: Books - Website
Website:
● Daily news
● Weekly news
● Archive open
● Added data (books,
writers, tags)
DrupalCamp Stockholm: Drupal use cases

9. Case 1: Books – +170.000 nodes
Content (1/2):
● 12.000 articles (1991-2009)
● Source: proprietary backend system
● XML format
● enriched with tags
● weekly new imported articles
● (copyright issues)
● 110.000 books
● proprietary format
● Title + isbn + writer + price + availability + ...
DrupalCamp Stockholm: Drupal use cases

10. Case 1: Books – +170.000 nodes
Content (2/2):
● 40.000 authors
Different sources:
● Articles
● Book information
● Biographies (“400 famous authors”, ...)
● Internal biographies
DrupalCamp Stockholm: Drupal use cases

11. Case 1: Books – Data import (1/4)
Ftp + data_import
Articles (+12.000)
+11.500 – one shot
Backoffice (1991­now)
Reviews, interviews, title, subtitle, streamers,
obituaries, ... body text, blocks,
Ftp + data_import
+/­ 20/week Pictures: copyright, description, ...
Ftp + data_import
+110.000 – one shot
Books (+110.000)
Book information
isbn, title, author, Title,edition, author, ISBN,
price, ... availability, price, ...
Ftp + data_import
daily
DrupalCamp Stockholm: Drupal use cases

12. Case 1: Books – Data import (2/4)
Ftp + data_import
Articles (+12.000)
+11.500 – one shot
Backoffice (1991­now)
Reviews, interviews, title, subtitle, streamers,
obituaries, ... body text, blocks,
Ftp + data_import
+/­ 20/week Pictures: copyright, description, ...
Manual by
Authors (+40.000)
webmasters name, alternative names, initials
pictures,special lists
Ftp + data_import
+110.000 – one shot
Books (+110.000)
Book information
isbn, title, author, Title,edition, author, ISBN,
price, ... availability, price, ...
Ftp + data_import
daily
DrupalCamp Stockholm: Drupal use cases

13. Case 1: Books – Data import (3/4)
Import data (one shot)
● PHP CLI: drush
● 250 MB memory
● +72h (books)
● +72h (articles)
● Optimize MySQL DB (indexes)
DrupalCamp Stockholm: Drupal use cases

14. Case 1: Books – Data import (3/4)
Import data (one shot)
● PHP CLI: drush
● 250 MB memory
● +72h (books)
CHECK OUT
● +72h (articles) CYRVE.com
( Moshe Weitzman )
● Optimize MySQL DB (indexes)
DrupalCamp Stockholm: Drupal use cases

15. Case 1: Books – Data import (4/4)
Import data (daily, weekly)
● +100 book prices, availability, editions,
etc (daily)
● Articles from newspaper (weekly)
Manually (whenever needed)
● Articles (obituaries, special events)
● Special series (tagging)
DrupalCamp Stockholm: Drupal use cases

16. Case 1: Books – Data cleanup
Link & cleanup data (one shot)
● Link books + authors + articles
● Find 'simular' authors
DrupalCamp Stockholm: Drupal use cases

17. Case 1: Books – Data cleanup
Link & cleanup data (one shot)
● Link books + authors + articles
● Find 'simular' authors
DrupalCamp Stockholm: Drupal use cases

18. Case 1: Books – Data cleanup
Link & cleanup data (new modules)
● Link books + authors + articles
● Interface to find 'simular authors'
S. Larsson = Stieg Larsson = St.
Larsson = Larsson, S. = Larsson,
Stieg
Hek, Youp van't = Youp van't Hek =
Youp v't Hek = Hek, Youp van = Y.
van't Hek = Hek, Y. van't = van't Hek,
Y. = van't Hek, Youp, ...
DrupalCamp Stockholm: Drupal use cases

19. Case 1: Books – Performance
Performance
● Cleanup revisions (books: price change =
new revision)
● PHP CLI for heavy lifting (memory &
timeouts)
● Seperate server: webserver <> database
● Cache router
DrupalCamp Stockholm: Drupal use cases

20. Case 1: Books – Why Drupal ?
Why Drupal ?
● Flexibility:
● Content types: defined during
development
● Views is easy
● Tagging (taxonomy) adds great power
● No hidden fees, no lock-in, well known
and proven technological platform
● Free choice of technological partner
DrupalCamp Stockholm: Drupal use cases

21. Outline
Case 1: NRC Boeken (Books)
Case 2: Debatagenda (Debates) (20'')
Case 3: Free websites for schools (20'')
DrupalCamp Stockholm: Drupal use cases

22. Case 2: Debatagenda
DrupalCamp Stockholm: Drupal use cases

23. Case 2: Debatagenda
Cameleon by DevianART: ~Aspectabund
DrupalCamp Stockholm: Drupal use cases

24. Case 2: Debatagenda
Mini-Website:
● Visually integrated in
existing site
● Own login/users/roles
DrupalCamp Stockholm: Drupal use cases

25. Case 2: Debatagenda
Mini-Website:
● Visually integrated in
existing site
● Own login/users/roles
Why Drupal ?
● Embeded media
● Seperate users
● Fast development
● Widgets
DrupalCamp Stockholm: Drupal use cases

26. Outline
Case 1: NRC Boeken (Books)
Case 2: Debatagenda (Debates) (20'')
Case 3: Free websites for schools (20'')
DrupalCamp Stockholm: Drupal use cases

27. Case 3: Your 'local' newspaper
Client:
● Corelio
● Nieuwsblad: popular
newspaper, with local presence
Disclaimer: This is not a Krimson­website
DrupalCamp Stockholm: Drupal use cases

28. Case 3: Your 'local' newspaper
Disclaimer: This is not a Krimson­website
DrupalCamp Stockholm: Drupal use cases

29. Case 3: Your 'local' newspaper
Mini-Website:
● Visually integrated in existing site
● Own login/users/roles
● All menu's are dependent on the 'location'
Why Drupal ?
● Community features (organic groups)
● Completely seperate from 'the real newspaper website'
Disclaimer: This is not a Krimson­website
DrupalCamp Stockholm: Drupal use cases

30. Case 4: Project “secret”
Traditional media:
● See presentation Ken Richards
Why Drupal ?
● Open source
● Fast development – adding features is easy
● No lock-in
DrupalCamp Stockholm: Drupal use cases

31. Conclusion
Media:
● What's YOUR power ? Archive ? Brand ?
● Do small (drupal) projects that blend in
Drupal:
● BIG projects
● SMALL projects
● Cameleon into your existing website
DrupalCamp Stockholm: Drupal use cases

32. Contact us
Questions ?
Jo Wouters
Roel De Meester
www.krimson.be
DrupalCamp Stockholm: Drupal use cases