How Should a Creative Coder in Spain Show Generative Art, Installations, and Web Demos?

A creative coder should present each coherent artwork or installation as one project, explain the interaction and their role, and link the most durable proof available: live sketch, documentation, repository, or video.

Interactive work changes meaning across formats. A browser demo can be opened, an installation may only survive as documentation, and commissioned code may remain private. The portfolio must describe what existed without pretending every piece is still live.

Which creative-coding projects belong on the page?

Include finished sketches, exhibited installations, approved commissions, reusable tools, and selected experiments that demonstrate your current practice.

Group variations that belong to one series rather than making every output a project. State whether you created the concept, visuals, code, electronics, sound, fabrication, or only part of a collaboration.

Place a completed but offline installation under Built, active work under Building or Working on, and abandoned experiments under Archived. Shipped is appropriate when the work remains publicly released.

Live sketch: stable browser destination.
Installation: documented page or video.
Public tool: repository with instructions.
Private commission: approved case summary only.

What is the fast way to organise creative work with IndieShow?

The fast way is to add one IndieShow card per piece or series, assign its current status, and give it the most useful durable destination.

Use the tag for the medium or technology and the description for the interaction, context, and your role. Add a metric only when a factual exhibition or usage figure is permitted and useful.

Lead with work that can be understood quickly. The page preview helps you check whether still images, names, and descriptions explain the work before someone opens a resource-heavy demo.

Build your IndieShow pageClaim your handle, organise the projects in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

Should you link the live demo, source code, or installation video?

Choose the destination that proves the main claim with the least setup and remains meaningful outside the original venue.

A live demo is strongest for browser interaction, a repository for reusable technical work, and a video for a physical experience that cannot be recreated online. Do not call a video a live demo.

Avoid duplicate cards for code, video, and exhibition coverage of one piece. Use one maintained project page as the destination when you need to gather several artifacts.

How do you handle broken browsers, missing sensors, or expired hosting?

Archive the original state honestly and replace a broken destination with stable documentation rather than leaving a failed experience as the first proof.

Record the environment or hardware required when that context matters. Never expose an installation control panel or credentials just to preserve interactivity.

The related IndieShow guides cover visualisation demos and prototypes whose technical state differs from their creative value.

Why does IndieShow suit a creative-coding portfolio?

IndieShow gives live, filmed, physical, and archived work a single readable structure while specialist hosts continue to carry each artifact.

Reorder pieces as your practice changes, move fragile experiments to Archived, and update destinations without changing the personal page URL.

IndieShow closes the portfolio by explaining what every external demo is before the click, which is especially useful when the work cannot all survive in the same format.