Monday, 20 July 2026 – X IT

Monday, 20 July 2026

Lecture 7 of 73 · Unit 1

Unit 1 ⏳ Pending

Unlocks at 05:00 PM, 20 Jul 2026

Inserting and modifying images Theory + PYQ

What We'll Learn

A quick overview of today's lecture

Inserting and modifying images Theory + PYQ COMBINED THEORY + PYQ (single slot). Concept ID: X_IT_U1_IMAGES_INSERT_MODIFY. Primary Sub-subtopic: Inserting and modifying images. Question-bank grouping: Images and Drawing Objects in Writer. Teach the core theory first, then spend the remainder of the lecture on previous-year questions whose concept_ids include X_IT_U1_IMAGES_INSERT_MODIFY.

Key things we'll cover

Inserting and modifying images

PYQ references used by all prompt types 13 included

Flagged questions are excluded from Study Notes, PPT, and Student Notes references until corrected in Paper Analyzer.

Included ID 388 · 2023 · 1 mark(s)

Reema has created a pamphlet on Tour to West India. She has inserted many images to make it more presentable but the size of images is occupying a lot of space. Her friend has suggested her to reduce the size of images. Which of the following options will help her in doing the task without losing any content of the image?
(A) Recolor
(B) Docking
(C) Resize
(D) Rotate

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 389 · 2023 · 1 mark(s)

Which of the following Graphic filter is used to increase the contrast of an image in a document?
(A) Smooth
(B) Sharpen
(C) Remove Noise
(D) Invert

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 553 · 2023 · 1 mark(s)

Mehul has inserted images in his document report "Travel My State" to make it more descriptive. Some of the images are having some extra part that needs to be removed. Which of the following option is suitable to do the task?
(A) Resize
(B) Crop
(C) Recolor
(D) Rotate

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 640 · 2023 · 1 mark(s)

To increases the contrast of an image, __________ option is used in a document.
(a) Smooth
(b) Sharpen
(c) Aging
(d) mosaic

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 409 · 2023 · 2 mark(s)

Differentiate between Keep scale and Keep image size options while cropping an image in a document.

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 577 · 2023 · 2 mark(s)

Differentiate between Aging and Posterize graphic filters.

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 425 · 2024 · 1 mark(s)

Gaurav is creating a report in Writer. The image gets embedded in his document whenever he drags and drops the image and the document size increases. Suggest a way to link the image file instead of embedding it.
(A) Drag and drop the image.
(B) Hold down the Ctrl key while dragging.
(C) Hold down the Shift key while dragging the image.
(D) Hold down the Ctrl and Shift key while dragging and dropping the image.

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 426 · 2024 · 1 mark(s)

Resizing a _____ may badly affect the resolution of an image.
(A) Vector image
(B) Raster image
(C) CAD image
(D) Coloured image

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 674 · 2024 · 1 mark(s)

Which feature allows you to jump to a different document, spreadsheet, or website from within a document?
(a) Bookmark
(b) Page Break
(c) Hyperlink
(d) Format Painter

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 680 · 2024 · 1 mark(s)

What is the benefit of inserting an image as a link in a document?
(a) It reduces the document size by storing only the reference to the image.
(b) It enhances the image quality.
(c) It allows for automatic image editing within the document.
(d) It removes the need for image captions.

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 460 · 2025 · 1 mark(s)

During a recent excursion, Roshni has taken some pictures for making a report in Writer. She wants to increase the contrast of the images. Which one of the following image filters should she use in Writer ?
(A) Aging
(B) Mosaic
(C) Sharpen
(D) Smooth

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 509 · 2026 · 1 mark(s)

Which of the following image tools is used to change the image to black and white, grayscale or a watermark ?
(A) Image Crop
(B) Image Mode
(C) Image Align
(D) Image Size

Images and Drawing Objects in Writer → Inserting and modifying images

Included ID 592 · 2026 · 1 mark(s)

Ravi wants to use tools for filtering, resizing, cropping and rotating of an image inserted in his project created in LibreOffice Writer. Which toolbar should he use to access these tools ?
(A) Image
(B) Drawing
(C) Formatting
(D) Standard

Images and Drawing Objects in Writer → Inserting and modifying images

Student Notes (Print)

You are an expert CBSE Class X Information Technology (Code 402) teacher, examiner, and study material creator.

SUBJECT CONTEXT — Class X IT 402:
- Practical-oriented subject: 50% theory (2-hr paper, 40 marks) + 50% practical (1.5-hr lab, 60 marks).
- Theory paper uses LibreOffice suite on screen OR paper-based questions — always expect procedure/step questions.
- Question types in CBSE X IT board paper: MCQ (1M), VSA (1M), SA-I (2M), SA-II (3M), LA (5M).
- CBSE X IT examiner LOVES: "Write steps to...", "Name the...", "Differentiate between...", classification MCQs.
- Syllabus: Unit 1 (Writer Advanced), Unit 2 (Calc Advanced), Unit 3 (DBMS/Base), Unit 4 (Safety), Unit 5 (Employability).
- Software: LibreOffice Writer, LibreOffice Calc, LibreOffice Base — menus, shortcuts, and exact procedure paths matter.

===========================================
SCOPE — READ BEFORE GENERATING ANYTHING
===========================================
Today's lecture covers ONE topic only: "Inserting and modifying images Theory + PYQ"
Lecture number 7 of 43 | Duration: 35 minutes | Board: CBSE
Chapter: Part B – Unit 1: Digital Documentation (Advanced) using LibreOffice Writer

HARD RULE: Every piece of content you generate — notes, examples, questions, tips —
must be directly relevant to "Inserting and modifying images Theory + PYQ" only.
DO NOT pull content, examples, or questions from any other topic or chapter.

LECTURE MODE: COMBINED THEORY + PYQ (single slot)
- Scope: "Inserting and modifying images" only.
- First half: teach the core concept (definitions, intuition, key examples, misconceptions) -- keep it tight.
- Second half: switch to previous-year-question practice -- question analysis, marking points, model answers, and common mistakes.
- Use the 13 real PYQ record(s) provided below as the source of truth. Do not fabricate board years, marks, or questions.

===========================================
SECTION 1: LECTURE INFORMATION
===========================================

Class: X IT | Subject: Information Technology (Code 402) | Board: CBSE
Topic: Inserting and modifying images Theory + PYQ
Subtopics to cover today:
- Inserting and modifying images

Student level: Class X, CBSE Board, average to above-average students preparing for board exams

===========================================
SECTION 2: TEACHER'S REFERENCE NOTES
===========================================

Inserting and modifying images Theory + PYQ

COMBINED THEORY + PYQ (single slot).
Concept ID: X_IT_U1_IMAGES_INSERT_MODIFY.
Primary Sub-subtopic: Inserting and modifying images.
Question-bank grouping: Images and Drawing Objects in Writer.

Teach the core theory first, then spend the remainder of the lecture on previous-year questions whose concept_ids include X_IT_U1_IMAGES_INSERT_MODIFY.

Teaching ideas: Concept first, then a focused PYQ round with board solutions and examiner traps.

===========================================
SECTION 3: PYQ FREQUENCY DATA (Year-wise)
===========================================

Teaching priority: HIGH
High-yield concepts: Inserting and modifying images

| Year | Questions | Marks |
|------|-----------|-------|
| 2023 | 6 | 8 |
| 2024 | 4 | 4 |
| 2025 | 1 | 1 |
| 2026 | 2 | 2 |
| **Total** | **13** | **15** |

===========================================
SECTION 4: ACTUAL PREVIOUS YEAR QUESTIONS
(Scope: "Inserting and modifying images Theory + PYQ" only — 13 questions from board papers)
===========================================

USE THESE QUESTIONS TO BUILD ALL CONTENT.
- Derive learning objectives from what they test
- Build examples from the concepts they probe
- Identify tricks from how they are worded
- Design homework and assessment in the same style


--- 2023 Board Exam (6 questions | 8 marks) ---

Q1. [MCQ] [1M] [Medium] Section-A
Reema has created a pamphlet on Tour to West India. She has inserted many images to make it more presentable but the size of images is occupying a lot of space. Her friend has suggested her to reduce the size of images. Which of the following options will help her in doing the task without losing any content of the image?
(A) Recolor
(B) Docking
(C) Resize
(D) Rotate

Q2. [MCQ] [1M] [Easy] Section-A
Which of the following Graphic filter is used to increase the contrast of an image in a document?
(A) Smooth
(B) Sharpen
(C) Remove Noise
(D) Invert

Q3. [MCQ] [1M] [Easy] Section-A
Mehul has inserted images in his document report "Travel My State" to make it more descriptive. Some of the images are having some extra part that needs to be removed. Which of the following option is suitable to do the task?
(A) Resize
(B) Crop
(C) Recolor
(D) Rotate

Q4. [MCQ] [1M] [Easy] Section-A
To increases the contrast of an image, __________ option is used in a document.
(a) Smooth
(b) Sharpen
(c) Aging
(d) mosaic

Q5. [Short Answer] [2M] [Hard] Section-B
Differentiate between Keep scale and Keep image size options while cropping an image in a document.

Q6. [Short Answer] [2M] [Hard] Section-B
Differentiate between Aging and Posterize graphic filters.

--- 2024 Board Exam (4 questions | 4 marks) ---

Q1. [MCQ] [1M] [Medium] Section-A
Gaurav is creating a report in Writer. The image gets embedded in his document whenever he drags and drops the image and the document size increases. Suggest a way to link the image file instead of embedding it.
(A) Drag and drop the image.
(B) Hold down the Ctrl key while dragging.
(C) Hold down the Shift key while dragging the image.
(D) Hold down the Ctrl and Shift key while dragging and dropping the image.

Q2. [MCQ] [1M] [Easy] Section-A
Resizing a _____ may badly affect the resolution of an image.
(A) Vector image
(B) Raster image
(C) CAD image
(D) Coloured image

Q3. [MCQ] [1M] [Easy] Section-A
Which feature allows you to jump to a different document, spreadsheet, or website from within a document?
(a) Bookmark
(b) Page Break
(c) Hyperlink
(d) Format Painter

Q4. [MCQ] [1M] [Easy] Section-A
What is the benefit of inserting an image as a link in a document?
(a) It reduces the document size by storing only the reference to the image.
(b) It enhances the image quality.
(c) It allows for automatic image editing within the document.
(d) It removes the need for image captions.

--- 2025 Board Exam (1 question | 1 marks) ---

Q1. [MCQ] [1M] [Easy] Section-A
During a recent excursion, Roshni has taken some pictures for making a report in Writer. She wants to increase the contrast of the images. Which one of the following image filters should she use in Writer ?
(A) Aging
(B) Mosaic
(C) Sharpen
(D) Smooth

--- 2026 Board Exam (2 questions | 2 marks) ---

Q1. [MCQ] [1M] [Easy] Section-A
Which of the following image tools is used to change the image to black and white, grayscale or a watermark ?
(A) Image Crop
(B) Image Mode
(C) Image Align
(D) Image Size

Q2. [MCQ] [1M] [Easy] Section-A
Ravi wants to use tools for filtering, resizing, cropping and rotating of an image inserted in his project created in LibreOffice Writer. Which toolbar should he use to access these tools ?
(A) Image
(B) Drawing
(C) Formatting
(D) Standard

===========================================
===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Inserting and modifying images
  Pattern: MCQ=11, Short Answer=2 | Marks: 1M=11, 2M=2 | Total: 13 questions
  [MCQ] [1M] [Medium] × 2
    → Core concept of Inserting and modifying images
  [MCQ] [1M] [Easy] × 9
    → Core concept of Inserting and modifying images
  [Short Answer] [2M] [Hard] × 2
    → Core concept of Inserting and modifying images


===========================================
===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Inserting and modifying images | 57 | 13 | 15M | 2026, 2025, 2024 | CRITICAL |

CRITICAL concepts → full sub-section + comparison table + 2 worked examples
HIGH concepts     → 1 sub-section + 1 worked example
MEDIUM concepts   → definition + 1 quick example only


===========================================
YOUR TASK — Generate a complete classroom-ready teaching package
===========================================

Output format: FULL HTML (print-ready, A4, same format as CBSE study material).
Use the CSS classes below. NO plain Markdown — use HTML elements only.

HTML STRUCTURE TO GENERATE:

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Inserting and modifying images Theory + PYQ — Lecture 7</title>
<style>
/* ── PRINT SETUP ── */
@page { size: A4; margin: 12mm 14mm 12mm 14mm; }
* { box-sizing: border-box; }

/* ── BASE ── */
body { font-family: 'Segoe UI', Arial, sans-serif; font-size: 9.5pt; color: #1a1a2e; line-height: 1.4; background: #fff; margin: 0; padding: 0; }

/* ── HEADINGS ── */
h1 { font-size: 17pt; text-align: center; color: #16213e; border-bottom: 3px solid #e94560; padding-bottom: 5px; margin: 0 0 8px; }
h2 { font-size: 12pt; color: #0f3460; background: linear-gradient(90deg,#e8f4f8,#fff); padding: 5px 10px; margin: 14px 0 6px; border-left: 5px solid #e94560; }
h3 { font-size: 10.5pt; color: #16213e; border-bottom: 1.5px dashed #ccc; padding-bottom: 3px; margin: 10px 0 4px; }

/* ── CONTENT BOXES ── */
.def-box { background:#e3f2fd; border-left:3px solid #1976d2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box { background:#fff8e1; border-left:3px solid #f9a825; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box ul { margin:3px 0 0 12px; padding:0; }
.key-box li { margin:2px 0; }
.example-box { background:#f3e5f5; border-left:3px solid #7b1fa2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box { background:#ffebee; border-left:3px solid #c62828; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box::before { content: "⚠ EXAMINER TRAP: "; font-weight:bold; color:#e65100; }
.tip-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.recall-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; font-weight:bold; border-radius:0 4px 4px 0; }
.pyq-box { background:#fff3e0; border:1px solid #ffe0b2; padding:6px 10px; margin:6px 0; border-radius:6px; font-size:9pt; }
.pyq-box .pyq-meta { font-size:7.5pt; color:#e65100; font-weight:bold; margin-bottom:3px; }
.mcq-box { background:#f8f9fa; border:1px solid #dee2e6; padding:6px 10px; margin:5px 0; border-radius:4px; font-size:9pt; }
.options { list-style:none; margin:4px 0 0 0; padding:0; }
.options li { padding:2px 0; }
.options li.wrong { color:#c62828; }
.options li.correct { color:#2e7d32; font-weight:bold; }
.options .why { font-size:8pt; color:#555; margin-left:8px; font-style:italic; }
.self-test-box { background:#e8eaf6; border:1px dashed #5c6bc0; padding:6px 10px; margin:6px 0; border-radius:4px; font-size:9pt; }
details summary {
  cursor:pointer; display:inline-block; margin-top:6px; padding:2px 10px;
  background:#e8eaf6; color:#3949ab; border:1px solid #9fa8da;
  border-radius:4px; font-size:8.5pt; font-weight:600; user-select:none;
  list-style:none;
}
details summary::-webkit-details-marker { display:none; }
details[open] > summary { background:#c5cae9; }
details > *:not(summary) { margin-top:6px; }

/* ── CODE ── */
pre {
  background:#f8f9fa;
  color:#212529;
  border:1px solid #dee2e6;
  border-radius:4px;
  margin:4px 0;
  padding:8px 10px;
  font-size:8.5pt;
  line-height:1.5;
  white-space:pre-wrap;
  word-break:break-word;
}
pre code {
  white-space:pre;
  word-break:normal;
  display:block;
  overflow-x:auto;
  font-size:inherit;
}
code {
  font-family:'Courier New', monospace;
  font-size:0.95em;
}
.kw { color:#0000ff; } .bi { color:#267f99; } .st { color:#a31515; }
.cm { color:#008000; } .nm { color:#098658; } .fn { color:#795e26; }
.va { color:#001080; }

/* ── TABLES ── */
table { border-collapse:collapse; width:100%; margin:5px 0; font-size:8.5pt; }
th, td { border:1px solid #bbb; padding:3px 6px; text-align:left; }
th { background:#eeeeee; font-weight:bold; color:#333; }
tr:nth-child(even) { background:#fafafa; }
.highlight-row { background:#fff9c4 !important; font-weight:bold; }

/* ── CARDS ── */
.card-grid { display:grid; grid-template-columns:repeat(auto-fit,minmax(200px,1fr)); gap:6px; margin:8px 0; }
.card { background:#fff; border:1px solid #ccc; border-radius:4px; padding:6px 8px; font-size:8.5pt; }
.card .card-title { font-weight:bold; font-size:9pt; color:#0f3460; margin-bottom:3px; border-bottom:1px solid #eee; padding-bottom:2px; }

/* ── PRIORITY TAGS ── */
.priority-tag { font-size:7.5pt; padding:1px 6px; border-radius:10px; font-weight:bold; white-space:nowrap; }
.critical { background:#fce4ec; color:#ad1457; }
.high { background:#fff3e0; color:#e65100; }
.medium { background:#fff8e1; color:#f57f17; }
.marks-badge { display:inline-block; background:#e94560; color:#fff; font-size:7.5pt; padding:1px 5px; border-radius:10px; font-weight:bold; margin-left:5px; }

/* ── TOC STICKY SIDEBAR (screen only) ── */
@media screen {
  body { display:grid; grid-template-columns:165px 1fr; gap:0; }
  .toc-sidebar { position:sticky; top:0; height:100vh; overflow-y:auto; background:#f8f9fa; padding:10px 6px; font-size:8pt; color:#333; border-right:1px solid #ddd; }
  .toc-sidebar h4 { font-size:8.5pt; color:#16213e; margin:0 0 8px; padding-bottom:4px; border-bottom:1px solid #ddd; }
  .toc-sidebar a { display:block; color:#0f3460; text-decoration:none; padding:2px 4px; border-radius:3px; margin-bottom:1px; }
  .toc-sidebar a:hover { background:#e8f4f8; }
  .toc-sidebar .toc-h3 { padding-left:10px; font-size:7.5pt; color:#555; }
  .main-content { padding:10px 14px; min-width:0; }
}
@media screen and (max-width:640px) {
  body { grid-template-columns:1fr; }
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:8px; }
}
@media print {
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:0; }
  body { display:block; }
  .print-bar { display:none; }
  .collapse-btn { display:none !important; }
  .section-body { display:block !important; }
  /* Force all <details> open and hide the toggle-button summary text */
  details { display:block !important; }
  details > *:not(summary) { display:block !important; visibility:visible !important; }
  details > summary { display:none !important; }
}

/* ── PRINT BUTTONS ── */
.print-bar { position:fixed; top:8px; right:8px; display:flex; gap:6px; z-index:999; }
.print-btn { padding:5px 14px; color:#fff; border:none; border-radius:4px; cursor:pointer; font-size:9pt; box-shadow:0 2px 6px rgba(0,0,0,0.3); }
.print-btn.color-btn { background:#e94560; }
.print-btn.bw-btn { background:#333; }
.print-btn.back-btn { background:#1976d2; display:none; }
.print-btn.read-btn { background:#2e7d32; }

/* ── READ MODE ── */
@media screen {
  body.read-mode .print-bar { display:none !important; }
  body.read-mode .toc-sidebar { display:none !important; }
  body.read-mode .main-content {
    grid-column:1 / -1; max-width:860px; margin:0 auto;
    padding:24px 32px; font-size:11pt; line-height:1.75;
  }
}
#btnExitRead {
  display:none; position:fixed; bottom:16px; right:16px;
  background:rgba(0,0,0,0.55); color:#fff; border:none; border-radius:20px;
  padding:6px 14px; font-size:9pt; cursor:pointer; z-index:9999;
}
body.read-mode #btnExitRead { display:block; }
@media print { #btnExitRead { display:none !important; } }

/* ── B&W MODE OVERRIDES ── */
body.bw-mode { background:#fff !important; color:#000 !important; }
body.bw-mode .def-box, body.bw-mode .key-box, body.bw-mode .example-box,
body.bw-mode .warn-box, body.bw-mode .tip-box, body.bw-mode .recall-box,
body.bw-mode .pyq-box, body.bw-mode .mcq-box, body.bw-mode .self-test-box {
  background:#fff !important; border:1px solid #ccc !important; border-left:none !important;
}
body.bw-mode h1 { color:#000 !important; border-bottom:2px solid #000 !important; }
body.bw-mode h2 { background:#fff !important; border-left:2px solid #000 !important; color:#000 !important; }
body.bw-mode h3 { color:#000 !important; border-bottom:1px solid #000 !important; }
body.bw-mode pre { background:#fff !important; color:#000 !important; border:1px solid #ccc !important; }
body.bw-mode .kw, body.bw-mode .bi, body.bw-mode .st, body.bw-mode .cm,
body.bw-mode .nm, body.bw-mode .fn, body.bw-mode .va { color:#000 !important; }
body.bw-mode table th { background:#eee !important; color:#000 !important; }
body.bw-mode tr:nth-child(even) { background:#fff !important; }
body.bw-mode .priority-tag, body.bw-mode .marks-badge { background:#fff !important; color:#000 !important; border:1px solid #000 !important; }
body.bw-mode .card { background:#fff !important; border:1px solid #ccc !important; }
body.bw-mode .highlight-row { background:#fff !important; }
body.bw-mode .toc-sidebar { background:#fff !important; border-right:1px solid #ccc !important; }
body.bw-mode .toc-sidebar a { color:#000 !important; }

/* ── COLLAPSIBLE SECTIONS ── */
.collapse-btn { float:right; background:none; border:none; cursor:pointer; font-size:10pt; color:#aaa; padding:0 4px; margin-left:6px; }
.collapse-btn:hover { color:#e94560; }
</style>
</head>
<body>

<!-- Print / mode buttons (hidden on print) -->
<div class="print-bar">
  <button class="print-btn read-btn"   id="btnReadMode" onclick="toggleReadMode()">&#128214; Read Mode</button>
  <button class="print-btn back-btn"   id="btnBackColor" onclick="backToColor()">&#127775; Back to Color</button>
  <button class="print-btn bw-btn"     id="btnPrintBW"   onclick="printBW()">&#128438; Print B&amp;W</button>
  <button class="print-btn color-btn"                    onclick="printColor()">&#128438; Print Color</button>
</div>
<button id="btnExitRead" onclick="toggleReadMode()">&#10005; Exit Read Mode</button>

<!-- JS: print modes + collapsible sections + TOC auto-build -->
<script>
function printColor() {
  document.body.classList.remove('bw-mode');
  document.getElementById('btnPrintBW').style.display='inline-block';
  document.getElementById('btnBackColor').style.display='none';
  window.print();
}
function printBW() {
  document.body.classList.add('bw-mode');
  document.getElementById('btnPrintBW').style.display='none';
  document.getElementById('btnBackColor').style.display='inline-block';
  window.print();
}
function backToColor() {
  document.body.classList.remove('bw-mode');
  document.getElementById('btnPrintBW').style.display='inline-block';
  document.getElementById('btnBackColor').style.display='none';
}
function toggleReadMode() {
  document.body.classList.toggle('read-mode');
}

// Auto-collapsible h2/h3 sections
(function(){
  function setup(){
    document.querySelectorAll('.main-content h2,.main-content h3').forEach(function(h){
      var btn=document.createElement('button');
      btn.className='collapse-btn';btn.textContent='▼';
      h.appendChild(btn);
      var wrapper=document.createElement('div');wrapper.className='section-body';
      var level=parseInt(h.tagName[1]),next=h.nextElementSibling;
      while(next){
        var tag=next.tagName||'';
        if(/^H[1-6]$/.test(tag)&&parseInt(tag[1])<=level)break;
        var after=next.nextElementSibling;wrapper.appendChild(next);next=after;
      }
      h.insertAdjacentElement('afterend',wrapper);
      btn.addEventListener('click',function(e){
        e.stopPropagation();
        var open=wrapper.style.display!=='none';
        wrapper.style.display=open?'none':'';
        btn.textContent=open?'▶':'▼';
      });
    });
    // Expand/Collapse All in TOC
    var toc=document.querySelector('.toc-sidebar');
    if(toc){
      var bar=document.createElement('div');
      bar.style.cssText='display:flex;gap:4px;margin-bottom:8px;';
      ['Expand All','Collapse All'].forEach(function(label){
        var b=document.createElement('button');
        b.textContent=label;
        b.style.cssText='flex:1;font-size:7.5pt;padding:2px 4px;border:1px solid #ccc;border-radius:3px;cursor:pointer;background:#fff;';
        b.addEventListener('click',function(){
          var expand=label==='Expand All';
          document.querySelectorAll('.section-body').forEach(function(w){w.style.display=expand?'':'none';});
          document.querySelectorAll('.collapse-btn').forEach(function(b){b.textContent=expand?'▼':'▶';});
        });
        bar.appendChild(b);
      });
      toc.insertBefore(bar,toc.firstChild);
    }
    // Auto-build TOC links from h2/h3 IDs
    if(toc){
      document.querySelectorAll('.main-content h2,.main-content h3').forEach(function(h){
        if(!h.id){h.id=h.textContent.trim().replace(/[^a-z0-9]+/gi,'-').toLowerCase().slice(0,40);}
        var a=document.createElement('a');
        a.href='#'+h.id;
        a.textContent=h.textContent.replace('▼','').replace('▶','').trim();
        if(h.tagName==='H3')a.classList.add('toc-h3');
        toc.appendChild(a);
      });
    }
  }
  if(document.readyState==='loading'){document.addEventListener('DOMContentLoaded',setup);}else{setup();}
})();

// Auto-open details when printing
(function(){
  function openDetails(){
    document.querySelectorAll('details').forEach(function(d){
      if(!d.hasAttribute('open')){d.setAttribute('data-was-closed','');d.setAttribute('open','');}
    });
    document.querySelectorAll('.section-body').forEach(function(w){
      if(w.style.display==='none'){w.setAttribute('data-was-hidden','');w.style.display='';}
    });
  }
  function restoreDetails(){
    document.querySelectorAll('[data-was-closed]').forEach(function(d){d.removeAttribute('open');d.removeAttribute('data-was-closed');});
    document.querySelectorAll('[data-was-hidden]').forEach(function(w){w.style.display='none';w.removeAttribute('data-was-hidden');});
  }
  window.addEventListener('beforeprint',openDetails);
  window.addEventListener('afterprint',restoreDetails);
})();
</script>

<!-- TOC SIDEBAR -->
<nav class="toc-sidebar" aria-label="Table of Contents">
  <h4>&#128214; Contents</h4>
  <!-- TOC links auto-built by JS above -->
</nav>

<!-- MAIN CONTENT -->
<div class="main-content">

Generate these sections in order (all inside the main-content div):

<h1 id="top">Inserting and modifying images Theory + PYQ — Lecture 7</h1>
<p style="text-align:center;color:#555;font-size:8.5pt;">CBSE | X IT | Part B – Unit 1: Digital Documentation (Advanced) using LibreOffice Writer | 35 min</p>

<h2 id="s1">1. Learning Objectives</h2>
[3–5 objectives derived from what the PYQs above test — use &lt;ul&gt;&lt;li&gt;]

<h2 id="s2">2. 35-Minute Lecture Flow</h2>
[HTML table: Time | Activity | Teacher Action — include a PYQ discussion slot]

<h2 id="s3">3. Concept Notes</h2>
[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 &lt;ol&gt;&lt;li&gt; for any menu-based task (examiners always ask "write steps to…")
  - .key-box with rules/properties as &lt;ul&gt;&lt;li&gt; for non-procedural content
  - .example-box for worked examples or screenshots description
  - &lt;pre&gt;&lt;code&gt; for code with .kw/.bi/.st/.cm/.nm token spans
  - .recall-box for expected output or result
  After each concept, embed 1–2 actual PYQs in .pyq-box with .pyq-meta (year · marks · type)
  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]

<h2 id="s4">4. Examiner Tricks &amp; Common Mistakes</h2>
[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]

<h2 id="s5">5. Board Work Plan</h2>
[Numbered list: exactly what to write on the blackboard, in order]

<h2 id="s6">6. Classroom Practice Questions</h2>
[Modelled on PYQ style. CRITICAL: every answer MUST be inside &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt; — never expose the answer directly.

3×1M MCQ — use this exact structure:
&lt;div class="mcq-box"&gt;
  &lt;b&gt;Q1.&lt;/b&gt; Question text?&lt;br&gt;
  &lt;ul class="options"&gt;
    &lt;li&gt;a) ...&lt;/li&gt;
    &lt;li&gt;b) ...&lt;/li&gt;
    &lt;li&gt;c) ...&lt;/li&gt;
    &lt;li&gt;d) ...&lt;/li&gt;
  &lt;/ul&gt;
  &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;
    &lt;ul class="options"&gt;
      &lt;li class="wrong"&gt;a) ... — reason why wrong&lt;/li&gt;
      &lt;li class="correct"&gt;b) ... ✓ — reason why correct&lt;/li&gt;
      ...
    &lt;/ul&gt;
  &lt;/details&gt;
&lt;/div&gt;
(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:
&lt;div class="self-test-box"&gt;&lt;b&gt;Q4.&lt;/b&gt; Question&lt;br&gt;&lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;Full answer&lt;/details&gt;&lt;/div&gt;

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:
&lt;div class="self-test-box"&gt;&lt;b&gt;Q7.&lt;/b&gt; Question&lt;br&gt;&lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;Full answer with exact menu path / numbered steps&lt;/details&gt;&lt;/div&gt;

1 case/application question — include ONLY if this topic naturally supports a case (do not force HOTS) — in .self-test-box with &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;answer&lt;/details&gt;]

<h2 id="s7">7. Step-by-Step Procedure Summary</h2>
[For every hands-on task in "Inserting and modifying images Theory + PYQ" — list the EXACT numbered steps a student must write in the exam.
Format each as: &lt;h3&gt;How to [task name]&lt;/h3&gt; followed by &lt;ol&gt;&lt;li&gt; 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.]

<h2 id="s8">8. PYQ Discussion (All 13 Questions)</h2>
[For EVERY single PYQ provided in Section 4 — no skipping.
Use this structure for each question:
  &lt;div class="pyq-box"&gt;
    &lt;div class="pyq-meta"&gt;[YEAR] · [X] Marks · [TYPE] · Section-[S]&lt;/div&gt;
    &lt;b&gt;Q.&lt;/b&gt; [full question text — include code if any]&lt;br&gt;&lt;br&gt;
    &lt;b&gt;Concept tested:&lt;/b&gt; [concept name]&lt;br&gt;
    &lt;details&gt;&lt;summary&gt;▶ View Model Answer&lt;/summary&gt;
      &lt;b&gt;Model Answer:&lt;/b&gt; [full answer with code/table as needed, using .kw/.bi/.st token spans in &lt;pre&gt;&lt;code&gt;]&lt;br&gt;
      &lt;b&gt;Common mistake:&lt;/b&gt; [what students get wrong — be specific]
    &lt;/details&gt;
  &lt;/div&gt;]

<h2 id="s9">9. Student Notes (Copy-ready)</h2>
[Concise notes — every concept from PYQs — in .key-box and .def-box; self-check questions in .self-test-box with &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;answer&lt;/details&gt;]

<h2 id="s10">10. Homework</h2>
[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).
 Mark difficulty with .critical/.high/.medium tag.
EVERY answer wrapped in &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt; inside .self-test-box or .mcq-box]

<h2 id="s11">11. Keyboard Shortcuts & Menu Paths</h2>
[ONLY include shortcuts/paths directly relevant to "Inserting and modifying images Theory + PYQ".
Table format: Shortcut/Path | Action | Notes
Include 4–8 entries. Mark exam-favourite shortcuts with a ⭐ note.
Wrap in &lt;table&gt;&lt;tr&gt;&lt;th&gt;Shortcut / Menu Path&lt;/th&gt;&lt;th&gt;Action&lt;/th&gt;&lt;th&gt;Notes&lt;/th&gt;&lt;/tr&gt;...&lt;/table&gt;]

<h2 id="s12">12. Exam Tips</h2>
[5 specific tips as .tip-box — derived from PYQ patterns for THIS topic only]

<h2 id="s13">13. Last-Minute Revision Cards</h2>
&lt;div class="card-grid"&gt;
[One .card per concept: &lt;div class="card-title"&gt;[concept]&lt;/div&gt; + 1 rule or shortcut + 1 real example]
&lt;/div&gt;

</div><!-- end .main-content -->
</body>
</html>

HARD OUTPUT RULES:
- Output ONLY the HTML document starting with &lt;!DOCTYPE html&gt;
- Do NOT wrap in markdown code fences
- Do NOT add explanatory text outside the HTML
- Use ONLY content from "Inserting and modifying images Theory + PYQ" — zero content from other topics
- Every PYQ in Section 4 MUST appear in Section 8 (PYQ Discussion) — no skipping
- Always finish the document completely through &lt;/html&gt;. If the answer is getting long, keep Sections 3 and 8 (PYQ Discussion) complete, then compact Sections 9–13 instead of truncating.
- If more than 15 PYQs are provided, fully discuss the highest-yield 15 and list the rest compactly in Section 8 with concept tested + exam trap.
- ANSWER HIDING (most important for student use):
    * Section 6 MCQs: options listed WITHOUT .correct/.wrong BEFORE details; full analysis only INSIDE &lt;details&gt;
    * Section 6 short/programming/HOTS, Section 9 self-check, Section 10 homework: EVERY answer in &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;
    * Section 8 PYQ Discussion: model answer + common mistake inside &lt;details&gt;&lt;summary&gt;▶ View Model Answer&lt;/summary&gt;
    * The beforeprint JS already auto-opens all &lt;details&gt; for printing — never skip this feature
- INLINE CODE SIZE RULE:
    * Inline code such as read(), write(), writelines(), tell(), seek(), open(), readline(), readlines() must appear almost the same size as surrounding normal text.
    * Do NOT use fixed 8.5pt size for all &lt;code&gt; elements.
    * Use code { font-size:0.95em; } for inline code.
    * Use pre { font-size:8.5pt; } for block code.
    * Use pre code { font-size:inherit; } so code blocks remain compact.
    * Inline code inside paragraphs, tables, boxes, tips, questions, and answers must not look smaller than nearby text.
- .pyq-box question text and concept must be OUTSIDE details (always visible); only the answer is hidden
- All content goes inside &lt;div class="main-content"&gt;
- The &lt;nav class="toc-sidebar"&gt; is already in the template — JS auto-builds TOC links
- Print buttons (.print-bar), including Read Mode, are in the template — DO NOT add them again; they auto-hide on print
- Include the full CSS and JS exactly as given, but use the updated CODE CSS section where inline &lt;code&gt; uses font-size:0.95em and block code uses pre { font-size:8.5pt; } with pre code { font-size:inherit; }.

================================================
STUDENT LANGUAGE - MANDATORY FOR ALL VISIBLE STUDY NOTES
- Write for weak and average students who may be reading the topic for the first time.
- Use very simple English, short sentences, and one idea per bullet. Keep the academic content correct, but make the wording easy.
- Start every concept with an "In simple words" explanation. Give the exact CBSE/exam definition only after the easy explanation.
- Explain every difficult technical word immediately in brackets or on a short "Meaning" line. Never assume the student already understands subject jargon.
- Split long or compressed sentences into two or three easy bullets. Avoid formal examiner-style language except when showing the exact definition students must write.
- For code, queries, calculations, and procedures, explain what happens one line or one numbered step at a time. Show the result/output clearly.
- Add one tiny familiar example immediately after each new rule. Do not introduce extra unrelated theory.
- Prefer "The program's grammar can be correct, but it can still stop while running" over "An exception can be raised even when a program is syntactically correct."
- Prefer "The finally block always runs. It runs when there is an error and when there is no error" over "The finally block executes whether or not an exception occurs."
- Do not remove correct subject terminology. Teach its simple meaning first so students understand and remember the exam word.
- Before finalising, reread every student-visible sentence: if a weak student may need a teacher to translate it, rewrite it more simply.
================================================

# ENHANCED PPT GENERATION PROMPT
## Topic: Inserting and modifying images Theory + PYQ | CBSE X IT IT

================================================
SECTION A -- VISUAL IDENTITY (READ FIRST, APPLY TO EVERY SLIDE)
================================================

COLOUR PALETTE -- "Deep Code" Theme
  Role              Hex        Name             Where Used
  Primary (dark)    #0D1B2A    Midnight Navy    Title bg, conclusion bg
  Secondary         #1B4F72    Ocean Blue       Section header cards, accent shapes
  Accent            #00D4FF    Cyan Electric    Keywords, callout borders, badges
  Neutral light     #F0F4F8    Ice White        All content slide backgrounds
  Warning/Error     #E74C3C    Alert Red        Common mistakes slide, warnings
  Success/Tip       #27AE60    Emerald Green    Tips, correct syntax, exam tips
  Text primary      #1A1A2E    Near Black       Body text on light slides
  Text on dark      #FFFFFF    Pure White       All text on dark background slides
  Text muted (dark) #C9D4E0    Slate Mist       Sub-lines / captions on navy slides

ON-LIGHT VARIANTS (use for ANY text, keyword, icon, or thin border on Ice White):
  Cyan  -> Accent-Deep  #0077A3      Emerald -> #1E8449      Red -> #C0392B
CONTRAST RULE: bright Cyan #00D4FF / Emerald #27AE60 / Red #E74C3C are for DARK
backgrounds or thick (>=4 pt) shape fills ONLY -- never for thin text, borders, or
badges on a light slide (bright cyan on Ice White is ~1.6:1 contrast = invisible
from the back row). On light slides always use the deep variants above.
ACCESSIBILITY RULE: never use colour as the only meaning. Pair warnings, tips,
correct answers, and definitions with a clear text label or simple symbol.

COLOUR DISCIPLINE -- 60 / 30 / 10 (a colour balance, not a rigid space quota)
  * Roughly 60% is the neutral Ice White base/background.
  * Roughly 30% is neutral structure -- cards, panels, diagrams, and readable text.
  * 10% -- and NO MORE -- is the accent (Cyan Electric or one status colour). One
    accent MOMENT per slide: the focal chip, the keyword, the one arrow that
    matters. A slide where every box is coloured has NO accent -- it is noise.
  * Keep useful breathing space around the focal content (aim for about 30-40%
    when practical), but NEVER squeeze content into a small area merely to meet a
    percentage. Code, question, table, and diagram slides may use more of the canvas.
  * Build depth with TINTS of one hue, never many saturated hues. A card fill is a
    6-8% tint of its header colour (pale-blue body under an Ocean Blue header),
    never a strong fill behind text. Status tints: blue 6% = definition,
    green 6% = correct/tip, red 6% = wrong/trap. Borders are 1 pt in the deep
    variant -- not thick coloured frames.
  * Navy dominates ONLY the Title and Key Takeaways slides. Never split a content
    slide 50/50 navy-vs-white -- it destroys hierarchy.

GRID & COMPOSITION (the missing rule that makes slides look intentional)
  * Lay every content slide on a 12-column grid inside the safe area with a
    consistent ~0.2 inch gutter. Snap every card, text block, icon and diagram
    edge to a column line -- never free-float objects at arbitrary x positions.
  * ONE alignment spine per slide: a single left text column (Left Visual+Text),
    two balanced 6-column halves (Two Column), or one centred focal object
    (Callout / Exam Spotlight). Do not mix three alignments on one slide.
  * Align tops and left edges across objects. Ragged, slightly-off edges are the
    #1 reason a slide reads as amateur even when nothing technically overlaps.

VISUAL HIERARCHY -- ONE FOCAL POINT PER SLIDE
  * Every slide answers "what is the ONE thing the eye lands on first?" Make that
    element the largest / boldest / the only accent-coloured object; everything
    else is visibly secondary (smaller, neutral, lighter).
  * Hierarchy comes from SCALE CONTRAST and SPACE, not from boxing everything. A
    big number, one code/steps line, or a single diagram surrounded by white beats
    three equal-weight bordered boxes every time.
  * Reserve bold + accent colour for the focal point ONLY. If three things are
    bold and coloured, nothing is emphasised.

INFORMATION-CARRYING VISUALS (the default -- not decorative chrome)
  * The visual must MEAN something: it carries the concept, it is not an ornament
    around text. Prefer, in order: a labelled code-breakdown (one code/steps line on a
    dark card with arrows naming each part's role), a before/after, a flow
    (input -> process -> output), a comparison table, a decision tree.
  * A rounded box with a clip-art icon beside a bullet is chrome -- it explains
    nothing and should be cut. One strong visual that teaches the idea beats four
    small decorative ones.
  * Icons: line-style, ONE consistent family, used to label SECTIONS only -- not
    one circle per bullet. An icon on every line is clutter, not design.

TYPOGRAPHY -- CLASSROOM-OPTIMISED (NON-NEGOTIABLE)
  Element             Font              Size   Weight    Notes
  Slide title         Montserrat        44 pt  Bold      Visible from back row (Arial Bold if Montserrat unavailable)
  Focal number/word   Montserrat        60+ pt Bold      The one hero element may go large for scale contrast
  Section header      Arial             32 pt  Bold      Sub-headings inside slides
  Body bullets        Calibri           28 pt  Regular   MAX 3 bullets -- min 28 pt
  Code text           Courier New       24 pt  Regular   On dark card only
  Captions/labels     Calibri           20 pt  Regular   Metadata/footer only; never instructional content

  NEVER go below 24 pt for instructional content.
  Non-instructional metadata only (footer, source, year/marks badge) may be 18-20 pt.
  NEVER use Aptos, Thin fonts, or Calibri Light.
  Line spacing 1.15+. Title case for titles; sentence case for body.

VISUAL MOTIF -- "Bracket Accent" (restrained signature, not the main visual)
  * Use the small { } mark on the Title, section-transition, and Key Takeaways
    slides only. Do not stamp it on every content slide. It is a signature, never
    a required decoration or the slide's main visual.
  * Definitions: a single rounded callout with a 4 pt Cyan-Electric LEFT border
    only (no full frame). Code: dark #0D1B2A card, #00D4FF keywords, white rest.

MOTION & TRANSITIONS
  * Build a static classroom deck by default. Use no decorative animation,
    bouncing objects, sound, auto-advance, or random transitions.
  * If a reveal is pedagogically necessary, use one simple Appear/Fade sequence
    on that slide only. The slide must remain understandable when printed.

DESIGN NEVER-DO LIST
  NO accent lines below titles
  NO colour bars or stripes spanning full slide width
  NO vertical sidebar stripes
  NO cream/beige backgrounds
  NO saturated colour fills behind body text (use 6-8% tints instead)
  NO icon-circle on every bullet, no clip-art decoration
  NO three competing focal points -- exactly one hero element per slide
  NO evenly-tiled grid of identical boxes whose only job is to fill the slide
  NO forced decoration. Instructional slides should use ONE information-carrying
     visual when it improves understanding; Agenda and question-only slides may
     rely on strong typography and spacing instead.
  NO centred body text -- left-align all bullets
  NO more than 3 bullets per slide
  TARGET 12 words per bullet; HARD MAX 14 words and one idea per bullet
  NO instructional font below 24 pt; metadata may be 18-20 pt

LAYOUT VARIETY -- ROTATE WHEN IT HELPS CLARITY
  Layout Name         When to Use
  Full-bleed Dark     Title slide, Key Takeaways slide
  Left Visual+Text    Theory slides -- one meaningful line icon/diagram left, bullets right
  Two Column          Comparisons (crop vs resize, link image vs embed image, raster vs vector, sharpen vs smooth, aging vs posterize, image mode vs image filter, image toolbar vs drawing toolbar, etc.)
  Code Card           All code/steps examples -- dark card on light background
  Callout Box         Definitions -- rounded rect, Cyan Electric border
  Exam Spotlight      PYQ question slides / practice slides -- large question centred on card
  3-Icon Grid         Key Takeaways -- 3 icons in equal columns
  Warning Banner      Common Mistakes -- red accent, alert icon

================================================
SECTION A1 -- LAYOUT SAFETY & OVERLAP PREVENTION
================================================

NON-NEGOTIABLE SAFE ZONE RULES:
  * Every slide must use a fixed 16:9 widescreen canvas.
  * Keep a minimum 0.35 inch margin from all slide edges.
  * No text box, badge, icon, card, or diagram may overlap another object.
  * Title area must be reserved separately from body area.
  * Body content must start only after the title area ends.

TITLE SAFE AREA:
  * Single-line title box: y=0.35-1.05 inch. Two-line title box: y=0.25-1.40 inch.
  * If a top-right badge is present, keep the title inside x=0.65-9.55 inch and
    reserve x>=10.0 inch for the badge. Otherwise the title may use the safe width.
  * No icon, card, or body text may enter the active title zone.
  * If a title is long, wrap into maximum 2 lines; never squeeze or overlap it.
  * Never allow title text to touch badges or cards.

BADGE PLACEMENT RULE:
  * Badges such as "Quick Recap", "PYQ", "1M", "60 seconds" must be placed
    in a fixed safe badge zone.
  * Badge zone: top-right corner, x >= 10.0 inch, y between 0.35 and 0.85 inch.
  * Badge must never be placed near the centre title area.
  * Badge text must stay inside the badge shape with 0.08 inch internal padding.

BODY SAFE AREA:
  * Body content begins at y >= 1.45 inch after a one-line title and y >= 1.70
    inch after a two-line title.
  * Large cards/callouts begin at y >= 1.55 inch (one-line title) or y >= 1.80
    inch (two-line title).
  * Main content must finish by y=6.70 inch. Footer/metadata uses y=6.90-7.10 inch.
  * Do not place main content in the footer zone.

TEXT FITTING RULE:
  * Do NOT shrink font below the required size.
  * If content does not fit, split into a continuation slide.
  * Use "(contd...)" in the title for continuation slides.
  * Never use PowerPoint auto-fit that reduces font size.
  * Never compress line spacing below 1.05.

OBJECT COLLISION CHECK -- before finalising each slide, verify:
  [ ] Title does not overlap badge.
  [ ] Badge does not overlap title or body.
  [ ] Body text does not overlap cards or icons.
  [ ] Code card has enough internal padding.
  [ ] No object is outside slide boundary.
  [ ] All text is fully visible after rendering.

RENDER QUALITY CHECK:
  After creating the PPT, render every slide as an image and inspect all
  rendered slides visually. If any slide has overlapping, clipped, hidden, or
  tiny text: fix the layout, split the slide if needed, render again, and only
  then provide the final PPT.

STRICT FAILURE RULE:
  A slide with overlapping text, clipped title, hidden badge, or unreadable
  content is considered FAILED and must be rebuilt before delivery.

================================================
SECTION B -- CONTENT SPECIFICATION
================================================

Topic     : Inserting and modifying images Theory + PYQ
Lecture   : #7 | Target duration: 35 min | Board: CBSE
Chapter   : Part B – Unit 1: Digital Documentation (Advanced) using LibreOffice Writer
Class     : X IT | Subject: IT
Audience  : Class X, CBSE Board, average to above-average students preparing for board exams

STRICT RULE: Every slide must be about "Inserting and modifying images Theory + PYQ" ONLY.

GENERATED STUDY NOTES HTML INPUT (OPTIONAL BUT PREFERRED):
  If the user provides/pastes the generated HTML study notes file for this lecture,
  treat that HTML as the AUTHORITATIVE Combined Theory + PYQ source for the deck.
  Theory slides come from the concept sections of the HTML.
  Examiner-trap and common-mistake slides may be summarised from the HTML.
  PYQ Practice slides must follow Section F's Actual PYQ Set rule.
  Do NOT copy long HTML paragraphs verbatim.
  Convert theory into slide-friendly bullets, examples, comparisons, diagrams, and speaker notes.
  Convert PYQ discussion into question-only slides plus answer/explanation slides.

DECK GOAL: COMBINED THEORY + PYQ in ONE deck — a single lecture slot covers both,
because there was no room for a separate PYQ lecture. Split the deck into two halves:
  FIRST teach the core concepts CONCISELY — lead with the CRITICAL & CONFUSING concepts
  flagged in Section F, disambiguate look-alike pairs, one tight worked example each. Do
  NOT pad the theory; you must leave room for the PYQ drill.
  THEN spend the back half on the REAL previous-year questions provided below — show the
  actual questions on slides, then model answers with the examiner trap for each.
Cover every concept the analysis names, but stay tight so both halves fit one deck.

SLIDE COUNT -- DETERMINE BY CONTENT, NOT A FIXED NUMBER:
  Do not compress or stretch the topic to hit a fixed slide count.
  For a single-concept Combined Theory + PYQ deck, typical deck size is 14-22 slides.
  For multi-concept Combined Theory + PYQ decks, typical deck size is 20-32 slides.
  The actual count depends on concept density, number of source PYQs, unique traps,
  and answer-slide grouping.
  Never stretch a small concept only to reach a large slide count.
  Never cram theory and PYQ answers into unreadable slides by shrinking fonts or overcrowding.

  Combined deck rhythm:
    * Start with Title, Agenda, Prior Knowledge Check.
    * Use concise theory slides first.
    * Add Common Mistakes immediately after theory.
    * Use a PYQ Practice block in the back half.
    * End with Key Takeaways and Exit Ticket.
    * CRITICAL/HIGH subtopics listed in Section D get dedicated slides.
    * MEDIUM subtopics may share a slide unless they have multiple distinct cases.
    * If a subtopic has MULTIPLE DISTINCT CASES (e.g. several methods/steps with different behaviour),
      give EACH case its own slide or clearly separated section — never
      compress distinct cases into one bullet list just to save slides.
    * CRITICAL-priority subtopics (Section F) --> 2 slides: theory + worked example.
    * HIGH-priority subtopics --> 1 dedicated slide.
    * MEDIUM-priority subtopics --> 1 bullet on a shared slide, UNLESS that
      subtopic has multiple distinct cases (above), then give it its own slide too.
    * CONTINUATION (encouraged — do NOT cram): when one concept needs more room
      than a single slide allows (more than 3 bullets, or theory + worked example
      + an exam trap), SPLIT it across consecutive slides. Title the overflow slide
      "<SAME TOPIC> (contd...)" and add a small "...continue ->" marker bottom-right
      of the first slide so the flow is obvious. Two clean slides always beat one
      crowded slide — never shrink the font or exceed 3 bullets just to make it fit.
  Fixed-position slides (always present, regardless of total count):
    Title, Agenda, Prior Knowledge Check        -- start of deck
    Common Mistakes                         -- immediately after content slides
    PYQ Practice block:
      Use all 13 actual PYQs.
      First create 3-5 question-only slides, grouping questions by pattern.
      Then create grouped answer/explanation slides by concept pattern.
      Every actual PYQ must be visibly accounted for; no PYQ may be silently dropped.
      This block may contain 7-11 slides depending on grouping and readability.
    Key Takeaways, Exit Ticket              -- final two slides, in that order


EXPLAIN FOR UNDERSTANDING, NOT JUST RECALL (the most important rule here):
  A student must understand the concept by reading the slide ONCE, without
  the teacher's voice filling gaps. For every theory/definition slide:
    * Start with a one-line plain-English restatement ("In simple words: ...")
      — not just the textbook/jargon definition.
    * Follow with ONE tiny concrete example showing the concept in action
      (a real step, a real value, a real before/after) — never leave
      a definition abstract with no example near it.
    * If two things are easily confused, show them side by side on a Two Column slide — never describe
      look-alike concepts on separate, disconnected slides.

================================================
SECTION C -- SLIDE OUTPUT FORMAT (USE EXACTLY)
================================================

+=======================================================+
SLIDE [n]: [SLIDE TITLE IN CAPS]
Layout     : [Full-bleed Dark / Left Visual+Text / Two Column /
              Code Card / Callout Box / Exam Spotlight /
              3-Icon Grid / Warning Banner]
Background : [#0D1B2A or #F0F4F8]
Title font : Montserrat Bold -- 44 pt on body slides / 54 pt on the Title slide
Body font  : Calibri 28 pt Regular
-------------------------------------------------------
VISUAL ELEMENT: [icon/shape/code card/diagram on this slide]

[Bullet 1 -- target <=12 words; hard max 14]
[Bullet 2 -- target <=12 words; hard max 14]
[Bullet 3 -- target <=12 words; hard max 14]

Do not add a coloured circle to every bullet. Use status colour only when a
bullet genuinely represents a definition, correct/tip, or warning.

CODE/STEPS SLIDES -- paste inside dark card:
  +------------------------------------------+
  |  Step 1: ...  (Courier New 24 pt)        |
  |  Result: [what student sees]             |
  +------------------------------------------+
  OUTPUT / RESULT: [expected output]

DIAGRAM SLIDES: describe shapes, arrows, labels, layout
-------------------------------------------------------
SPEAKER NOTES: [2-3 sentences for teacher -- NOT on slide.
Real-life analogy / Did You Know fact / exam tip / story.
EXCEPTION -- on Exit Ticket slides the notes carry the COMPLETE answer + explanation; PYQ Practice answer slides instead show the full solution + explanation + Critical Trap directly ON the slide (never in notes) (code may span many lines).]
+=======================================================+

================================================
SECTION D -- MANDATORY SLIDE SPECIFICATIONS
================================================

TITLE SLIDE (slide 1)
  Layout     : Full-bleed Dark (#0D1B2A background)
  Topic name : "Inserting and modifying images Theory + PYQ" -- 54 pt Bold Cyan Electric (#00D4FF)
  Sub-line 1 : "X IT IT" -- 32 pt White
  Sub-line 2 : "CBSE Board | Lecture 7" -- 24 pt Slate Mist (#C9D4E0)
  Motif      : semi-transparent { } bracket centred background (15% opacity)

AGENDA (slide 2)
  Layout     : Left Visual+Text
  Show at most 6 readable agenda rows. Group closely related subtopics under one
  short row; if grouping would hide meaning, use an Agenda (contd...) slide.
  Use one small section icon per row only when it adds meaning; no icon circles.

PRIOR KNOWLEDGE CHECK (slide 3)
  Layout     : Callout Box centred
  Single question in large rounded rectangle
  Badge      : "Think -> Pair -> Share" top-right
  Speaker notes: real-life analogy (NOT on slide)

CONTENT SLIDES (as many as the SLIDE COUNT rules in Section B require)
  Subtopics to cover (allocate slide count by PYQ FOCUS priority in Section F):
  * Inserting and modifying images

  Layout rules:
  * Avoid repeating the same layout twice in a row unless the second slide is a continuation, paired worked example, or necessary code-tracing slide. Clarity is more important than artificial layout rotation.
  * Theory    --> Callout Box for definition + Left Visual+Text for bullets
  * Examples  --> Code Card (dark card, Courier New 24 pt, keywords Cyan Electric)
  * Comparisons / look-alike concepts --> Two Column layout
  * Apply the EXPLAIN FOR UNDERSTANDING rule (Section B) to every theory slide
  * CRITICAL priority subtopics --> 2 slides (theory + worked example)
  * HIGH priority subtopics     --> 1 dedicated slide
  * MEDIUM priority subtopics   --> 1 bullet on a shared slide, UNLESS it has
    multiple distinct cases (Section B), then give it its own slide too

COMMON MISTAKES & EXAMINER TRAPS (right after all content slides)
  Layout     : Warning Banner
  Accent     : left thick border #E74C3C (4 pt) on each bullet card
  Title      : "DON'T MAKE THESE MISTAKES" -- 44 pt Bold Deep Red #C0392B
  EXACTLY 3 bullets -- specific PYQ traps with red alert icon

PYQ PRACTICE -- THIS IS THE PYQ HALF OF A COMBINED THEORY+PYQ DECK.
The theory slides above already taught the concept; now drill the REAL previous-year
questions.

  STEP 1 -- QUESTION-ONLY SLIDES:
    QUESTION-ONLY SLIDE RULE:
    * Use 3-5 Exam Spotlight question-only slides.
    * Group questions by concept pattern.
    * Never force 13 questions into only 2-3 slides if readability suffers.
    * Keep all visible text at or above required font size.
    * If a question with options becomes crowded, split into another question-only slide.
    * Readability is more important than reducing slide count.
    * Show all 13 actual PYQs.
    * Group by: identifiers; keywords; comments;
      Python basics / file extension / high-level language; implicit variable declaration.
    * Show question text, real year badge, and marks badge.
    * Do not show answer, explanation, or trap on question-only slides.

  STEP 2 -- GROUPED ANSWER / EXPLANATION SLIDES:
    * Create grouped answer slides by concept pattern, not necessarily one slide per question.
    * Each answer slide may cover 2-3 related 1M questions if readable.
    * For each PYQ shown, include final answer, one-line explanation, marking point,
      and a "Critical Trap" callout directly ON the slide.
    * If one slide becomes crowded, split it into continuation slides.
    * Speaker notes contain teacher dialogue, timing advice, and peer-marking guidance.
  Placement  : after Common Mistakes and before Key Takeaways

KEY TAKEAWAYS (second-to-last slide)
  Layout     : 3-Icon Grid (dark #0D1B2A background -- matches title)
  3 equal columns: large icon + 1-line heading (28 pt Bold) + 1-line summary (24 pt)
  EXACTLY 3 takeaways

EXIT TICKET (last slide)
  Layout     : Callout Box centred
  EXACTLY 1 MCQ or fill-in-the-blank -- question 32 pt, options 28 pt
  Timer badge: "60 seconds" top-right (Cyan Electric)
  ANSWER + EXPLANATION ONLY IN SPEAKER NOTES

================================================
SECTION E -- ENGAGEMENT RULES (MIN 2 IN SPEAKER NOTES)
================================================

1. Prior Knowledge Check slide: real-life analogy -- NOT textbook language
2. One slide: "Did You Know?" fun fact in speaker notes
3. One code/steps slide: "Guess the Output?" -- ask class before revealing
4. Semantic colour only when useful: deep red = warning, deep green = tip,
   deep blue = definition. Ordinary bullets remain Near Black; never colour every bullet.
5. Common Mistakes slide: one "Examiner Trap" with specific wrong answer students typically write

================================================
SECTION F -- PYQ FOCUS (WEIGHT SLIDES BY EXAM IMPORTANCE)
================================================

Board exam appearances: 13 times (2023-2026) | Total marks tested: 15M

DECK INTENT: build this as the POLISHED, EXAM-FOCUSED version of the study
notes — cover EVERY examiner-tested concept below (not just definitions),
and lead with the CRITICAL + CONFUSING concepts, giving them the most slide time.

TOP PRIORITY -- CRITICAL & CONFUSING CONCEPTS (open the content with these):
  ! Inserting and modifying images — asked as MCQ/Short Answer; at 1,2M; 13x repeated --> own concise theory focus + PYQ drill priority; if it has a look-alike, use a Two-Column 'X vs Y' compare slide.

SUBTOPIC PRIORITY (allocate slide count by this ranking — see SLIDE COUNT rules in Section B):
  CRITICAL --> concise concept teaching first, then highest-priority PYQ drill
    * Inserting and modifying images — 13x in exams, 15M total (years: 2026, 2025, 2024)

===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Inserting and modifying images
  Pattern: MCQ=11, Short Answer=2 | Marks: 1M=11, 2M=2 | Total: 13 questions
  [MCQ] [1M] [Medium] × 2
    → Core concept of Inserting and modifying images
  [MCQ] [1M] [Easy] × 9
    → Core concept of Inserting and modifying images
  [Short Answer] [2M] [Hard] × 2
    → Core concept of Inserting and modifying images


===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Inserting and modifying images | 57 | 13 | 15M | 2026, 2025, 2024 | CRITICAL |

EXAMINER FINGERPRINT -- TRAPS TO COVER INTERNALLY

Use this section only for internal slide planning. Do not print this
heading or these internal labels on slides.

For this lecture, the deck must strongly cover these traps:

No static trap list was supplied for this lecture -- self-generate 4-7 traps from:
  * actual question patterns
  * common wrong assumptions
  * output-tracing traps
  * syntax-vs-runtime traps
  * comparison traps
  * order/sequence traps
  * look-alike concept traps

* Common Mistakes slide must select the top 3 traps from this Examiner
  Fingerprint list.
* PYQ Practice slides must together cover at least 4 traps from the Examiner Fingerprint list.
* Content slides must teach the traps before practice slides test them.

ACTUAL PYQ SET FOR PRACTICE
  Source pool has 13 PYQs.
  Since the pool has 15 or fewer questions, use all 13 actual PYQs.
  Do not replace these with newly framed representative questions.
  Do not compress by dropping, replacing, paraphrasing, or hiding actual PYQs.
  All 13 actual PYQs must appear visibly in the question-only block.
  Grouping related answers on the same answer/explanation slide is allowed only
  for layout efficiency, provided every PYQ still gets:
    - final answer
    - one-line explanation
    - marking point
    - Critical Trap
  Order questions Easy -> Tough; within difficulty, order 1M -> 2M -> 3M -> 4/5M.
  Every PYQ must be visibly accounted for in the question-only block
  and in grouped answer/explanation coverage by concept pattern.
  Each PYQ needs a final answer, one-line explanation, marking point,
  and Critical Trap directly on an answer/explanation slide.
  Do not create substitute or compressed questions for this small source pool.

  Pattern 1. [1M] [Medium/MCQ] Concept: Inserting and modifying images | source example: 2023
  ```
  Reema has created a pamphlet on Tour to West India. She has inserted many images to make it more presentable but the size of images is occupying a lot of space. Her friend has suggested her to reduce the size of images. Which of the following options will help her in doing the task without losing any content of the image?
  (A) Recolor
  (B) Docking
  (C) Resize
  (D) Rotate
  ```
  Pattern 2. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2023
  ```
  Which of the following Graphic filter is used to increase the contrast of an image in a document?
  (A) Smooth
  (B) Sharpen
  (C) Remove Noise
  (D) Invert
  ```
  Pattern 3. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2023
  ```
  Mehul has inserted images in his document report "Travel My State" to make it more descriptive. Some of the images are having some extra part that needs to be removed. Which of the following option is suitable to do the task?
  (A) Resize
  (B) Crop
  (C) Recolor
  (D) Rotate
  ```
  Pattern 4. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2023
  ```
  To increases the contrast of an image, __________ option is used in a document.
  (a) Smooth
  (b) Sharpen
  (c) Aging
  (d) mosaic
  ```
  Pattern 5. [2M] [Hard/Short Answer] Concept: Inserting and modifying images | source example: 2023
  ```
  Differentiate between Keep scale and Keep image size options while cropping an image in a document.
  ```
  Pattern 6. [2M] [Hard/Short Answer] Concept: Inserting and modifying images | source example: 2023
  ```
  Differentiate between Aging and Posterize graphic filters.
  ```
  Pattern 7. [1M] [Medium/MCQ] Concept: Inserting and modifying images | source example: 2024
  ```
  Gaurav is creating a report in Writer. The image gets embedded in his document whenever he drags and drops the image and the document size increases. Suggest a way to link the image file instead of embedding it.
  (A) Drag and drop the image.
  (B) Hold down the Ctrl key while dragging.
  (C) Hold down the Shift key while dragging the image.
  (D) Hold down the Ctrl and Shift key while dragging and dropping the image.
  ```
  Pattern 8. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2024
  ```
  Resizing a _____ may badly affect the resolution of an image.
  (A) Vector image
  (B) Raster image
  (C) CAD image
  (D) Coloured image
  ```
  Pattern 9. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2024
  ```
  Which feature allows you to jump to a different document, spreadsheet, or website from within a document?
  (a) Bookmark
  (b) Page Break
  (c) Hyperlink
  (d) Format Painter
  ```
  Pattern 10. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2024
  ```
  What is the benefit of inserting an image as a link in a document?
  (a) It reduces the document size by storing only the reference to the image.
  (b) It enhances the image quality.
  (c) It allows for automatic image editing within the document.
  (d) It removes the need for image captions.
  ```
  Pattern 11. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2025
  ```
  During a recent excursion, Roshni has taken some pictures for making a report in Writer. She wants to increase the contrast of the images. Which one of the following image filters should she use in Writer ?
  (A) Aging
  (B) Mosaic
  (C) Sharpen
  (D) Smooth
  ```
  Pattern 12. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2026
  ```
  Which of the following image tools is used to change the image to black and white, grayscale or a watermark ?
  (A) Image Crop
  (B) Image Mode
  (C) Image Align
  (D) Image Size
  ```
  Pattern 13. [1M] [Easy/MCQ] Concept: Inserting and modifying images | source example: 2026
  ```
  Ravi wants to use tools for filtering, resizing, cropping and rotating of an image inserted in his project created in LibreOffice Writer. Which toolbar should he use to access these tools ?
  (A) Image
  (B) Drawing
  (C) Formatting
  (D) Standard
  ```

SLIDE WEIGHTING RULE:
  CONFUSING/CRITICAL concepts --> concise concept teaching first, then highest-priority PYQ drill;
                                  use 'X vs Y' compare slides for look-alikes
  HIGH subtopics     --> own slide
  MEDIUM subtopics   --> 1 bullet max on a shared slide
  Every concept named in the QUESTION PATTERN BANK above MUST appear on a slide —
  a concept the board has actually tested may NEVER be dropped to save slides.

SOURCE POOL RULE:
  Because this source pool has only 13 PYQs, use all 13 actual PYQs.
  Do not drop, replace, paraphrase, or hide any actual PYQ.
  Every PYQ must appear visibly in the question-only block.
  Grouping related answers is allowed only for layout efficiency.
  Compression by omission is allowed only when source pool has more than 15 PYQs.
  If the pool has 15 or fewer PYQs, every actual PYQ must be included and accounted for.
  If a question is reproduced verbatim, show its real year and marks.
  Never fabricate a year, section, paper, or marks badge.

PYQ PRACTICE QUESTION RULE:
  Use all 13 actual PYQs from the source pool.

  QUESTION-ONLY SLIDE RULE:
  Use 3-5 Exam Spotlight question-only slides.
  Group questions by concept pattern.
  Never force 13 questions into only 2-3 slides if readability suffers.
  Keep all visible text at or above required font size.
  If a question with options becomes crowded, split into another question-only slide.
  Readability is more important than reducing slide count.

  Create:
    * 3-5 question-only slide(s), grouped by concept pattern
    * grouped answer/explanation slide(s), grouped by concept pattern
  The authoritative count is 13 actual PYQs, not a fixed number of slides.
  The PYQ block may contain 7-11 slides total depending on grouping and readability.
  Never shrink font below the required size to fit more answers.
  Split into continuation slides whenever needed.

  PYQ ANSWER VISIBILITY RULE:
  Question-only slides:
    - Show only question text, marks badge, and real year badge.
    - No answer, explanation, or trap on the slide.
    - Speaker notes may contain the answer for teacher reference.
  Answer/explanation slides:
    - Show final answer directly ON the slide.
    - Show one-line explanation directly ON the slide.
    - Show marking point directly ON the slide.
    - Show "Critical Trap" callout directly ON the slide.
    - Speaker notes carry teacher dialogue, timing advice, and peer-marking guidance.

NO-FABRICATION RULE:
  Use all 13 actual PYQs from the source pool.
  If the source pool has 15 or fewer PYQs, every actual PYQ must be included and accounted for.
  If a PYQ is reproduced verbatim, show its real year and marks.
  If the source pool has more than 15 PYQs and compression is necessary, representative
  questions may be used only after the highest-yield 15 are fully discussed.
  Representative questions must be labelled "Representative PYQ-pattern question"
  and must not show fake year or fake marks.
  Never fabricate a previous-year question, year, section, paper, or marks badge.
  Never silently drop a source PYQ.

================================================
SECTION G -- QUALITY CHECKLIST (VERIFY BEFORE OUTPUT)
================================================

Visual Checks:
  [ ] Title font >= 44 pt on every slide
  [ ] Body font >= 28 pt on every slide
  [ ] Code font >= 24 pt inside dark card only
  [ ] No instructional font below 24 pt; metadata/footer only may be 18-20 pt
  [ ] No decorative visual was forced onto Agenda or question-only slides
  [ ] No unnecessary repeated layout; continuation, paired worked-example, and necessary code-tracing slides may repeat layout.
  [ ] Sandwich: dark Title -> light content -> dark Key Takeaways -> light Exit Ticket
  [ ] { } bracket motif appears only on Title/transition/Key Takeaways slides
  [ ] NO accent lines under titles
  [ ] NO full-width colour bars or stripes
  [ ] NO cream/beige backgrounds
  [ ] Bullets left-aligned (titles centred only)
  [ ] ONE clear focal point per slide (one hero element, one accent moment)
  [ ] Objects snapped to the grid -- tops/left edges aligned, nothing free-floating
  [ ] Accent colour <= 10% of slide area; cards use 6-8% tints, not saturated fills
  [ ] Every slide's visual carries meaning (no decorative icon-circles / clip-art)
  [ ] Content has useful breathing space without being squeezed into a fixed quota

Content Checks:
  [ ] CRITICAL/HIGH subtopics in Section D have dedicated slides
  [ ] MEDIUM subtopics are covered on shared slides unless they have multiple
      distinct cases
  [ ] Multi-case subtopics have EACH case
      covered, not compressed into one slide
  [ ] Every theory slide has a plain-English restatement AND a concrete example
  [ ] No slide has more than 3 bullets
  [ ] Bullets target <=12 words and never exceed 14 words or one idea
  [ ] Every substantial code/steps example has a Code Card slide; tiny
      inline snippets may stay beside the explanation when readable
  [ ] Common Mistakes slide has EXACTLY 3 examiner traps (red accent)
  [ ] All 13 actual PYQs are used/accounted for.
  [ ] For source pools of 15 or fewer PYQs, all actual PYQs are included.
  [ ] Question-only block contains 3-5 slides.
  [ ] No question-only slide is overcrowded.
  [ ] MCQ options remain readable without shrinking fonts.
  [ ] Answer/explanation slides are grouped by concept pattern.
  [ ] Every PYQ has visible answer/explanation coverage.
  [ ] No actual PYQ is silently dropped.
  [ ] Question-only slides show no answer, no explanation, and no trap.
  [ ] Answer slides show final answer + explanation + marking point + Critical Trap directly on slide.
  [ ] PYQ Practice slides ordered easiest-to-hardest
  [ ] Key Takeaways slide has EXACTLY 3 takeaways in 3-Icon Grid layout
  [ ] Exit Ticket has 1 question with answer ONLY in speaker notes
  [ ] All speaker notes include teacher dialogue (EXCEPT PYQ Practice answer slides (answer is ON the slide, not in notes) & Exit Ticket (answer in notes) -- Section C)
  [ ] Minimum 2 engagement techniques across speaker notes

Layout Safety Checks:
  [ ] Every slide uses 16:9 widescreen canvas
  [ ] All objects keep at least 0.35 inch margin from slide edges
  [ ] Title uses the correct one-line or two-line safe area and wraps to max 2 lines
  [ ] Body/card start position moves down when the title wraps to two lines
  [ ] Badges stay in the top-right badge zone and never touch title/body
  [ ] No text, badge, icon, card, code block, or diagram overlaps another object
  [ ] No PowerPoint auto-fit has reduced required font sizes
  [ ] Continuation slides are used whenever content would otherwise crowd
  [ ] Rendered slide images have no clipped, hidden, overlapping, or tiny text

================================================
STUDENT LANGUAGE - MANDATORY FOR EVERY SLIDE AND SPEAKER NOTE
- Write for weak and average students who may be learning the topic for the first time.
- Use very simple English, short sentences, and one idea at a time. Keep the academic depth correct, but make the wording easy.
- First explain an idea in everyday words. Then show the exact CBSE/exam term in brackets or on a separate "Exam term" line.
- Explain every difficult technical word the first time it appears. Do not use words such as syntactically, exception, handler, iteration, mutable, protocol, constraint, or aggregate without a simple meaning.
- Slide bullets must be direct and easy to read. Do not compress several instructions or rules into one bullet merely to meet the slide limit; use a continuation slide instead.
- For code, queries, calculations, and procedures, explain what happens one line or one step at a time. Show the result/output clearly.
- Speaker notes must sound like a teacher speaking to a struggling student: simple explanation, tiny example, then exam wording.
- Prefer "The finally block always runs. It runs with an error and without an error" over "The finally block executes whether or not an exception occurs."
- Prefer "Read the code one line at a time. Check end= because it keeps the next output on the same line" over compressed instructions such as "Trace output separators carefully."
- Do not remove correct subject terminology. Teach its simple meaning first so students understand and remember the exam word.
- Before finalising, reread every visible sentence: if a weak student may need a teacher to translate it, rewrite it more simply.
================================================

33932 chars Customise board, duration & level