64x64base

Suggest a Lesson

How educators, students, technical writers, and collaborators can suggest Laboratory Campus lessons and reviews.

The Laboratory Campus is open to lesson suggestions and review. Useful input can come from students, teachers, CS faculty, database practitioners, technical writers, curriculum reviewers, non-profit partners, and experienced developers.

For now, the intake path is static and email-based. A writable form can come later after the project chooses durable storage and moderation rules.

What to Suggest

Good suggestions fit one of these lanes:

LaneExamples
Student lessonA lab on records, indexes, relations, DotScript, mutation safety, HELP/CMDHELP, or database history.
Career lessonA lesson learned while building, recovering, documenting, testing, or teaching systems.
Review requestFeedback on prerequisites, learning sequence, accessibility, proof labels, or classroom safety.
Proof gapA place where the site claims something but needs stronger evidence or clearer status.
Dataset or case ideaA small inspectable dataset, historical case, or classroom scenario that could support a lesson.

Suggestion Template

Use this structure:

Title:
Suggested lane: student lesson | career lesson | review | proof gap | dataset/case
Audience:
Concepts:
Relevant page or file:
What the learner should do:
Expected observation:
What proof exists:
What still needs review:
Safety or mutation risk:
Your role or background:

Email Intake

Send suggestions to deraldg@msn.com.

Include "LabTalk lesson suggestion" in the subject and paste the template into the message body. For academic review, mention whether your perspective is CS, databases, technical writing, curriculum, general education, learning theory, or industry practice.

Review Rules

Lesson suggestions are strongest when they preserve these boundaries:

  • live runtime proof is different from source-defined behavior.
  • source memory is different from reviewed historical fact.
  • a simulation can be useful, but it must be labeled.
  • student-ready material needs setup, safety notes, expected observations, and proof links.
  • a draft can be public when the status is honest.