Skip to main content

Documentation Index

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

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

Welcome, Mortals includes eleven HTML pages, each acting as a standalone entry file for a different section of the portfolio. The pages share a common visual identity managed by components/Layout.js and assets/main.css, which means you can update the written content of any page without touching the theme’s structure or styling. Work through the pages below and replace every piece of placeholder content with your own before publishing.
The unusual interface choices — decorative corner rays, the animated spider, eerie copy, the custom cursor — are part of the design. Fit your new content into the existing structure rather than removing the theme personality. Stripping the atmospheric elements produces a visually inconsistent result and defeats the purpose of the theme.

index.html — Homepage

index.html is the GitHub Pages entry point and the first page visitors see. Start here. Replace the portfolio owner’s name, professional headline, and homepage introduction. These three elements set the tone for the entire site. This page also carries any themed labels or decorative section titles that should reflect your own voice.
Write the homepage introduction in a register that matches the rest of the theme: a little theatrical, direct, and confident. The dark purple and orange palette supports bold statements better than cautious corporate copy.

about.html — Biography

about.html is the best place to tell the full story behind the portfolio. Replace the default biography with your own. Content that belongs here:
  • Personal and professional background
  • Career history or transition narrative
  • Education, certifications, and training
  • Creative influences and working philosophy
  • Goals and what you are currently focused on
  • Interests outside of work, if you want to include them
There is no required structure for the biography beyond what the page already provides. Fill in the sections that apply and leave out sections that do not. projects.html holds your featured projects, repositories, and work samples. Replace every default project entry with your own. For each project, include:
  • Project title
  • A short description of what it is and what problem it solves
  • The technologies, languages, or tools used
  • A link to the live project or repository
  • A screenshot or preview image, stored inside images/ and referenced by filename
Keep image filenames consistent with the paths already referenced in the page. If you add new images, update the src values to match.

work.html — Professional Experience

work.html is the professional work-history page. Replace the default entries with your own employment history, freelance engagements, or contract work. For each role, include:
  • Employer or client name
  • Your title or role
  • Dates of employment or engagement
  • A brief description of your responsibilities and contributions
List entries in reverse chronological order so the most recent experience appears first.

skills.html — Skills and Technologies

skills.html presents the languages, tools, technologies, and capabilities you bring to your work. Replace the default skill entries with your own. Organize skills in whatever grouping makes sense for your background — by category (languages, frameworks, tools), by proficiency level, or by domain area. The page structure is flexible enough to support most approaches.
Keep the skill labels brief. Single words or short phrases (React, TypeScript, Figma, Docker) read more cleanly in the grid layout than longer descriptions.

casestudies.html — Detailed Breakdowns

casestudies.html is for detailed project write-ups that go deeper than the project listing on projects.html. Replace the default case study content with your own. A case study entry typically covers:
  • The problem or brief
  • Your process and decisions
  • What you built and why
  • Results, outcomes, or lessons learned
  • Supporting images or diagrams
This page suits projects where the approach and reasoning matter as much as the final result.

articles.html — Article Index

articles.html holds a list or index of articles. Replace the default entries with your own published articles, posts, or notes. For each entry, include:
  • Article title
  • Publication name or platform (if applicable)
  • Publication date
  • A brief summary or excerpt
  • A link to the full article (external or internal)
If you have not published any articles yet, leave this page as a placeholder or use placeholders.html as a holding space until you have content ready.

writing.html — Writing Archive

writing.html is the long-form writing archive. This page is the right place for longer essays, technical papers, documentation samples, copywriting examples, creative writing, or any written work that does not fit neatly into the article index. Replace the default writing entries with your own. For each piece, include a title, a short description, and a link or download path.
For work published externally, link directly to the source URL.
<a href="https://example.com/your-article" target="_blank" rel="noopener">
  Article Title
</a>

testimonials.html — Testimonials

testimonials.html holds testimonials and feedback from colleagues, clients, or collaborators. Replace the default testimonial entries with real ones. For each testimonial, include:
  • The quoted text
  • The name of the person giving the testimonial
  • Their title or relationship to you (optional but helpful)
  • A link to their profile (optional)
Only include testimonials from people who have given permission for their words to be published publicly.

placeholders.html — Future Content

placeholders.html holds content sections that have not been filled in yet. It is a staging area rather than a finished page — a place to keep sections visible without publishing incomplete content to the other pages.
Update or remove placeholder sections as real content becomes ready. Do not leave the default placeholder text in any page that visitors will reach from the navigation. When a section is ready to publish, move it to the appropriate page and delete it from placeholders.html.
Use this page to:
  • Draft new sections before moving them to their permanent page
  • Hold content that needs review before publishing
  • Mark areas where you plan to add content in the future

contact.html — Contact Details

contact.html presents your contact information and external profile links. Replace the default email address, GitHub link, LinkedIn link, and résumé download link with your own before publishing. See the Personal Branding guide for detailed instructions on updating each contact field.

Page summary

index.html

Homepage entry point. Update name, headline, and introduction first.

about.html

Biography page. Share background, education, goals, and interests.

projects.html

Featured work. Add project titles, descriptions, screenshots, and links.

work.html

Professional experience. List roles in reverse chronological order.

skills.html

Skills and technologies. Group by category or proficiency.

casestudies.html

Detailed project breakdowns. Cover process, decisions, and outcomes.

articles.html

Article index. List published pieces with dates and links.

writing.html

Writing archive. Include longer essays, papers, and samples.

testimonials.html

Testimonials. Add real feedback from colleagues and clients.

contact.html

Contact details. Update email, GitHub, LinkedIn, and résumé links.

placeholders.html

Staging area. Hold future content here until it is ready to publish.

Build docs developers (and LLMs) love