Every tag accounted for
Go through your own file and be able to say what every single tag is doing. Where you cannot, you have found the next thing to learn.
Open your generated file. Start at the top. For every tag, say out loud what it does.
Where you can, move on. Where you cannot, write the tag in a file called unknowns.md and keep going. Do not stop to look anything up on the first pass.
You will end up with a list, maybe ten tags, maybe twenty. That list is useful because it is specific to what you do not know yet. It gives you a small, personal syllabus for the next pass.
Now take the list to MDN, not to a model. Search "mdn" plus the tag. Read the first two paragraphs, no more. Write one sentence in your own words next to each.
Learn by collecting your unknowns
A simple learning loop
Scan first. Learn second.
Do one fast pass through the file. Save the unknowns for later.
generated file
read from top to bottom
Say each tag out loud. If you know it, keep moving.
unknowns.md
write only the unknown tags
Keep the list short, specific and personal.
MDN lookup
read a little, then explain it simply
read
First two paragraphs only.
your sentence
Section groups a related part of the page.
One sentence is enough. Write it in your own words.
First pass
Read the tags out loud.
If you know it, move on.
No searching yet.
Simple rule: first pass to collect what you do not know. Second pass to learn only those things.
This keeps the first pass fast and turns confusion into a small study plan.
The reason it is documentation and not a chat window: you are building the reflex of checking a primary source, and you will need it in about three chapters when a model tells you something confidently wrong.
Finish with a second pass through the file. It should read as a document rather than as output.
Build this in your own editor
This one runs on your machine rather than in the browser workbench. Work to the outcomes below, then come back and mark it complete.
You should now be able to
- Account for every tag in a file you did not write
- Use documentation rather than a model to close a gap
- Produce an honest list of what you do not yet know
Loading…