A prototype does not need to imitate every detail of the finished work. Its value comes from making an uncertainty concrete enough to explore before the full project is built.

Choose the question first. A rough arrangement may test whether the content has a clear order, while a clickable version may test whether an interaction is understandable. State which parts are placeholders so the feedback stays focused.

Keep the result of the experiment alongside the prototype. Record what it showed and what remains unknown. A successful prototype may lead to a revision or a narrower idea, rather than approval of every detail it happened to contain.

An example to consider.

A rough form can test whether a question makes sense before its polished visual treatment is ready. The prototype targets the uncertain relationship.

Put it in perspective.

Think about the life of the work after delivery. Source files, context, and credits can preserve the intent when the piece moves to a different setting.
A few starting points
  1. Name the question the prototype should answer.
  2. Make placeholders clear.
  3. Record what remains unknown after trying it.

Follow a related question

Choose a nonurgent source.

Choose the moment to check

Export a small representative sample.

Choose a tool with an exit

Keep learning

Related background to continue exploring this subject.

Git: version control fundamentals W3C: accessibility, usability, and inclusion
Make room for ideas