Content's quality for Plone editors

29
for Plone Editors. Content’s Quality Abstract for Plone Conference 2014 [email protected] /

description

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

Transcript of Content's quality for Plone editors

Page 1: Content's quality for Plone editors

for Plone Editors.

Content’s Quality

Abstract for Plone Conference 2014 [email protected] /

Page 2: Content's quality for Plone editors

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?

Page 3: Content's quality for Plone editors

not all web CMSs are created equal.

Page 4: Content's quality for Plone editors

WHAT ABOUT PLONE?

image: http://www.superbwallpapers.com/animals/labrador-puppy-27369/

Page 5: Content's quality for Plone editors

Meaningful URLs.● Content organized in folders● URLs derived from title/context of content

good to:✓ ease editors activities✓ ease SEO

Page 6: Content's quality for Plone editors

Dublin Core everywhere.● all content types provide major Dublin Core

metadata - title, creator, subject, description, ...

good to:✓ ease web syndication through RSS✓ ease SEO

Page 7: Content's quality for Plone editors

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

Page 8: Content's quality for Plone editors

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

Page 9: Content's quality for Plone editors

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

Page 10: Content's quality for Plone editors

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

Page 11: Content's quality for Plone editors

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

Page 12: Content's quality for Plone editors

Spelling & grammar checker.● afterthedeadline.com integrated in TinyMCE

good to:✓ avoid spelling & grammar errors in pages

Page 13: Content's quality for Plone editors

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

Page 14: Content's quality for Plone editors

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

Page 15: Content's quality for Plone editors

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! :)

Page 16: Content's quality for Plone editors

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.)

Page 17: Content's quality for Plone editors

Death to broken links.● collective.linkcheck● gocept.linkchecker

good to:✓ avoid broken links (internal, external)✓ improve SEO performance

Page 18: Content's quality for Plone editors

URLs under control.● Products.RedirectionTool

○ control Redirection, short-URL● collective.scriptedredirect

○ control redirection using Python

good to:✓ avoid 404s after migrations

Page 19: Content's quality for Plone editors

● plone.app.imagecropping● Products.ImageEditor

Better images.good to:✓ get more control over images

Page 20: Content's quality for Plone editors

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

Page 21: Content's quality for Plone editors

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

Page 22: Content's quality for Plone editors

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

Page 23: Content's quality for Plone editors

QA for webmasters.● quintagroup.analytics

○ content stats

good to:✓ understand content situation

Page 24: Content's quality for Plone editors

Cache quality.● collective.purgebyid

good to:✓ improve cache server

correctness

Page 25: Content's quality for Plone editors

Catalog quality.● collective.catalogcleanup

○ remove “dead” brains

good to:✓ avoid internal link errors if

catalog gets dirty

Page 26: Content's quality for Plone editors

more options in your mind?

Page 27: Content's quality for Plone editors

do CONTRIBUTE!

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

Page 28: Content's quality for Plone editors

How to contribute?● docs.plone.org● paragon.plone.org

good to:✓ let good practices and packages

emerge and get discovered

Page 29: Content's quality for Plone editors

Maurizio [email protected]