The Work page presents the portfolio owner’s professional history in a chronological, story-driven format. Labeled “The Journey” in the navigation bar (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/color-melt/llms.txt
Use this file to discover all available pages before exploring further.
bg-dye-blue), it uses the SpiralTimeline component to render work experience as a flowing timeline that matches the Color Melt aesthetic while keeping the career narrative easy to follow.
Purpose
The Work page gives visitors — especially recruiters and hiring managers — a structured overview of the portfolio owner’s professional experience. Where the Projects page shows what was built, the Work page explains where it was built, in what role, and over what period of time. The SpiralTimeline presentation makes the career history feel like a journey rather than a spreadsheet, which fits the Color Melt theme well. The format naturally draws the eye from one role to the next, encouraging visitors to read the full history rather than skimming a bullet list. This page is particularly important for portfolio owners with meaningful work history, career transitions, or a combination of full-time employment, freelance work, and personal projects. Each entry should give enough context for a visitor to understand the scope of the role and what the creator contributed.Components Used
| Component | Role on This Page |
|---|---|
TieDyeSpiral | Preloaded theme component available to the page’s React app bundle |
LavaBlob | Preloaded theme component available to the page’s React app bundle |
StickerSheet | Preloaded theme component available to the page’s React app bundle |
ShirtRack | Preloaded theme component available to the page’s React app bundle |
RainbowArch | Preloaded theme component available to the page’s React app bundle |
SpiralTimeline | Renders each work history entry as a node on a flowing spiral timeline, with dates, titles, employer names, and description text for each role |
MagazineSpread | Preloaded theme component available to the page’s React app bundle |
PatchworkQuilt | Preloaded theme component available to the page’s React app bundle |
SmileyFlower | Preloaded theme component available to the page’s React app bundle |
LiquidForm | Preloaded theme component available to the page’s React app bundle |
Navigation | Renders the shared top navigation bar; the “The Journey” pill is highlighted as the active route |
CursorDrops | Maintains the theme-specific cursor trail effect, consistent with all other pages |
PageTransition | Wraps the page content in the animated entrance transition triggered when navigating to /work |
Content to Customize
Replace employer names
Update each timeline entry with the real name of the organization, company, studio, or client. For freelance work, use a label such as “Freelance” or the client industry if the employer name is confidential.
Update job titles
Replace the placeholder job titles with the creator’s actual titles from each role. Use the official title from the position, and add a brief clarifying label if the title alone does not convey what the role involved.
Set accurate date ranges
Replace the placeholder start and end dates with the real employment or engagement dates. Use a consistent format across all entries — for example, “Jan 2022 – Mar 2024” or “2022–2024”. For a current role, use “Present” as the end date.
Write role descriptions
Replace the placeholder responsibility text with specific descriptions of what the creator did in each role. Focus on what was built, what was improved, what decisions were made, and what impact the work had. Two to four bullet points or sentences per role is usually enough.
Highlight key accomplishments
Within each role description, include at least one specific accomplishment — a shipped feature, a measurable improvement, a project delivered under a constraint, or a skill developed on the job. Accomplishments are more memorable than lists of generic duties.
Order entries from most recent to oldest
Place the current or most recent role at the top of the timeline and move backward through history. This is the standard reading order for professional experience and matches what visitors expect.
File Location
The Work page template ispages/Work.html inside the pages/ folder.
window.__STATIC_PAGE_ROUTE__ script tag that sets the active route when this page is opened directly:
pages/Work.html directly — for example, via a shared link or a direct URL. Do not remove or modify this script tag.
If the portfolio includes a downloadable résumé, the Work page is a natural place to add a download link. Store the résumé file in the repository (for example,
resume.pdf at the root) and link to it using a relative path so it works correctly on the live GitHub Pages site.