Difference between revisions of "WikiCMS"

From BITPlan royal-family Wiki
Jump to navigation Jump to search
Line 87: Line 87:
 
=== ⌘⌘ WikiCMS: use Semantic MediaWiki as CMS ===
 
=== ⌘⌘ WikiCMS: use Semantic MediaWiki as CMS ===
 
[[File:ProblemVersusSolution.svg]]
 
[[File:ProblemVersusSolution.svg]]
 +
=== ⌘⌘ WikiCMS: separation of frontend and backend ===
  
 
=== ⌘⌘ Questions/Discussion ===
 
=== ⌘⌘ Questions/Discussion ===
 
[[File:Bitplanpartner.png]]
 
[[File:Bitplanpartner.png]]

Revision as of 10:37, 6 October 2017

<slideshow style="bitplan" headingmark="⌘⌘" incmark="…" scaled="true" font="Comic Sans MS, Calibri, cursive" >

title

WikiCMSProfiwikiicon.png
author
Wolfgang Fahl info@bitplan.com
footer
Using SemanticMediaWiki as a Content Management System
subfooter
SMW CON Fall 2017

</slideshow>

WikiCMS

⌘⌘ Intro

Content is title=Queen

⌘⌘ Wolfgang Fahl

Wfjuggling.png
  • Wolfgang wf@bitplan.com is from germany.
  • He is a teacher for software architecture
  • He has been working with MediaWiki since 2007
  • He has started learning english in England

⌘⌘ Agenda

  • What is a Content Management System CMS?
  • Could you use a MediaWiki/Semantic MediaWiki as a CMS?
  • Why would you not use MediaWiki as your CMS?
  • Why would you use MediaWiki as a CMS?
  • WikiCMS: use Semantic MediaWiki as CMS

⌘⌘ What is a Content Management System CMS?

According to Wikipedia a Content Management System has the following features:

  • a CMS supports the creation and modification of digital content.
  • a CMS is a collaborative environment
  • a CMS supports
    • format management
    • history editing
    • version control
    • indexing
    • search
    • retrieval
  • a CMS supports the separation of content and presentation

⌘⌘ Could you use a MediaWiki Semantic MediaWiki as a CMS?

  • MediaWiki supports the creation and modification of digital content.
  • MediaWiki is a collaborative environment
  • MediaWiki supports
    • format management
    • history editing
    • version control
    • indexing
    • search
    • retrieval
  • MediaWiki supports the separation of content and presentation

⌘⌘ Why would you not use MediaWiki as your CMS?

  • Anyone can edit it
  • No workflow
  • No approval method built into the wiki

⌘⌘ Why would you use MediaWiki as a CMS?

  • MediaWiki is free
  • MediaWiki is proven to work
  • There is a lot of knowledge/documentation about MediaWiki available
  • There are lots of extensions available of MediaWiki

⌘⌘ Why would you use MediaWiki as a CMS?

But this also true for Wordpress? Why still use MediaWiki?

Wordpress-Logo-transparent-smallshadow.png
SMW logo.svg
  • That depends where your focus is!
  • Presentation -> Wordpress
  • Structured Content -> Semantic Media Wiki

⌘⌘ What content is available in MediaWik/Semantic MediaWiki ?

see Royal-Family Wiki

Photos
Videos Video.png
Maps Kensingtonpalacemap.png
Lists Example
Tables Example
Graphs Example
...

⌘⌘ WikiCMS: use Semantic MediaWiki as CMS

ProblemVersusSolution.svg

⌘⌘ WikiCMS: separation of frontend and backend

⌘⌘ Questions/Discussion

Bitplanpartner.png