Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/y2k-webring/llms.txt

Use this file to discover all available pages before exploring further.

StatusWidget is a zero-prop component that renders the developer’s current status from the status field of the S export in portfolioData.js. It presents three named status lines — what is being built, read, and debugged right now — in a compact terminal-style panel labeled // NOW_PLAYING.exe. Each line is prefixed by a small Lucide icon and a colored keyword, giving the block a scannable, status-screen feel without any external data fetching. All values come from a static object in data/portfolioData.js.

​
Data Source

StatusWidget imports the named export S (aliased as the devInfo object) from portfolioData.js and reads devInfo.status directly. The status object has three fixed string fields: 
// data/portfolioData.js
status: {
  building: "A haunted React component",
  reading:  "Documentation from 2014",
  debugging: "Reality (and CSS grids)"
}
Each field maps to one list item in the rendered widget:
FieldIconLabel color
buildingTerminal (Lucide)text-y2k-lime
readingBookOpen (Lucide)text-y2k-cyan
debuggingBug (Lucide)text-y2k-magenta

​
Usage

StatusWidget is rendered on the About page, typically nested inside a BorderedPanel to give it the standard Y2K frame: 
import { StatusWidget } from '../components/y2k/StatusWidget';
import { BorderedPanel } from '../components/y2k/BorderedPanel';

export function AboutPage() {
  return (
    <BorderedPanel title="Status" color="magenta">
      <StatusWidget />
    </BorderedPanel>
  );
}
Because the component has no props, it renders identically every time — there is nothing to configure at the call site. Drop it in and it just works.

​
Customization

StatusWidget does not accept props for overriding its content. To change what is displayed, update the status object directly in data/portfolioData.js: 
// data/portfolioData.js
status: {
  building:  "Your new project name here",
  reading:   "The book or docs you are working through",
  debugging: "The current thorny problem you are solving"
}
Because portfolioData.js is a static module, changes take effect on the next build (or hot-module reload in development). No database, no API call, no environment variable required.
Keep the status entries updated regularly. A portfolio that shows genuine, current activity signals that the developer is engaged and actively shipping. Stale entries — especially ones that reference specific dates or old projects — are immediately noticeable to recruiters and collaborators who visit more than once. Treat the status block like a sticky note on your monitor: refresh it whenever you start something new.

Build docs developers (and LLMs) love

Get started for freeTalk to us