Lulu’s Github Notebook
Table of Contents
Blocks
Hat Block:
Looks like a square, It’s shaped to attach to below blocks but not block above it.
It’s used for starting a stack of blocks and it belongs at the very top of a stack.
Stack / Command Block:
Looks like a square, shaped to attach to below and above blocks for a chain.
It connects by clicking it into another block, or letting another block above it click into it.
C-Block:
Has a complex C shape, which means it can have blocks inside it because of the gap.
It can also let blocks click into it from the top, or click itself into a block below.
Reporter / Oval:
Reports values in the form of numbers.
Can be used anywhere with oval inputs, because it’s an oval.
Boolean:
It reports conditions as true or false.
Its shape is different because it allows to fit inside blocks that have the same hexadomical shape, rather than just stacking on them.
Repeat Block:
Shaped like a C, its shape allows it to have things inside it, over it and below it stacked.
Its especially useful for sensing, logic operator and drivetrain blocks, but every block type can attach to it.
Wait Until Block: It repeatedly checks a Boolean reporter block.
It wont move to the next block until the Boolean block allows it.
If Then Block:
Shaped like a C to stack up and down or fit things inside it.
The if then block checks for a condition, and activates when its met. When the condition is true, it activates the events put inside of it.
Forever Block: Shaped like a C to fit things ontop inside and below it.
Programmers use it to repeat a sequence forever because it allows for automatic events at any time, like automatically turning when you touch the color red
Concepts
Sequence:
Vocabulary
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
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:
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.1
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.
-
See “Objects and Classes” in your textbook. ↩