Showing posts with label training. Show all posts
Showing posts with label training. Show all posts

Ajabbi slide talks

Mike's Notes

I will have to give many presentations (talks and demos) in the future, so here is a rough plan that builds on an earlier note from a month ago. Feedback on this is welcome.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

12/03/2026

Ajabbi slide talks

By: Mike Peters
On a Sandy Beach: 09/03/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Background

I previously gave hundreds of slide talks to conferences, workshops, and public meetings in NZ. I enjoyed explaining complex things so that anyone could understand. Everything from 30 seconds to 2+1/2 hours. But that was years ago.

As Pipi continues to develop and international interest grows, I will have to give many talks to different audiences in the future. 

The need is now becoming urgent, with requests and opportunities arriving.

What works

I'm also highly visual and prefer to talk about something I can see, like a map, chart, video, gadget, or drawing, rather than read a speech.

What is needed

Audiences

  • Software developers
  • Scientists
  • Pitching to a panel
  • Training users
  • Radio or TV interviews
  • Contractors
  • Volunteers and staff
  • Open office hours
  • etc
Format
  • In-person
  • Remote
  • Hybrid

Delivery

  • Live
  • Pre-recorded

Modular

  • Short & consice
  • Combined for longer talks.

What will happen

This is what I thought might work.

  • Design a structured outline of topics to cover.
  • Design a simple uniform slide format.
  • Apart from the title, utility, and end slides, use one slide per minute, following the 5:5:5 rule.
  • Practice delivering some to the fortnightly research group I attend online, as well as to other groups I am a member of.
  • Start rapidly manufacturing slide talks based on the priority of need.
  • Reuse the notes and images from the 650 posts on this blog.
  • Create simple 1-page A4 summary notes for print, hand out, event notices and email invitations.
  • Record the talks with slides in advance and upload them to YouTube as a library.
  • Pre-record short videos of live demos of using Pipi and upload them to YouTube as a library.
  • Save and share the slides using links as PowerPoint, Google Slides, or Adobe PDF. On Slideshare.
  • Automate by using the Pipi CMS Engine (cms) to store, reuse, update, render, and manage metadata, put in the right place, etc

Work Log

09/03/2026

  • Wrote this post
  • Made A4 paper card mockups of typical slides, looking at layout, fonts, and colours

10/03/2026

  • Created a topic outline (Google Sheet)
  • Watched how TED recommend how to give talks
  • Built a temporary Access Database to organise content. To be imported into the Pipi Learning Object Engine (lob) and use those tools to further configure.
    • ID
    • Code No, e.g., "103-10045-100001-eng-US", "103-10045-100001-fra"
    • Footer, e.g., "Ajabbi Learn"
    • Collection, e.g., "Signing Up"
    • Title (5 word max), e.g., "Creating your profile"
    • Subtitle (5 word max)
    • Slide Talk Flag Y/N
    • Video Demo Flag Y/N
    • PDF Summary Flag Y/N
    • Note
  • Imported the Google Sheet topic outline into the database
  • Discovered Free/open-source screen capture software to pre-record live demos for YouTube.
    • "ShareX (Windows): Open-source, lightweight, and excellent for both screen recording (including GIFs) and screenshots, featuring powerful, automatic sharing options."
    • "OBS Studio (Windows/Mac/Linux): The premier choice for high-quality, unlimited, and feature-rich recording. It is ideal for streaming and complex recordings but has a steeper learning curve."

11/03/2026

  • Added list of slide footers (lower right-hand side)
  • Added list of Collections
12/03/2026
  • Created codes
    • 3-digit footer
    • 5-digit collection
    • 6-digit presentation
  • Heavy editing and reorganising

Content reuse

The same material can be reused in many formats.

  • Developer Docs
  • User learning (Diataxis)
  • In-context workspace help
  • Newsletters
  • This blog
  • Whitepapers
  • Etc

Slide Footers (Host websites)

Visit the Presentation Catalogue (Google Sheet)

  • 100 Ajabbi
  • 101 Ajabbi Learn
  • 102 Ajabbi Design
  • 103 Ajabbi Research
  • 104 Ajabbi Foundation
  • 105 Ajabbi Developer
  • 106 Ajabbi Handbook
  • 107 pipiWiki
  • 108 Ajabbi Community
  • 109 Ajabbi Project
  • 110 Ajabbi i18n
  • 111 Ajabbi Workspace

Collections

Visit the Presentation Catalogue (Google Sheet)

  • 101-10001 Personal Account
  • 101-10002 Enterprise Account
  • 101-10003 Developer Account
  • 101-10004 Researcher Account
  • 101-10005 SME Account
  • 107-10006 Engines
  • 101-10007 Content Management System
  • 106-10008 History
  • 106-10009 Engineering
  • 106-10010 Ajabbi
  • 103-10011 About
  • 103-10012 Research Publications
  • 103-10013 Research Platform
  • 104-10014 Mission
  • 101-10015 Agent Account
  • 102-10016 Components
  • 102-10017 Accessibility
  • 109-10018 Accessibility
  • 105-10019 Boxlang
  • 107-10020 Industries
  • 107-10021 Plugins
  • 109-10022 i18n
  • 103-10023 Complex Systems
  • 104-10024 Programme
  • 104-10025 Board

Talks & Demos

Visit the Presentation Catalogue (Google Sheet)

101 Ajabbi Learn

  • 101-10007 Content Management System
    • 101 Introduction
    • 102 Content Management System
    • 103 Publication
    • 104 Website
    • 105 Blog
    • 106 Wiki
    • 107 Docs
    • 108 Help
    • 109 Workspace
  • <Unknown>
    • Agents & engines
    • How to use the engines
    • DevOps
    • Security
    • Pipi
    • Sign up
    • Choosing an account type
  • 101-10001 Personal Account
    • Personal Account
    • Username, password, and 2FA
    • Account settings
    • Create a profile
    • Languages
    • Accessibility
    • Support
    • Training
  • 101-10002 Enterprise Account
    • Enterprise account
    • Account settings
    • Default Language
    • Billing
    • Support
    • Training
    • Creating a deployment
    • Choose a Language
    • SaaS configuration
    • Creating a workspace
    • Adding modules
    • Adding Plugins
    • Roles and Permissions
    • Adding Users
  • 101-10003 Developer Account
    • Developer account
    • Account settings
    • Default Language
    • Billing
    • Support
    • Training
    • Creating a deployment
    • Choose a Language
    • Creating a workspace
    • Adding modules
    • Adding Plugins
    • Roles and Permissions
    • Adding Users
  • 101-10004 Researcher Account
    • Researcher account
    • Account settings
    • Default Language
    • Billing
    • Support
    • Training
    • Creating a workspace
    • Adding modules
    • Adding Plugins
    • Roles and Permissions
    • Adding Users
  • 101-10005 SME Account
    • SME account
    • Account settings
    • Default Language
    • Billing
    • Support
    • Training
    • Choosing a module
    • Roles and Permissions
    • Adding Users
  • 101-10015 Agent Account
    • Agent Account
    • Account settings
    • Default Language
    • Billing
    • Support
    • Training
    • Creating a deployment
    • Choose a Language
    • Creating a workspace
    • Adding modules
    • Adding Plugins
    • Roles and Permissions
    • Adding Users

102 Design System

  • 102-10016 Components

  • 102-10017 Accessibility

103 Ajabbi Research

  • 103-10011 About
    • Ajabbi Research 
    • Role and purpose
    • Income
    • Open handbook
    • Team culture
    • Open Research
    • Library
    • Projects
  • 103-10023 Complex Systems

  • 103-10012 Research Publications
    • Publications
    • Newsletter
    • Friday Report
    • Seminars
    • On arXiv
  • 103-10013 Research Platform

104 Ajabbi Foundation

  • 104-10014 Mission
    • Ajabbi Foundation
    • Role and purpose
    • Income
    • The Open Handbook
    • Team culture
  • 104-10025 Board

  • 104-10024 Programme
    • Future support
    • Ortus Open-source
    • SIL KeyMan
    • User groups
    • Books

105 Pipi Developer

  • 105-10019 Boxlang
    • BoxLang in a VM
    • BoxLang in Docker

106 Ajabbi Handbook

  • 106-10010 Ajabbi
    • Ajabbi intro
    • Who am I
    • Resources
    • Thanks & Questions
    • Origin
    • Mission & values (why)
    • Organisational form
    • Ajabbi
    • Role and purpose
    • SaaS
    • Profit distribution
    • From customers to community-driven
    • Bootstrap Startup
    • Scaling
    • Open-source
    • GitLab
    • GitHub
    • Future Collaborations
    • Unicode
    • OMG
    • W3C WCAG
    • CNCF
    • Pipi
    • Intro
    • Origin
  • 106-10008 History
    • Pipi 1-5 (1997-2008)
    • Pipi 6 (2017-2019)
    • Pipi 7 (2020)
    • Pipi 8 (2021-2022)
    • Pipi 9 (2023-2026)
  • 106-10009 Engineering
    • Closed core & open-source
    • Closed-core
    • Roadmap
    • Pipi 9 (2023-2026)
    • Pipi 10 (2027-2029)
    • Pipi 11 (2030-)
    • Open-source
    • Roadmap
    • Pipi 9 (2023-2026)
    • Pipi 10 (2027-2029)
    • Pipi 11 (2030-)

107 pipiWiki

  • 107-10006 Engines
    • Algorithm Engine (alg)
    • CMS Engine (cms)
    • Configuration Engine (cnf)
    • Factory Engine (fac)
    • Workflow Engine (wfl)
    • Workspace Engine (wsp)
  • 107-10020 Industries
    • Agriculture
    • Arts & Culture
    • Built Infrastructure
    • Civil Defense
    • Data Centre
    • DevOps
    • Learning
    • Nature Conservation
    • Research
    • Transport
  • 107-10021 Plugins
    • AddThis
    • Amazon Book
    • Apple Map
    • Apple Music
    • ArcGIS Map
    • Atlassian Analytics
    • Azure Map
    • Cacophony
    • CloudConvert
    • CodePen
    • CodeSandbox
    • Confluence
    • Elfsight Weather
    • Flightradar24
    • FormBlock
    • GitHub-Embed 
    • GitLab Snippet
    • Google Analytics
    • Google Calendar
    • Google Docs
    • Google Form
    • Google Map
    • Google Meet
    • Google Sheets
    • Google Slides
    • Instagram
    • IUCN Threat Status 
    • Jira Advanced Roadmap  
    • JSBin
    • Jupyter Notebook
    • KeyMan
    • MailChimp
    • Metservice Weather
    • Microsft Forms
    • Monaco Editor
    • NASA Spot the Station 
    • NASA Worldview
    • NetSuite Case Form 
    • NIWA CO2 Widget
    • NIWA Tide Widget
    • NIWA UV Widget
    • NIWA Weather Widget
    • Odoo Form
    • PDF
    • PostHog Analytics
    • Survey Monkey
    • Trello Board
    • Trello Card
    • TypeForm
    • VesselFinder
    • Vimeo Video
    • Weather Widget
    • Wolfram Notebook  
    • Yandex Map
    • Yandex Video
    • YouTube Video
    • Zoho Calendar
    • Zoho Form
    • Zoom Meeting
108 Ajabbi Community

109 Pipi Project
  • 109-10018 Accessibility
    • Accessibility Profile
    • UK.Govt Design Guide
  • 109-10022 i18n
    • Web KeyMan
    • Mobile KeyMan
110 Ajabbi i18n

111 Ajabbi Workspace

By , No comments:
Tags , , , , ,

Using slide presentations to describe Pipi

Mike's Notes

Thoughts on how to give useful slide presentation talks about Pipi, record them, and make them available on YouTube as a way to explain how Pipi works.

Resources

References

  • Content Management Bible 2nd Ed., by Bob Boiko. Wiley. 2005.

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

09/02/2026

Using slide presentations to describe Pipi

By: Mike Peters
On a Sandy Beach: 09/02/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

I gave a slide talk last night at the regular Open Research Group online meeting about future blog posts being created by a human using a Workspace, transferred to the CMS Engine (cms), processed, and then automatically published to Google Blogger. Creating the slides made me realise the opportunity available to use this format to visually explain the many parts of Pipi simply.

I will give a slide presentation on the Workspace Engine (wsp) at the next meeting. I will also give one on the Workspaces for Screen to the local Film Industry group this month.

Backstory

When I was a young adult, I went around with a group of good people, many of whom have since become lifelong friends, who encouraged me to give some talks. The only problem was that their approach was to write the talk in advance and then read it aloud to the audience. They were all very good at it, and I was hopeless.

  • The first problem was that I found it impossible to write.
  • The second problem was reading out loud what was written. I tripped over the words.

Years later, I had this idea that just talking about something in front of me might work a lot better, a picture, a map, a physical gadget, for example. I have no problems talking about something I understand.

When I became National President of NZERN, I had to give many talks, and that was the method: show slides and just talk about the pictures or diagrams without using notes, unless there was a name or date to remember, often using a whiteboard to draw answers for people who asked questions in a meeting.

I ended up giving hundreds of talks at conferences and workshops across NZ. The longest was 2 1/2 hours, given to the South Island DOC IMU workshop about the NZERN GIS project using ESRI software, and it was highly technical. No notes, just 50 slides.

Using computers like a typewriter has been a tremendous help because of cut-and-paste, which is much easier than shuffling bits of paper. Besides, I use Arial 16pt, which is much easier to read than my handwriting.

Mrs Grammarly

Later, I learned to use assistive technology to help me write. Grammarly Pro rewrites every single sentence that has my name on it, including this post. Grammarly is set on formal British business English. I hope my personal secretary, Mrs Grammarly, is doing a good job.

Big Challenge

Pipi is largely undocumented because it was designed and built visually. There must be thousands of hand coloured drawings on A4 paper, some neatly filed in 50+ 3-hole A4 ring binders, and the rest in many cartons waiting to be filed. Pipi needs to be documented so others can use it. There is a steadily growing interest in Pipi worldwide.

Solutions

  1. Getting Pipi to self-document is well underway, using structured templates that render from hundreds of databases. A rough estimate is that 20,000 web pages of developer technical documentation will be required due to the scale and scope of this enterprise platform.
  2. Setting up a community forum where users can ask questions and provide answers will take the load off me.
  3. I also need to explain verbally the more complicated bits that I find too difficult to write about. Give a slide presentation and record it to share on YouTube.
  4. Use screen capture to record live demos of Pipi in use.
  5. Provide regular Office Hours that can be booked for video chats via Google Meet or Zoom. I'm doing that a lot, and it seems to work.
  6. Record video interviews with the people who wrote most of the articles that I have copied and republished on this engineering blog, On a Sandy Beach. They could be two-way and a chance to discuss some deep issues.
  7. Teaching someone something complex by making it simple is the best way to learn it. So, giving many talks will also help me understand more clearly.

Slide Presentations

Here is a possible list of some overview talks about just one engine as an example. Then there could be more detailed talks on the same subjects. There are hundreds of Agent Engines. Each talk could have about 10-20 slides.

CMS Engine

  • 101 Introduction
  • 102 Content Management System
  • 103 Publication
  • 104 Website
  • 105 Blog
  • 106 Wiki
  • 107 Docs
  • 108 Help
  • 109 Workspace

Next Steps

Once I get into the swing of it, it should get easy. I need to learn to speak more slowly, develop a visual style for the slides, establish a simple slide-naming convention, and address related details. Each slide set will need a webpage for downloading the PDF/PowerPoint/Google Slides, watching the YouTube Video, a printable PDF handout, and links to related information.

The recorded slides, talks, and demos could all be organised using the existing Diataxis framework and Learning Objects, which Pipi uses elsewhere.

By , No comments:
Tags , , , , , ,
Subscribe to: Posts (Atom)