Why I Built It

I don’t use LinkedIn or other social media platforms.

Not because I dislike technology, but because those platforms encourage behavior that doesn’t align with how I work:

• constant posting instead of thoughtful writing
  
• visibility chasing instead of substance
  
• algorithms instead of clarity
  
• performance instead of professionalism
  

I wanted a place that could do three things well:

1. Present a clear, accurate version of my professional background
   
2. Allow deeper context where it actually helps (case studies, explanations)
   
3. Remain usable and readable years from now
   

This site is the result.

What This Site Is (and Is Not)

This site is:

• a professional reference point
  
• a place for verified work history and case studies
  
• a way to add context that doesn’t fit on a résumé
  
• intentionally quiet and non-performative
  

This site is not:

• a blog driven by posting frequency
  
• a social media replacement feed
  
• a comment platform
  
• a place optimized for engagement metrics
  

If someone wants a quick overview, the résumé is enough.

If someone wants deeper understanding, it’s available — but optional.

How the Site Works

The site uses a two-layer model: writing and presentation are intentionally separated.

1. Writing layer (Listed / Standard Notes)

All content is written in plain Markdown using Standard Notes and published through Listed.

This provides:

• distraction-free writing
  
• version history
  
• portability
  
• no dependence on a custom editor or CMS
  

Each major section of the site corresponds to a single published note.

2. Manifest-driven structure

One published note acts as a JSON manifest that defines the site:

• which pages exist
  
• their titles
  
• their source URLs
  

When I want to add a page, I don’t touch the website itself.

I update the manifest and publish it.

The site updates automatically.

3. Sync and normalization

A small server-side script runs periodically and:

• fetches content from Listed
  
• removes platform-specific branding and boilerplate
  
• normalizes headings and structure
  
• stores clean HTML fragments locally
  

Only the content remains — not the publishing platform.

This ensures the site reads as my own, not as a republished blog.

4. Assembly at request time

Apache Server Side Includes (SSI) assemble each page at request time:

• navigation is included from a shared fragment
  
• page content is included from cached HTML
  
• the browser receives a fully static page
  

There is:

• no database
  
• no JavaScript framework
  
• no tracking
  
• no user accounts
  

The result is fast, readable, and resilient.

Why This Approach Matters

This design prioritizes:

• ownership — all content lives under my domain
  
• durability — no dependency on trends or platforms
  
• clarity — separation of writing from presentation
  
• honesty — no algorithmic amplification or optimization
  

The site can function unchanged for many years.

If Listed ever disappears, the cached content remains.

If the server is rebuilt, the manifest can regenerate the site.

Nothing is locked in.

Why Case Studies Exist Here

A résumé explains what someone did.

It rarely explains:

• how decisions were made
  
• what constraints existed
  
• what went wrong
  
• what mattered under pressure
  

Case studies exist to provide that context.

They are not required reading — only available for those who want a clearer understanding of how I work in real environments.

A Quiet Alternative

This site isn’t meant to compete with social platforms.

It’s meant to replace what they were originally supposed to be:

a stable professional presence

controlled by the person who owns it

No feeds.

No noise.

No performance.

Just work, documented clearly.

In Short

• I write in plain text
  
• the site structure is data-driven
  
• content is owned and portable
  
• presentation is simple and durable
  
• attention is optional
  

That is intentional.

This site exists so that when someone asks

“Can I see your work?”

the answer is simply:

Yes.