Digital Portfolio

01 — Adobe Production

1. Adobe InDesign
2. Adobe Photoshop
3. Adobe Illustrator

02 — 3D & Digital Drawing

4. CLO 3D
5. Browzwear (at some schools)
6. Procreate

03 — Portfolio Assembly

7. Canva (sometimes)
8. PDF portfolio creation

04 — Publication & Delivery

9. Website portfolio
10. Digital presentation

Adobe InDesign

Use InDesign as the portfolio’s page-layout and document-control centre. Define page size, orientation, margins, columns, baseline grid and bleed before designing spreads. Build parent pages for recurring elements and use paragraph, character and object styles for headings, captions, credits, folios and image frames. A controlled style system makes global revision possible and prevents small inconsistencies from accumulating across a long document.

Place linked Photoshop and Illustrator files instead of repeatedly copying pixels into the document. Name links clearly, keep them inside a stable project structure and resolve missing or modified links before every export. Establish a narrative rhythm: strong opening, concise project context, research and development, technical evidence, outcomes and reflection. UAL recommends organising a portfolio by project, showing the journey from research and process to outcome, using concise annotations and avoiding overcrowded pages.^[1]

Add bookmarks and meaningful hyperlinks for section navigation, website, email and project references, then test them in the exported file. Adobe’s current InDesign documentation distinguishes print PDF from interactive PDF and notes that interactive export can preserve hyperlinks, bookmarks, buttons, media and page transitions.^[2] Use interactivity only when it improves orientation; the portfolio must remain understandable when video, hover or animation is unavailable.

Portfolio checkpoint: Build a 12-page project template with parent pages, a type hierarchy, three object styles, live links, bookmarks and a preflight check. Change one style and confirm that every related page updates correctly.

Adobe Photoshop

Use Photoshop for tonal correction, colour control, masking, retouching, compositing and raster-image preparation. Begin with the highest-quality available original and preserve it. Work non-destructively with adjustment layers, Smart Objects, Smart Filters and layer masks so edits remain reversible; Adobe notes that these methods protect original image data and avoid repeated quality loss.^[3] Name layers by function, group related edits and keep one clean master rather than a chain of unexplained final files.

Correct exposure, white balance, lens distortion, dust and background distractions without changing garment construction, body proportions, fabric texture or colour in misleading ways. Compare hero images, process photographs and technical details at their intended size. Use consistent crops and neutral reference views when the work must be evaluated accurately. Record photographer, permissions, colour treatment and retouching decisions in file metadata or the project log.

Separate output preparation from the editable master. Resize once for the destination, apply appropriate sharpening after resize and export web derivatives in an efficient format while retaining a high-resolution archival file. For online viewing, Adobe recommends an sRGB workflow because work will appear on many uncalibrated displays, while acknowledging that exact appearance cannot be controlled across every screen.^[4] Check image quality on phone, laptop and a larger display before release.

Portfolio checkpoint: Prepare one editorial image, one neutral garment view and one construction detail from raw or high-resolution originals. Submit layered masters, web derivatives and a short retouching and colour-management log.

Adobe Illustrator

Use Illustrator for technical flats, vector diagrams, logos, symbols, repeat artwork and scalable line-ups. Establish a garment drawing convention for visible edges, seams, topstitching, folds and hidden construction; create reusable brushes and symbols without allowing automation to introduce false details. Align front and back views, use consistent proportions and label style, view and revision. Keep construction callouts concise and verify every line against the pattern or sample.

Structure the file for revision. Separate guides, garment, stitching, colour, artwork and annotation layers; name artboards by project and deliverable; define global swatches and graphic styles; and preserve an editable master. Use clipping masks rather than destructive cropping and expand effects only when a downstream workflow requires it. Illustrator’s native formats preserve editing data, while exported formats may discard information; Adobe therefore recommends retaining the AI source until work is complete and exporting purpose-specific copies.^[5]

Choose output by use: PDF for controlled pages or review, SVG for scalable web graphics when appropriate, and PNG, JPEG or WebP for raster delivery. Test stroke weight, small text, transparency, linked images, fonts and colour after export. Avoid outlining all text in the portfolio itself, because live text remains more searchable and accessible; reserve outlined type for artwork whose shape must not change and keep a live-text source.

Portfolio checkpoint: Produce a front-and-back technical flat, a collection line-up and a vector identity asset. Export each for print and screen, then document what remains editable and what changes in every format.

CLO 3D

Build CLO evidence from a credible garment file rather than from a decorative render alone. Record the avatar or measurement set, pattern source, scale, seam relationships, fabric assignment, trims and version. Check grain, particle distance, collision thickness, seam direction and arrangement before evaluating the drape. CLO’s simulation system applies gravity and collision to sewn pattern pieces and offers modes for faster work, more accurate fabric fitting and more stable animation.^[6]

Show why 3D changed the design. Include 2D pattern and 3D garment views together, then document fit maps, strain or pressure indicators, silhouette comparisons, colourways and major corrections. Treat simulation as evidence to test against physical fabric and fittings, not proof that a garment is production-ready. State which fabric properties were measured, supplied or estimated and identify any avatar, trim, lighting or physics limitations that could alter interpretation.

Create repeatable presentation views: front, three-quarter, side, back and selected details using consistent camera, pose, light and background. Save the project and render settings, then export stills, turntables or animation at the resolution required by the portfolio. CLO advises completing a high-resolution simulation before final rendering and beginning with a plain background, controlled lighting and a lossless PNG when image quality is the priority.^[7]

Portfolio checkpoint: Present one garment from 2D pattern through two simulation corrections to final views. Include input assumptions, fit evidence, matched camera angles and a comparison with a physical toile or sample.

Browzwear (at some schools)

Where Browzwear is available, use VStitcher to demonstrate an apparel-development workflow built around a digital garment and its 2D pattern. Import or create correctly scaled pieces, verify seams and construction, assign measured or approved material data and fit the garment on an appropriate avatar. Browzwear describes VStitcher as a system for physics-based simulation using real fabric data, with 3D views, pressure or tension maps and multiple avatar perspectives.^[8]

Organise evidence around decisions: block selection, pattern alteration, fabric response, fit review, colourway, artwork placement and approval. Capture equivalent front, side and back views for every version and record comments beside the exact garment state they address. If Stylezone or another review space is used, identify reviewer, date, issue, decision and resulting revision. Portfolio pages should show collaboration and version control, not just interface screenshots.

Do not describe a render as a physical sample. Label it “3D simulation” or “digital prototype,” state the software version and disclose measured versus assumed inputs. Export a concise set of beauty images, turntables, fit-map evidence and pattern details, then compare them with the real sample wherever possible. A strong case study demonstrates what digital prototyping clarified and what still required physical validation.

Portfolio checkpoint: Build a three-stage VStitcher review for one style. Show pattern and fabric inputs, fit-map findings, stakeholder comments, the revised digital prototype and an honest physical-sample comparison.

Procreate

Use Procreate for fast visual research, silhouette exploration, expressive fashion illustration, textile ideas and annotated concept development. Choose canvas dimensions, resolution and colour profile before beginning, based on whether the work will be printed or viewed on screen. The Procreate Handbook provides sRGB and Display P3 options for screen work and CMYK profiles for print-oriented canvases, and warns that RGB and CMYK colour spaces cannot simply be switched inside an existing canvas.^[9]

Build an editable layer system: reference, sketch, line, base colour, material, shadow, highlight, annotation and background. Name important groups, duplicate a version before flattening and use alpha lock, clipping masks and layer masks for controlled experiments. Preserve evidence of selection and iteration by exporting a process sequence or time-lapse when it contributes to assessment; do not let the time-lapse replace readable still stages or captions.

Export by purpose. Retain the native Procreate file with layers, use PSD when editable transfer is required, PNG for transparency or lossless graphics, JPEG for efficient continuous-tone images and PDF only after checking page order and quality. Test line weight and text after reduction, because an illustration that reads at canvas size may collapse inside a portfolio spread. Keep external brushes, photographs and textures licensed and credited.

Portfolio checkpoint: Develop one illustration from thumbnail to final rendering in at least five documented stages. Deliver the layered source, an appropriately profiled final image and print- and screen-ready exports.

Canva (sometimes)

Canva can be appropriate for rapid prototypes, simple portfolios, collaborative reviews or learners without access to specialist page-layout software. Begin by defining the same system required in any professional tool: page ratio, margins, grid, type hierarchy, colour palette, caption style and image treatment. Replace template filler with purposeful structure and remove effects that compete with the work. The platform should accelerate production, not make unrelated portfolios look identical.

Control assets and permissions. Upload correctly sized images, organise projects and page names, keep a master copy before major revisions and verify that collaborators cannot accidentally overwrite approved work. Check the licence and attribution requirements for every template, stock asset, font, photograph and uploaded element, especially when a portfolio will support commercial employment or promotion. Export a proof and inspect it outside Canva, because fonts, links, transparency, crop and video behaviour may differ after download or sharing.

Use available accessibility tools as a starting point. Canva states that its Design Accessibility checker can flag colour contrast, typography and alternative-text issues, and that captions and PDF accessibility features are available.^[10] Automated checks do not decide whether the narrative, reading order or alternative text is meaningful; review those manually and test the final exported format.

Portfolio checkpoint: Rebuild four portfolio pages from a selected template, removing decorative dependence. Test the exported PDF for links, text extraction, reading order, image quality, contrast and correct asset credits.

PDF portfolio creation

Design the PDF for a known use: email application, upload portal, interview screen share, tablet review or print. Check the recipient’s page, dimension and file-size rules before layout. Use a logical order with cover, concise navigation, project sections and contact information; keep selectable live text, consistent page numbers and meaningful link labels. Start and end with strong work, and ensure that every project identifies context, date, role, collaborators and outcome.

Export from the source application with appropriate image resolution, compression, bleed and colour profile. Embed or correctly subset fonts, avoid accidental printer marks in screen files and do not flatten the only accessible copy. Open the PDF on more than one viewer, test every page and link, zoom into technical details and check that image quality survives the target file-size limit. Maintain a version name that identifies owner, role or course, destination and revision date.

Accessibility must be built into the source and verified after export. Adobe explains that document tags define headings, paragraphs, sections and reading order for assistive technology and also support reflow on small screens.^[11] Set document language and title, tag headings and lists, add concise alternative text, mark decoration as artifacts, preserve contrast and inspect reading order. Run an accessibility check, then perform a manual keyboard, text-extraction and read-aloud review.

Portfolio checkpoint: Deliver a lightweight application PDF and a high-quality interview PDF from one source file. Both must pass page-order, link, font, colour, metadata, text-extraction, tag and reading-order checks.

Website portfolio

Define the primary audience and action before choosing a platform. A focused site usually needs a clear home page, selected work, project case studies, concise profile or about page and reliable contact route. Give each project its own readable narrative from context and question through research, development, technical evidence and outcome. Keep navigation labels familiar, URLs stable and contact information available without forcing social-platform membership.

Build with semantic headings, meaningful link text, keyboard access, visible focus, sufficient contrast and useful alternative text. W3C explains that well-structured regions and logically nested headings improve orientation for screen-reader, keyboard, cognitive and mobile users.^[12] Test zoom, text resizing and reflow; never hide essential explanation inside hover-only interactions. Publish a privacy notice or consent information when collecting messages or analytics, and do not expose confidential client work without permission.

Optimise media without erasing detail. Use descriptive filenames, responsive image sizes, modern formats where supported, explicit width and height and lazy loading for non-critical images. Web.dev notes that width and height provide aspect-ratio hints that reserve layout space and reduce visual movement while images load.^[13] Test the site on phone, tablet and desktop, with keyboard, touch, slow connection and images disabled; verify titles, social previews, forms, links, analytics and a custom domain before launch.

Portfolio checkpoint: Publish a three-project prototype with semantic page structure, responsive media, accessible navigation and a contact route. Complete a manual test matrix across devices, input methods and connection speeds.

Digital presentation

Design the live presentation for the audience, time limit and decision required. Build a simple arc: identity and proposition, selected challenge, research insight, development, technical resolution, outcome, reflection and invitation for questions. One slide should carry one main idea, supported by an image or a short evidence statement. Prepare spoken transitions and explain what only you can add; do not read dense portfolio pages aloud.

Make the delivery adaptable. Use large readable type, strong contrast, restrained motion and captions for essential audio or video. Send accessible materials in advance when appropriate and provide a separate handout for detail that cannot fit on slides. W3C’s presentation checklist recommends sufficient contrast, legible fonts, accessible handouts, captions and deliberate use of motion rather than decorative animation.^[14]

Rehearse with the real device, display, connection and time limit. Keep slides, embedded media, fonts and a PDF fallback available locally; carry the portfolio link and essential video as separate files. Test screen sharing, presenter view, audio, aspect ratio and remote-room legibility. Prepare a shorter version if time is reduced and a deeper sequence for questions. Afterward, record questions and update unclear portfolio evidence rather than treating delivery as separate from design development.

Portfolio checkpoint: Deliver an eight-minute portfolio presentation with a five-minute backup version. Submit the slide file, accessible PDF, speaker plan, captions, technical contingency list and a reflection based on audience questions.