Skip to main content

Complete Incomplete Pages Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Complete the flagged Markdown pages so they no longer contain placeholder or broken content and can be published as study notes.

Architecture: This is a content-only change. Keep file paths, front matter, and Docusaurus conventions stable while replacing incomplete sections in place.

Tech Stack: Docusaurus, Markdown/MDX, shell verification with rg, awk, and npm run build.

Task 1: Baseline Inventory​

Files:

  • Read: docs/Software_engineer_interview_prep/*.md

  • Read: flagged non-software Markdown pages

  • Create/update: /tmp/topperGuide_incomplete_pages_all.txt

  • Regenerate the incomplete-page list.

Run:

(rg -l '^\s*[0-9]+\.\s*(TBD\.\.\.|\.\.\.)\s*$' docs/Software_engineer_interview_prep; rg -l -i '\bTBD\b|placeholder\.com|via\.placeholder|content provided is a draft|^\s*\.\.\.\s*$|^\s*Let.s begin.*\.\.\.|^\s*Let.s dive deeper.*\.\.\.' docs blog src/pages privacypolicy -g '!docs/Software_engineer_interview_prep/**'; find docs blog privacypolicy src/pages -type f \( -name '*.md' -o -name '*.mdx' \) -print0 | xargs -0 awk 'FNR==1{if (file && count%2==1) print file; file=FILENAME; count=0} /^```/{count++} END{if (file && count%2==1) print file}') | sort -u > /tmp/topperGuide_incomplete_pages_all.txt
wc -l /tmp/topperGuide_incomplete_pages_all.txt

Expected: the count is close to the approved baseline of 185, allowing for pages fixed during execution.

Task 2: Structural Markdown Repairs​

Files:

  • Modify: pages reported by the odd-code-fence scan

  • For each page with an odd number of code fences, inspect the surrounding content.

  • Close or relabel the intended code block without changing unrelated prose.

  • Re-run the odd-code-fence scan until it returns no files.

Run:

find docs blog privacypolicy src/pages -type f \( -name '*.md' -o -name '*.mdx' \) -print0 | xargs -0 awk 'FNR==1{if (file && count%2==1) print file; file=FILENAME; count=0} /^```/{count++} END{if (file && count%2==1) print file}'

Expected: no output.

Task 3: Non-Software Content Completion​

Files:

  • Modify: the 32 non-software flagged pages

  • Replace placeholder images with text diagrams, Mermaid diagrams, or stable explanatory prose.

  • Replace dangling completion phrases with actual sections.

  • Remove draft disclaimers after improving the page.

  • For Indian criminal law content, update references to account for the Bharatiya Nyaya Sanhita, 2023 and Bharatiya Nagarik Suraksha Sanhita, 2023.

  • Preserve front matter.

Task 4: Software Interview Prep Completion​

Files:

  • Modify: the 153 flagged files in docs/Software_engineer_interview_prep/

  • Replace each placeholder ### Procedure body with a real explanation derived from the existing code and problem title.

  • Include algorithm intuition, step-by-step procedure, complexity, and key edge cases.

  • Preserve existing code blocks and metadata tables unless they are malformed.

  • Do not invent runtime claims or replace accepted code unless the Markdown is broken.

Task 5: Starter Page Cleanup​

Files:

  • Modify or delete: src/pages/markdown-page.md

  • Remove the default starter content from public routes, either by deleting the page or replacing it with a real site page if navigation expects it.

Task 6: Verification​

Files:

  • Read: all Markdown/MDX files

  • Run placeholder scan.

rg -n -i '\bTBD\b|placeholder\.com|via\.placeholder|content provided is a draft|^\s*\.\.\.\s*$|^\s*[0-9]+\.\s*(TBD\.\.\.|\.\.\.)\s*$|^\s*Let.s begin.*\.\.\.|^\s*Let.s dive deeper.*\.\.\.' docs blog src/pages privacypolicy

Expected: no true incomplete-page hits.

  • Run code-fence scan.
find docs blog privacypolicy src/pages -type f \( -name '*.md' -o -name '*.mdx' \) -print0 | xargs -0 awk 'FNR==1{if (file && count%2==1) print file; file=FILENAME; count=0} /^```/{count++} END{if (file && count%2==1) print file}'

Expected: no output.

  • Build the site.
npm run build

Expected: Docusaurus build succeeds.

Last updated on