What to contact us about
The most useful correction includes the page URL, the heading or section where the problem appears, what is wrong, and what source or test result supports the correction. That helps keep fixes specific instead of vague. Good reports include broken downloads, missing internal links, confusing wording, stale instructions, unclear expected output, and unsafe command ordering.
For command-related pages, include the operating system, shell, command output, and whether the page should warn users before taking an action. For project pages, include which artifact, checklist, note, deck, or practice task failed to match the public page.
Report a broken page or download
If a note, deck, checklist, project page, reference page, or sitemap link breaks, send the URL where you clicked and the target URL that failed. If possible, include the browser message, status code, or filename. Static learning sites are only useful when their internal routes and downloads can be trusted.
Downloads are meant to be plain files that work without an account. Obsidian notes should open as Markdown. Anki-compatible decks should be tab-separated files. Practice checklists should be readable without special software. A broken or confusing download is worth reporting.
Report an unsafe command example
Unsafe command reports are high value. The safest TopicLadder command examples should inspect before changing state, name what the output proves, and warn before destructive or broad actions. Report any page that shows deletion, recursive permission changes, format commands, service restarts, firewall changes, database deletion, or direct downloads into a shell without enough context.
A good safety report says what can go wrong, what safer inspection command should appear first, and what page or project path needs the correction. The site should make dangerous shortcuts visible as mistakes to avoid, not as the first step.
Suggest a correction
Corrections are better than general opinions. If a lesson leaves out a needed prerequisite, if a glossary term is confusing, if a project path sends users to the wrong next step, or if a practice task checks the wrong skill, send the smallest change that would make the page more useful.
TopicLadder should improve by tightening pages, not by adding more pages that say the same thing. Reports that identify duplicate intent, weak explanations, missing source context, or unhelpful next steps are useful.
Limits
TopicLadder does not provide emergency help, custom engineering review, legal advice, medical advice, or real-time equipment repair. If a situation involves physical danger, workplace safety, production systems, money, credentials, or regulated work, use the appropriate qualified person and official documentation.
The current public site is designed for reading, downloading, and practice. It does not require a user account for public resources. If richer community features appear later, correction and moderation rules should stay stricter than the desire to publish quickly.
