Generate these sections in order (all inside the main-content div):
Writer templates Theory — Lecture 3
CBSE | X IT | Part B – Unit 1: Digital Documentation (Advanced) using LibreOffice Writer | 35 min
1. Learning Objectives
[3–5 objectives derived from what the PYQs above test — use <ul><li>]
2. 35-Minute Lecture Flow
[HTML table: Time | Activity | Teacher Action — include a quick concept-check slot]
3. Concept Notes
[For EVERY sub-concept tested in PYQs:
- .def-box for definition (with "In exam language: ..." line AND "Exam answer starter: ..." line)
- .key-box with NUMBERED STEP-BY-STEP PROCEDURE as <ol><li> for any menu-based task (examiners always ask "write steps to…")
- .key-box with rules/properties as <ul><li> for non-procedural content
- .example-box for worked examples or screenshots description
- <pre><code> for code with .kw/.bi/.st/.cm/.nm token spans
- .recall-box for expected output or result
After each concept, add 1–2 brief SELF-GENERATED concept checks built from today's topic (do NOT use .pyq-box, do NOT show year/marks/section, do NOT label them "PYQ" — actual PYQs stay internal only)
NOTE: For IT 402, always include the EXACT MENU PATH (e.g., "Format → Styles → Manage Styles") inside .key-box — CBSE X examiners dock marks for vague paths]
4. Examiner Tricks & Common Mistakes
[One .warn-box per trick from the EXAMINER FINGERPRINT list above (plus mistakes visible in the PYQs) — be specific, give the wrong vs right answer]
5. Board Work Plan
[Numbered list: exactly what to write on the blackboard, in order]
6. Classroom Practice Questions
[Modelled on PYQ style. CRITICAL: every answer MUST be inside <details><summary>▶ View Answer</summary>...</details> — never expose the answer directly.
3×1M MCQ — use this exact structure:
<div class="mcq-box">
<b>Q1.</b> Question text?<br>
<ul class="options">
<li>a) ...</li>
<li>b) ...</li>
<li>c) ...</li>
<li>d) ...</li>
</ul>
<details><summary>▶ View Answer</summary>
<ul class="options">
<li class="wrong">a) ... — reason why wrong</li>
<li class="correct">b) ... ✓ — reason why correct</li>
...
</ul>
</details>
</div>
(Note: options list shown WITHOUT .correct/.wrong BEFORE the details; INSIDE details show all options with correct/wrong analysis.)
3×2M short answer in .self-test-box:
<div class="self-test-box"><b>Q4.</b> Question<br><details><summary>▶ View Answer</summary>Full answer</details></div>
2×3M procedure / case-based short answer in .self-test-box — use IT 402 question types only (menu-path steps, identify the tool/option, differentiate, or a short case). Do NOT generate Python programs, output tracing, or database query writing unless the current topic genuinely involves programming:
<div class="self-test-box"><b>Q7.</b> Question<br><details><summary>▶ View Answer</summary>Full answer with exact menu path / numbered steps</details></div>
1 case/application question — include ONLY if this topic naturally supports a case (do not force HOTS) — in .self-test-box with <details><summary>▶ View Answer</summary>answer</details>]
7. Step-by-Step Procedure Summary
[For every hands-on task in "Writer templates Theory" — list the EXACT numbered steps a student must write in the exam.
Format each as: <h3>How to [task name]</h3> followed by <ol><li> numbered steps with exact menu paths.
Example: "How to apply a Paragraph Style: 1. Click inside the paragraph 2. Open Format → Styles → Manage Styles (F11) 3. ..."
If the topic has no procedural steps (e.g., pure theory/definition topic), write 2–3 key comparison tables instead.]
8. Quick Concept Check
[THEORY MODE — this section must NOT contain actual PYQs, .pyq-box, board years, marks, or sections.
Self-generate 4–6 short concept checks built ONLY from today's topic to confirm understanding.
Do NOT label them "PYQ", "previous-year", or "board-style". Use this structure for each:
<div class="self-test-box">
<b>Q.</b> [self-generated concept-check question — menu path, identify tool/option, differentiate, or short procedure]<br>
<b>Concept checked:</b> [concept name]<br>
<details><summary>▶ View Answer</summary>
<b>Model Answer:</b> [full answer with exact menu path / numbered steps as needed]<br>
<b>Common mistake:</b> [what students get wrong — be specific]
</details>
</div>]
9. Student Notes (Copy-ready)
[Concise notes — every concept from PYQs — in .key-box and .def-box; self-check questions in .self-test-box with <details><summary>▶ View Answer</summary>answer</details>]
10. Homework
[DYNAMIC HOMEWORK (Class X IT 402 — practical/procedure subject). Generate homework that matches the current topic, lecture mode, and the question TYPES/MARKS actually present in the source pool:
- Prefer MCQ, VSA (1M), short answer (2M), menu-path steps, procedure writing, identify tool/option, differentiate, and case-based questions.
- Use a 4M/5M question ONLY if the source pool or syllabus topic supports a procedure-based long answer; never hardcode a 5M if the source pool has no 5M question.
- Do NOT generate programming / Python / output-tracing / database-query questions unless the current topic genuinely involves programming.
- Do NOT force a HOTS unless the topic naturally supports a case/application question.
A good Writer/Calc/Base default: 2×1M (MCQ + tool/option identification) + 2×2M short answer + 1×3M procedure steps + 1×4M case-based (only if source supports it).
These are self-generated questions in IT 402 style — do NOT label them "PYQ".
Mark difficulty with .critical/.high/.medium tag.
EVERY answer wrapped in <details><summary>▶ View Answer</summary>...</details> inside .self-test-box or .mcq-box]
11. Keyboard Shortcuts & Menu Paths
[ONLY include shortcuts/paths directly relevant to "Writer templates Theory".
Table format: Shortcut/Path | Action | Notes
Include 4–8 entries. Mark exam-favourite shortcuts with a ⭐ note.
Wrap in <table><tr><th>Shortcut / Menu Path</th><th>Action</th><th>Notes</th></tr>...</table>]
12. Exam Tips
[5 specific tips as .tip-box — derived from PYQ patterns for THIS topic only]
13. Last-Minute Revision Cards
<div class="card-grid">
[One .card per concept: <div class="card-title">[concept]</div> + 1 rule or shortcut + 1 real example]
</div>