Table of Contents

• Notebook Style Guide
  • Headings
  • Text Formatting

Table of Contents

• Blocks
• Concepts
• Vocabulary
• Notebook Style Guide

Blocks

Block What Your Notes Should Include Hat Block What it looks like, what it is used for, and where it belongs Stack / Command Block What it does and how it connects to other commands C-Block What the C-shape means and why blocks can be placed inside Reporter / Oval Block What it reports and where it can be used Boolean / Hexagonal Block What it reports and why it has a different shape Repeat Block Its shape, what it does, and what goes inside it Wait Until Block What it does and what kind of condition it needs If Then Block Its shape, how its condition works, and what happens when the condition is TRUE Forever Block Its shape and why programmers use it For each block, include:

Name: Shape/Type: What It Does: Concepts

Concept Your Notes Should Explain Sequence Why the order of commands matters Parameters How changing an input changes what a command does Loops / Iteration How and why programs repeat instructions Sensors How a robot gets information about its environment Booleans & Conditions How TRUE/FALSE information controls a program Sense → Think → Act How a robot senses information, makes a decision, and responds Comparisons How < and > compare values and produce TRUE/FALSE Coordinates How X and Y values describe the robot’s location Conditionals How programs make decisions using conditions Patterns How recognizing repeated behavior can help create better algorithms For each concept, include:

What It Means: In My Own Words: Vocabulary IMPORTANT: One Row = One Notebook Entry Some related terms have been grouped together.

If several terms appear in the same row, put them together in ONE notebook entry.

You should still explain every term listed in that row.

Notebook Entry Terms to Include VR Robot + Playground VR Robot, Playground Programming Language + Project Programming Language, Project Behavior + Command Behavior, Command Drivetrain Drivetrain Loop + Iteration Loop, Iteration Sensor + Bumper Sensor Sensor, Bumper Sensor Boolean + Condition + TRUE/FALSE Boolean, Condition, TRUE, FALSE Distance Sensor + Threshold Distance Sensor, Threshold Coordinate Plane + X/Y Coordinates Coordinate Plane, X-axis, Y-axis, X-coordinate, Y-coordinate Location Sensor Location Sensor Comment Comment Eye Sensor Eye Sensor Conditional Statement Conditional Statement Markdown Style Guide

Boolean, Condition, TRUE/FALSE

**Definition:** A Boolean is a value that can only be TRUE or FALSE. A condition is a question or statement that produces a Boolean result. **In My Own Words:** The program checks a condition like a yes-or-no question. The answer is either TRUE or FALSE, and the program can use that answer to decide what to do. **Example:** A Bumper Sensor can be used to check whether the bumper is pressed. Pressed = TRUE Not Pressed = FALSE

Markdown Style Guide for Coding Notebooks

Follow this guide to keep your coding notebook clear, consistent, and professional.

This ensures your notes are easy for you (and others) to read later.

---

Headings

When to use: Organize your notebook into sections (like days, topics, or projects).

• # for the notebook title (use once at the top).

• ## for each day or major topic.

• ### for subsections (like “Notes”, “Practice”, “Reflections”).

Example:

My Coding Notebook

Day 1

Notes

Practice

Text Formatting

When to use: Highlight important ideas or add emphasis.

Use bold for key terms or definitions.

Use italic for emphasis or side comments.

Use inline code for keywords, functions, or commands.

Example:

Class = a blueprint for objects

Remember: always test your code

Use System.out.println() to print

Boolean, Condition, TRUE/FALSE

Definition:
A Boolean is a value that can only be TRUE or FALSE. A condition is a question or statement that produces a Boolean result.

In My Own Words:
The program checks a condition like a yes-or-no question. The answer is either TRUE or FALSE, and the program can use that answer to decide what to do.

Example:
A Bumper Sensor can be used to check whether the bumper is pressed.

Pressed = TRUE
Not Pressed = FALSE

</details>

Code Blocks

When to use: Anytime you write multiple lines of code.

Inline code for short snippets.

Fenced code blocks with language for full examples.

Example:

public class Hello {

    public static void main(String[] args) {

        System.out.println("Hello World!");

    }

}

Lists

When to use: Organize steps, notes, or key points.

Numbered lists for sequences or steps.

Bulleted lists for unordered ideas.

Example:

Define the class Write the main method Test your program Variables

• Loops

• Conditionals

Checklists

When to use: Track progress on assignments or tasks.

Example:

[x] Complete coding warm-up

• Finish project draft

• Reflect on learning

Blockquotes

When to use: Call out notes, reminders, or teacher comments.

Example:

💡 Remember: Loops repeat code until a condition is false.

Tables

When to use: Compare values, track progress, or organize data neatly.

Example:

Task	Status	Notes
Homework 1	Done #	Submitted
Homework 2	Pending	Needs review

Links & Images

When to use: Add references, resources, or visuals.

Example:

Java Docs

To make an image that is a link, paste the image, then add the following before it, replacing website address with the link:

And after the image info, add: </a>

Collapsible Sections

When to use: Hide solutions, extended notes, or extra details.

Example:

Click to reveal solution

System.out.println("Answer: 42");

Footnotes

When to use: Add references or side notes without cluttering the page.

Example:

This concept is related to object-oriented programming.¹

Style Rules

Consistency matters more than creativity

Always use headings to structure your notes.

Always use code blocks for multi-line code.

Clarity first

Bold key terms.

Use lists instead of long sentences when outlining steps.

Professional tone

Don’t mix casual notes with formal work in the same section.

Use blockquotes for reflections or teacher feedback.

Track your learning

Use checklists to mark what’s done.

Use collapsible sections if you want to hide answers until review time.

Bottom Line:

Headings = Structure

Bold/Italic = Emphasis

Code blocks = Code

Lists = Steps/Ideas

Tables = Organization

Checklists = Progress

Blockquotes = Notes/Tips

Collapsible = Hide/Show detail

Keep it simple, consistent, and clear.

1. See “Objects and Classes” in your textbook. ↩