Weekly Process Blog

First official blog — Friday, October 16, 2026

Your first official Process Blog is due Friday, October 16, 2026. It is worth 50 points and replaces this week's usual 50-point weekly check-in. It is one grade, not an additional 50-point assignment.

Use the established requirements below. The rubric describes the evidence Mr. Oxford checks; individual category weights have not been specified.

What this is

Every Friday, add a new dated section to the `Process Blog` page on your Google Site. Put the newest week at the top; keep all weeks on the same page. Answer the six guiding questions below in order. Two images are required, not optional.

This is not the same thing as your Daily Check-In. The check-in is private, it is for you and Mr. Oxford, and it runs day to day. This is public. A parent, a community member, or somebody reading your portfolio in two years should be able to open one post and follow what you are building without knowing anything about this class. That means no shorthand and no jargon you have not explained.

The six parts

1. Last week's goal, checked. Copy your answer to part 6 from last week's post, word for word, then answer it: did you hit it fully, partly, or not at all? If not fully, what got in the way?

First post of the year has nothing to check. Write "N/A - first entry."

2. Where you started this week. The image is last week's ending image. Do not take a new screenshot. Paste the same one, then write one sentence naming what state the project was in.

For your first entry, use the starting image you saved when beginning the project. If you already have posts, continue from your previous ending image and goal, and keep those earlier entries.

Reusing last week's ending image is the whole point. It proves the weeks connect, and it makes it impossible to shoot a fake before-and-after five minutes apart.

3. Where you ended this week. A new image showing the actual state of the project at the end of the week, plus one sentence naming what changed between image 2 and image 3.

This image becomes next week's part 2.

4. What got in the way, or what you changed. The obstacle, the mistake, or the decision to go a different direction. Name the specific thing. "The audio was clipping on every take because the gain was too high" is an answer. "Had some issues" is not.

If a week genuinely went smoothly, say what the hardest decision was instead.

5. What you learned. Use this sentence: "Next time I'll ___ because ___."

That is required phrasing, not a suggestion. It is a separate part from 4 on purpose. The problem is not the learning. What you will do differently is the learning.

6. What you hope to accomplish next week. One specific, finishable thing. This becomes part 1 of next week's post, and you will be checked against it, so do not write something vague to protect yourself.

Sources and AI use - standing requirement

Not a reflection question. A policy field, at the bottom of every post.

Any week you referenced someone else's work - a photo, a font, a song, a tutorial, a technique you copied - credit it. Any week you used an AI tool in an approved way, say which tool and what you used it for.

If neither applies that week, write "No outside sources or AI use this week." The line is never left blank.

This is required by the course. The Advanced scope and sequence lists source credits and approved AI-use disclosure as evidence for public-facing work. Doing it weekly here is what keeps it from becoming a scramble at the end of a project cycle.

Where it goes and how you turn it in

Two places, and they are not the same place.

• Write each Friday's update on your Google Site, in a new dated section

of the `Process Blog` page. Keep the newest section at the top. Do not make a new page each week; the whole arc of your project should be readable by scrolling down.

• Turn it in on Canvas. Paste the link to your Process Blog page into that

week's assignment. That is what gets graded.

Your Site has to be published and actually public. Test it: send the link to somebody sitting next to you and have them open it without signing in. If they cannot see it, a parent cannot see it either, and the post does not count.

Copy this template every week

Week of [date]

1. LAST WEEK'S GOAL, CHECKED
Last week I said: "[paste your part 6 from last week, word for word]"
Did I hit it? [fully / partly / not at all]
If not fully, what got in the way:

2. WHERE I STARTED
[paste LAST week's part 3 image here - do not take a new one]
At the start of the week, the project was:

3. WHERE I ENDED
[new image of the project right now]
What changed between those two images:

4. WHAT GOT IN THE WAY, OR WHAT I CHANGED

5. WHAT I LEARNED
Next time I'll ______ because ______.

6. WHAT I HOPE TO ACCOMPLISH NEXT WEEK

SOURCES AND AI USE
[credit anything you referenced and any AI tool you used, or write
"No outside sources or AI use this week."]

Keep the numbered headings. Same six parts, same order, every week - that is what lets somebody read four of your posts in a row and follow the project.

Images - how to capture them

• On a computer: press Shift + Command + 4, drag a box around what you want,

and the image saves to the desktop.

• On paper or physical work: phone photo, straight on, good light, no shadow

across the work.

• Paste the image directly into the post. Do not link to a file in your Drive.

A link that only you can open is the same as no image.

Public post rules

It is public. That changes two things.

• No classmates' faces and no full names in images or text without their

permission. First names only unless you have asked.

• No screenshots of anything with private information in it - logins, emails,

student IDs, gradebook screens.

What a bad post looks like

1. Last week I said I'd work on my project. I did some of it. 2. [screenshot] It was unfinished. 3. [screenshot] Now it's more finished. 4. Had some issues. 5. I learned a lot. 6. Keep working on my project.

Nobody outside this room can tell what the project even is. Nothing in part 5 is a learning. Part 6 cannot be checked next week, which means part 1 next week is worthless too.

What a usable post looks like

1. Last week's goal, checked. Last week I said: "Record all three interviews for the skate documentary." Partly. I got two of the three - the third person was absent Thursday and we couldn't reschedule before Friday.

2. Where I started. [same image as last week's part 3] One interview recorded, sitting on the SD card, nothing imported or organized yet.

3. Where I ended. [new image of the Premiere timeline] Two interviews are now imported, renamed by speaker, and the strongest 30 seconds of each is marked. The timeline went from empty to a rough order of clips.

4. What got in the way. The second interview clipped - the audio peaked and distorted on the loud parts, because I left the gain where it was from the first interview in a much quieter room.

5. What I learned. Next time I'll set the gain and record a ten-second test in the actual room before the interview starts, because the room changes the levels more than I expected.

6. Next week. Record the third interview and get it imported and marked like the other two.

Sources and AI use. Watched a Premiere marker tutorial by Justin Odisho on YouTube. Used Claude to help me write a list of interview questions - I wrote the final questions myself.

You can follow that without being in this class. That is the test.

How this is graded

October 16 blog check: 50 points total, replacing this week's 50-point weekly check-in. It is graded on evidence and specificity, not length or enthusiasm.

Descriptive rubric

These are the existing requirements used in the checking pass. The rows are checks, not equally weighted point categories. No individual point weights have been specified.

A short, honest, specific post beats a long vague one. A post with no images is incomplete regardless of how well it is written. A post that could have been written without doing any work scores zero.

The published page must be reachable and the images visible to its intended public audience. A post that the reader cannot open does not count.