Main flow aligned to the original teaching document
1. Overview: define the task scope and explain uploads, Q and A, reports, search, and assistant functions.
2. System architecture: map LINE Messaging API, Gemini, Sheets, Drive, external APIs, and Apps Script to system roles.
3. First-time setup: complete Google Sheet, Drive, Apps Script, API key, Google service, and Webhook configuration in the original sequence.
4. Admin functions: return to the spreadsheet and manage rich menus and operational controls.
5. Core functions: file management, Q and A, report generation, Threads posting, search, and utility tools.
Appendix: primary APIs, official docs, playlists, and MOOC entry points.
How Parts 2 and 3 continue the course
After Part 1, the original document moves into collaborative development with generative AI and a version-by-version feature evolution log. For a development-oriented course, those sections should follow the five-part usage flow above.
Delivery variants by available time
Focus on account setup, Webhook verification, minimum reply testing, and live demos.
Complete Sheets, Drive, GAS, LINE integration, and one AI-enhanced workflow.
Add prompt design, governance, logs, and project-based extension.
Emphasize teaching transfer, administrative use, and reusable instructional templates.
Assessment dimensions
| Dimension | Focus |
|---|---|
| System setup | Can the learner connect LINE, GAS, Sheets, and Drive successfully? |
| Process understanding | Can the learner explain how events are received, parsed, routed, and logged? |
| Workflow implementation | Can the learner build at least one reproducible workflow such as summarization or posting? |
| Instructional explanation | Can the learner explain the design clearly through slides, docs, or a mini-site? |
Suggested deliverables
- A LINE Bot that passes Webhook verification.
- A Google Sheet with API keys, logs, notes, and workflow-related tabs.
- At least one complete workflow description such as upload to summary to report.
- A presentation or site page explaining the system design and use case.