Digital workplace presentation at PodCamp 2017-02-25

Digital workplace hand and gears image.


The slides presented at the Building your own digital workplace, the tools, tricks and techniques session (see below) at the PodCamp Toronto 2017 conference are available in a downloadable PDF version:

Digital workplace presentation PodCamp 2017-02-25 PDF v1c F

Podcamp 2017 digital workplace session description well as in this post, below. The links work in both the post version and the PDF. Note that the links to pages on my own local filesystem don’t work. They are identifiable by the absence of “http://” and a domain name.

I recently presented at the combined WPToronto East: Let’s talk SEO | The Toronto WordPress Group Meetup and Hands-On Workshop | The Toronto WordPress Group Meetup events are available in a downloadable PDF version in another post, Structured data SEO presentation at WPTO Meetup 2017-02-18.

See also Data Markup Strategy for SEO notes, 2016-11-23 | WordPress Toronto Meetup, my earlier post with extensive structured data research notes including articles and posts explaining key concepts and techniques in greater detail.

If you found my presentation useful, a tweet to that effect would be appreciated (@Robin_Macrae #SEO #structured data #WPTO).

The presentation video

The presentation slides

Building your own digital workplace, the tools, tricks and techniques

  1. The context
    1. Download this presentation’s slides from (Digital workplace presentation at PodCamp 2017-02-25).

    2. What is a digital workplace?
      1. digital work inputs and outputs: all digital all the time
      2. knowledge work
      3. interconnected
      4. anytime, anywhere, any device
    3. Why a digital workplace?

      What does a digital workplace address? Why do we care?

      1. creating content everywhere
      2. data ownership, portability, durability
      3. digital life privacy and legacy
      4. text, HTML, image, video, audio media types/formats
    4. Who am I and what do I do
      1. consultant
      2. information architect
      3. content guy (strategy, development, writing, editing)
      4. front-end developer (HTML, CSS)
      5. DW evangelist
    5. What I have been doing
      1. small business management consultant
      2. legal practitioner
      3. marketing communications
      4. software development, CMS
      5. tech consulting (strategy, management)
    6. This means professional services
      1. work methodology is my responsibility
      2. knowhow and expertise work product
      3. documentation (process, deliverables)
      4. accountability
  2. My DW infrastructure
    1. Core concepts
      1. hypertext (HTML)
      2. everything is a vast collection of web site
      3. real-time timekeeping (docketing)
      4. workflow
    2. Concepts applied
      1. every activity and output is supported
      2. self-documentation is documenting my process in real-time
      3. author a serial/chron flow of hypertext
    3. Everything I produce and consume is validated HTML
      1. ultimate in portability and longevity
      2. separation of form and content
      3. machine/human compatibility
      4. can copy and paste into email, MS Office, inline forms/editors
    4. Why hypertext
      1. language of the web
      2. better paradigm for knowledge work and iterative/agile work methodologies (real world is iterative, granular, discoverable)
      3. semantic capabilities (human readable, machine-to-machine)
      4. lower risk of tech obsolescence
      5. open source (last but not least)
    5. Tools
      1. WYSIWYG word processor (HoTMetaL)
      2. clipboard manager and search-and-replace utility
      3. browser tabs groups, auto-refresh
      4. hierarchical filesystem, Cruella (NTFS) (same on all devices)
      5. publishing (WordPress, SharePoint)
    6. The topic set
      1. folder(s) in a hierarchy, think of nested dolls
      2. standard organization of sub-folders within a site
      3. standard pages (files) using templates
      4. standard entries (more templates)
    7. The content structure hierarchy
      1. item
      2. sub-entry
      3. entry
      4. page
      5. topic set
      6. topic superset
      7. / (root)
    8. Collections and how to decide to create one
      1. each is a collection of the smaller unit of content
      2. an entry is a collection of items
      3. a page is a collection of entries
      4. a topic set is a collection of pages
      5. a topic superset is a collection of topic sets
    9. Why it works to produce flow
      1. always a place within a structure to put something
      2. findable by asking where should it be?
      3. any given thing can move up or down the content hierarchy (flexibility)
      4. automagic secure distribution, sharing and backup
      5. linking a no-brainer
    10. Linking is a no-brainer and effortless
      1. every unit of content is linkable
      2. create with page or entry and hidden
      3. each hidden set preset for entry, page and log
      4. often a cross-reference (bilateral in effect)
      5. TOC represents the topic set
    11. An intuitive and mnemonic approach
      1. think “where should that be” rather than where did I put it
      2. 4-tier hierarchy is sufficient
      3. inventory/schema of content items, sub-entries, entries, tmp entries, topic set, topic superset
      4. use keywords to navigate your own space (instant Spotlight indexing)
    12. Real-time docketing
      1. the essential interconnecting technique
      2. an essential aspect of an information unit and its findability
      3. self-instrumentation and measurement (accountability, reporting)
      4. transparency
    13. The metadata
      1. Tables of content in each topic set
      2. Indexes for high value or complex ones
      3. Chron for time-based lists, topic set numbering
      4. Infrastructure level aggregation
    14. Let’s see them
      1. HoTMetaL editor UI
      2. ClipMate and X-Replace utilities
      3. Firefox browser
      4. tech topic set (t58), folders, template, page, entry
  3. Tour of the work landscape
    1. Addresses key issues
      1. granularity of content (what is the unit of content)
      2. fear of shipping (getting started)
      3. just-in-time vs just-in-case conundrum
      4. re-use
    2. Workflow screenshots
      1. desktop
      2. desktop space (OS X)
    3. Workflow example
      1. start in log entry
      2. move into a log entry sub-entry
      3. move into existing or new entry
    4. How I manage social media
      1. LinkedIn
        1. Social | LinkedIn
        2. Profile management | Social LinkedIn | Business Plan | BP8 | 2015-12-15 |
      2. Twitter, Social media | PodCamp 2017 presentation | Marketing | b326 2017-02-06 |
      3. Pinterest, Pinterest social network | Services | t58 | 2016-08-29 |
    5. This event’s topic set
      1. PodCamp 2017 presentation (b326)
      2. this is what I use for this event
      3. lots of other event topic sets
      4. pages for previous PodCamp attendance and speaking (standardization)
      5. tour the page’s entries
    6. Project redesign WordPress site
      1. WB v2 site redesign management, Procedures (t153b_b2)
    7. Dockets (timekeeping)
      1. 2016-02-22 We, the current docket
      2. Real-Time Log (2009 all), the last full year of the RTL compared to the current scheme
      3. compare to a client project log, Log 2016-05 | Metadata | NewPath | 2016-05-02 |
    8. A client topic set
      1. NewPath GKS, a client project
      2. a project, Scholarship application app 2016 | GKS Fund
      3. compare to another 6 years ago, SMRBA 2010 | hor01_p144 | 2010-11-02 |
      4. Log 2016-05 | Metadata | NewPath | 2016-05-02 |
    9. The WordPress guide topic superset
      1. TOC (t151_a1)
      2. Index (t151_b7)
      3. Plugins index (t163_h5)
      4. Log entry 2016-12-20 (t152k_b12)
      5. WB v2 site redesign management, Procedures (t153b_b2), my WordPress site
    10. The metadata infrastructure

      1. Frameset, Master Index List
      2. Frameset, Technology Index, Topics
      3. Index : Start : Single page version (2008-10-24)
      4. Directory : Cyberspace : General
    11. Re-use example
      1. evaluate a theme recommended for a WordPress client in a log entry
      2. move to a log sub-entry when length warrants
      3. move to a theme evaluation specific entry
      4. move to a redesign site page when theme selected for trial
      5. move to a CMS topic set when theme used for another client
  4. Odds and ends
    1. Key tools
      1. HoTMetaL editor
      2. Firefox
      3. ClipMate clipboard manager utility
      4. X-Replace search and replace
      5. S5 HTML presentation script
    2. HoTMetaL still the best editor
      1. WYSIWYG word processor (editor)
        1. stylesheets applied
        2. essential tag information
      2. validated HTML (HTML 4.01 Strict)
      3. 16bit antique runs in Windows 7 VM
    3. Firefox addons
      1. Tab Groups (includes backup/restore; entry)
      2. Auto Reload (auto-refresh; entry)
      3. AutoCopy 2 (page)
      4. View Selection Source (context menu)
    4. ClipMate clipboard manager utility
      1. unlimited clips
      2. copy multiple times
      3. auto paste a series
      4. example of how little developers/vendors know about work
    5. X-Replace search and replace
      1. enables a template to be turned into a page
      2. think form with fields and values
      3. retain as record of set-up
      4. regex capable
    6. S5 HTML presentation script
      1. one of many open source available
      2. use HTML just like any other page
      3. has the key presentation capabilities without bloat, proprietary format, etc.
    7. The essential role of CSS
      1. functional (re-usable) and semantic (human readable, machine-to-machine)
      2. 500+ rules for entities, events, components, etc. (CSS selector sidebar menu (m8 1a))
      3. topic set specific vs topic superset vs Cruella
      4. makes a WYSIWYG editor essential (feedback)
    8. Cloud storage services
      1. SugarSync for sync and backup of user space (~36 GB) (replicates Cruella filesystem)
      2. Google Drive for casual sharing, SW archive
      3. OneDrive for project sharing, MS Office, SharePoint
      4. iCloud for OS X and iOS backup and sharing mail, contacts, photos
      5. Dropbox for personal and casual sharing and portability
      6. Acronis True Image for VM backup
    9. Cloud services
      1. Slack for collaboration
      2. Zoom for conferencing, screen sharing
      3. Skype for voice and video calls
    10. CMS use and opportunities
      1. WordPress for publishing (WP, TypeMetal clients; authoring UX overhaul)
      2. SharePoint (greatly improved authoring UX)
      3. static site generators (e.g., Jekyll)
      4. file-based CMSes (e.g., Kirby, a file-based CMS running on PHP, Apache and MySQL (same as WordPress))
    11. WordPress as a platform for an individual’s digital workplace
      1. use WordPress site as a way to integrate core capabilities
      2. Knowledge worker or solopreneur
      3. Subdomain sites planning | WB v2 site redesign management, Procedures (t153b_b2)
      4. 4 potential sites to add to WordPress as subdomains
    12. The platform
      1. WordPress publishing
      2. CRM (vTiger)
      3. collaboration (P2 theme)
      4. KM (MediaWiki theme and plugin)
      5. tech writing/publishing (easyDITA)
    13. Related concepts and further reading
      1. knowledge management
      2. Working out loud
      3. an organization’s intranet
      4. eating your own dogfood
    14. Previous digital workplace related presentations
      1. Developing an Enterprise Strategy to Deliver Customized Sets of Capabilities is my 2008 deck for an SharePoint Saturday conference event presentation (event_b80_TSPUG_pres_2008-02-20)
      2. Shifting WordPress from Manual to Automattic is my 2016 deck co-authored with Sirota
  5. Questions