Build a Technical Project Journal

A portfolio shows results.

A technical journal can show reasoning.

Do not turn it into a diary of every keystroke.

Journal entry anatomy

A useful entry should answer some of:

• What were you trying to do?
• What changed?
• What evidence surprised you?
• What failed?
• What did you decide?
• What would you do differently?

Required structure

Create at least three posts tied to actual course work:

1. first build / dependency setup;
2. template refactor;
3. one debugging event.

Generate the index

Your journal page should come from site.posts, not a manually copied list of links.

Add metadata carefully

Use categories/tags only where they help explain or filter the work.

Public-boundary check

Before publishing journal entries, remove:

• credentials;
• private repository URLs if they reveal protected material;
• student records;
• internal/private contact information;
• screenshots containing sensitive tabs or account data.

Evidence checkpoint

Show:

• three post source files;
• generated journal index;
• one automatically generated URL;
• one date/filter transformation;
• one privacy edit you made before publishing.