A CMS is useful to take care of your HTML quality, avoiding broken links, improving SEO performance and so on.. let's see how Plone is very helpful in all this. VIDEO: https://vimeo.com/110421872

1. Content’s Quality
for Plone Editors.
maurizio.delmonte@abstract.it / Abstract for Plone Conference 2014

2. What “quality”?
★ html - well formed, accessibility, ...
★ links - not broken
★ images - correct size, ...
★ content - SEO, obsolescence, ...
★ …
sounds like you need a
a good web CMS, isn’t it?

3. not all web CMSs are created equal.

4. WHAT
ABOUT
PLONE?
image: http://www.superbwallpapers.com/animals/labrador-puppy-27369/

5. Meaningful URLs.
● Content organized in folders
● URLs derived from title/context of content
good to:
✓ ease editors activities
✓ ease SEO

6. Dublin Core everywhere.
● all content types provide major Dublin Core
metadata - title, creator, subject, description, ...
good to:
✓ ease web syndication through RSS
✓ ease SEO

7. Flexible links.
● each content has its own UID
● content UIDs are used to create internal links
good to:
✓ let editors safely move content around
✓ avoid broken internal links

8. No worries for navigation.
● automatic components in the pages take care
of navigation (portal tabs, breadcrumbs,
navigation portlet, folder listing, ...)
good to:
✓ let editors safely move content around
✓ avoid broken internal links

9. Valid and clean HTML.
● page body text HTML filtered using a configurable
filter (no nasty tags, attributes, classes, …)
good to:
✓ let editors safely copy/paste content snippets
✓ enforce accessibility rules easily
✓ ease visual coherence

10. Down with 404s.
● warning on deletion of content referenced by other content
● automatic redirection happens when old URLs of content are
requested
good to:
✓ avoid broken links
✓ avoid 404 for moved content
✓ improve SEO performance

11. Resized images at will.
● editors get different pre-defined automatic
scales for each published image
good to:
✓ avoid to use wrong size for images
✓ limit bandwidth for improved user experience

12. Spelling & grammar checker.
● afterthedeadline.com integrated in TinyMCE
good to:
✓ avoid spelling & grammar errors in pages

13. Plone offers all this out-of-the-box.

14. HOW TO IMPROVE FROM HERE?
image: http://carltons-quote-corner.weebly.com/uploads/8/5/6/8/8568685/2194609_orig.jpg

15. Plone add-ons.
● Pypi?plone -> 3033 packages
● Pypi?collective -> 1649 packages
● Github/collective -> 1245 packages
● out in the wild -> ++ packages
some of those definitely help with
contents’ quality.
… I hate not to know them all! :)

16. Editor’s assistant.
● collective.jekyll
● set of useful rules ootb
● configurable/extensible
good to:
✓ avoid common mistakes (title/description
length, copy_of URLs, etc.)
✓ suggest good practice (links and images
with correct size in body text, etc.)

17. Death to broken links.
● collective.linkcheck
● gocept.linkchecker
good to:
✓ avoid broken links (internal, external)
✓ improve SEO performance

18. URLs under control.
● Products.RedirectionTool
○ control Redirection, short-URL
● collective.scriptedredirect
○ control redirection using Python
good to:
✓ avoid 404s after migrations

19. Better images.
● plone.app.imagecropping
● Products.ImageEditor
good to:
✓ get more control over images

20. SEO to the rescue.
● collective.googleanalytics
○ per site/page reports
○ email/comments/download/external
links stats
● qg.seoptimizer
○ SEO oriented tags, canonical URLs
good to:
✓ improve SEO performance

21. Tags and more.
● Products.PloneKeywordManager
● eea.alchemy
○ auto-tagging, Natural Language Proc.
with alchemyapi
● collective.taghelper
○ auto-tagging
● collective.taxonomy
○ hierarchical taxonomies
good to:
✓ improve content classification and
findability

22. Relations.
● eea.alchemy
○ discover related items using
alchemyapi
● collective.simserver
○ discover related items using its own
doc similarity service
good to:
✓ improve content classification and
findability

23. QA for webmasters.
● quintagroup.analytics
○ content stats
good to:
✓ understand content situation

24. Cache quality.
● collective.purgebyid
good to:
✓ improve cache server
correctness

25. Catalog quality.
● collective.catalogcleanup
○ remove “dead” brains
good to:
✓ avoid internal link errors if
catalog gets dirty

26. more options in your mind?

27. do
CONTRIBUTE!
image: http://mybfolder.com/picture.php?ref=3&id=2029

28. How to contribute?
● docs.plone.org
● paragon.plone.org
good to:
✓ let good practices and packages
emerge and get discovered

29. Maurizio Delmonte
maurizio.delmonte@abstract.it