← Back to blog
Guides

Before your first demo, write a clear brief

Turn a rough idea into an actionable task with a defined audience, a small scope, and practical acceptance criteria.

Clidex Team

When preparing a small project with Clidex, start by describing the result you need. A concrete brief makes it easier to judge whether the implementation meets your expectations.

This guide uses a personal portfolio page as a planning example. It does not describe a completed demo or measured performance results.

Define who will use it

“Build me a beautiful website” leaves many decisions open. Start with three details: who will visit, what they need to learn, and what action they should take.

For example: build a portfolio for an independent developer so prospective collaborators can explore three projects and contact the author by email.

Keep the first version small

Start with one page containing an introduction, project cards, and a contact link. Each card needs a name, description, screenshot, and destination URL.

Local content can support the first version. Consider a content management system when editing needs justify it. Include the existing technology stack, visual preferences, and asset locations in the brief to reduce guesswork during implementation.

Make the acceptance criteria checkable

  • The page is readable on phones and desktops without horizontal overflow.
  • Project links reach the right destinations and the contact link opens an email client.
  • Every link is reachable by keyboard with a visible focus indicator.
  • Images have alternative text and text has sufficient contrast against its background.
  • The page title and description accurately describe the author and their work.

A reusable project brief

Implement a personal portfolio page in the current project.

Audience: prospective collaborators who want to explore my work.
Content: a short introduction, three projects, and an email link.
Constraints: follow the existing stack and styling conventions.
Assets: use the project details I provide; label missing content clearly.
Visual direction: simple and readable, with the work taking priority.
Acceptance criteria: works on phones and desktops; links work;
keyboard access is supported; no horizontal overflow.
When finished, explain the changes and what you verified.

Inspect the project structure before implementing.

Replace the project count, contact details, and visual direction with your requirements, then supply the actual project information.

Turn the iteration into a case study

After finishing the first version, save the initial brief, screenshots, key adjustments, and remaining limitations. Add the models used, time spent, and costs when you have actual records.

These materials can become a case study that lets readers experience the result and understand how you got there.

When you are ready, explore the Clidex installation guide.

Keep exploring