I wanted to give everyone a quick update about the course Handbooks, especially those of you waiting for Handbooks for the latest Access Developer lessons. A few of you have also politely reminding me that some of the newer lessons don't have Handbooks yet. I haven't forgotten about them. The delay is because I'm working on a much better way to produce them.
My old automated Handbook generator worked, but it was pretty basic. It took the lesson transcript, inserted a collection of screenshots from the video, and called it a day. The result was essentially a printed transcript with some pictures added.
My Handbook editors over the years, including Alex, Sami, and Sandra, have done fantastic work cleaning them up, replacing bad screenshots, adding missing images, and improving the formatting. However, that still requires a lot of time-consuming manual work. Someone has to watch the lesson, determine whether each screenshot is useful, find a better frame when it isn't, and place everything in the correct location.
Unfortunately, there are only so many hours in the day, and apparently Starfleet still hasn't delivered my requested army of holographic assistants. I've recently been working on a new proof-of-concept Handbook generator. My goal is to integrate it with my existing Microsoft Access database and video-production workflow.
The new system won't simply look for random scene changes and dump screenshots into a transcript. I want the AI to understand what I'm teaching, determine which steps actually need illustrations, and select the video frame that best demonstrates each action.
For example, if I say, "Click on this button," the Handbook shouldn't simply repeat those words. It should identify the button, include a screenshot showing where it is, draw a red box around it, and write something useful such as, "Click Current Database in the Access Options dialog."
The system can also add a short caption below each screenshot explaining exactly what the image demonstrates. Where appropriate, it can include a brief "Why This Matters" note that preserves the instructional reasoning from the video without copying everything I said word for word.
Moving forward, I want the course Handbooks to serve primarily as companions to the videos. They should provide a clear summary of the lesson, the important steps, useful explanations, and well-chosen screenshots showing exactly where to click.
In other words, you should be able to keep the Handbook open while watching the lesson and use it as a clean reference afterward. It shouldn't feel like you're merely reading a transcript of everything I said, including every "click here," "go over there," and occasional moment when my brain temporarily leaves spacedock.
Ideally, generating a Handbook will become another standard part of my production workflow. I finish recording and processing the lesson, click another button, and the system intelligently creates the Handbook. It may still need a quick human review, but I want to eliminate as much tedious manual cleanup as possible.
This is important to me, but it isn't my highest-priority project right now. I still have classes and other videos to produce, so I'm building the new generator during whatever spare development time I can find. I also don't want to rush it and start producing poor-quality Handbooks just to say they're finished. The screenshots need to show the correct controls, the red boxes need to highlight the right places, and the written instructions need to accurately reflect the lesson.
The sample I'm sharing today is only a proof of concept, but I think it demonstrates what this new format could become. Please take a look and let me know what you think. Do you prefer this cleaner video-companion format? Is there anything from the older Handbooks that you would miss? Would you like more explanation, more screenshots, or a different balance between the two? Your feedback will help determine how I develop the final format.
Once the companion Handbooks are working reliably, I would also like to expand the system to produce more comprehensive standalone books, similar to my Access Beginner 1 book on Amazon.
Those books would be different from the video Handbooks. They would contain more detailed explanations, examples, exercises, troubleshooting advice, and enough background to teach the material without requiring the videos. That is the longer-term goal. For now, I'm concentrating on making the course Handbooks smarter, clearer, more useful, and much easier to produce consistently.
Take a look at the sample and let me know what you think. If you guys like this direction, I'll continue developing it and eventually work my way through the missing Handbooks for the newer lessons. I might even start producing companion PDFs for TechHelp videos, too.
And keep in mind it's still just a rough proof of concept. I still have a lot of work to do on this before it's finished and polished.
I think Ricks note should be its own box like the Tip.
Maybe even with a picture of yourself with a speech bubble around it.
e.g. https://599cd.com/glossary/access/naming/
Sandra Truax
@Reply 8 hours ago
I think it should make sure the text that goes with the picture is on the same page. Example: Text for Overlapping Windows is on bottom of 8, picture is on 9. I like that the pictures are AFTER the text.
Other than that, I think it is really looking good!
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.