This is my portfolio showcasing my projects and skills.
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.
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”).
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.
Class = a blueprint for objects
Remember: always test your code
Use System.out.println() to print
When to use: Anytime you write multiple lines of code.
Inline code for short snippets.
Fenced code blocks with language for full examples.
public class Hello {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}
When to use: Organize steps, notes, or key points.
Numbered lists for sequences or steps.
Bulleted lists for unordered ideas.
Define the class Write the main method Test your program Variables
Loops
Conditionals
When to use: Track progress on assignments or tasks.
[x] Complete coding warm-up
Finish project draft
Reflect on learning
When to use: Call out notes, reminders, or teacher comments.
💡 Remember: Loops repeat code until a condition is false.
When to use: Compare values, track progress, or organize data neatly.
| Task | Status | Notes |
|————–|————|—————–|
| Homework 1 | Done # | Submitted |
| Homework 2 | Pending | Needs review |
When to use: Add references, resources, or visuals.
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>
When to use: Hide solutions, extended notes, or extra details.
When to use: Add references or side notes without cluttering the page.
This concept is related to object-oriented programming.1
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.
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. ↩