Digital writing and portfolio lessons for creators who want their decisions to be understood
Name the audience, problem, starting condition, role, date, and constraints. Readers should understand why the project exists before seeing the solution.
Read the lessonDescribe meaningful alternatives and why one fit the situation. A tool list is less useful than the reasoning behind each choice.
Read the lessonConnect claims to tests, measurements, feedback, source notes, or before-and-after comparisons. Explain how evidence was collected.
Read the lessonIdentify your contribution and credit research, design, code, art, testing, feedback, and outside resources.
Read the lessonExplain what changed, what failed, what remains limited, and what you would do next. Accurate boundaries improve credibility.
Read the lessonBegin with a one-sentence summary containing the project, audience, and result. Describe the situation before your work and the constraints that shaped real choices. Select decisions that reveal how you think instead of publishing a chronological dump.
Words such as intuitive, fast, innovative, and user-friendly need support. Describe the task completed, comparison performed, error observed, or feedback that caused a revision. Without measurements, use precise modest language rather than inventing numbers.
Define specialized terms on first use and give each paragraph one main job. Descriptive headings help readers scan. Link text should describe its destination, and screenshots need captions explaining what evidence the reader should notice.
Label work accurately as a concept, personal experiment, class assignment, prototype, client project, or production release. Do not imply employers, users, partnerships, awards, or outcomes that did not occur. For team work, state what you owned and where you collaborated.
Write: summary; audience and problem; constraints; your role; two important decisions; evidence; result; limitations; next step; and credits. Then underline every important claim and identify the evidence supporting it.
A screenshot should support a nearby explanation rather than replace it. Add a caption telling the reader what to notice, provide meaningful alternative text, and remove private information. Use descriptive link text so the destination makes sense without relying on surrounding sentences.
Read the draft once for missing context, once for unsupported claims, and once for accessibility. Remove repeated background, define unexplained terms, verify names and dates, test every link, and ask whether the conclusion matches the evidence actually shown.
Note: It’s not required, but it does help a lot.