All Portfolio Pages in the Welcome, Mortals Theme Site

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 ships with eleven separate HTML files, each acting as a self-contained entry point for a distinct section of the portfolio. Every page loads the same shared stylesheet and JavaScript components, so the spooky visual identity stays consistent across the entire site without any duplicated markup. This guide explains what each file is for, what content it is designed to hold, and what you should keep in mind when customizing it.

​

All Pages at a Glance

---

​

Homepage

​

index.html — Main Homepage

The homepage is the first page a visitor sees and the file GitHub Pages looks for automatically when the site URL is opened without a specific path. It introduces the portfolio owner, sets the theatrical tone of the theme, and provides entry points to the rest of the site through the shared navigation. What it holds:

• Portfolio owner name and professional headline
• Homepage introduction written in the theme’s eerie, playful voice
• Primary call-to-action links pointing visitors toward featured work, the about page, or the contact page
• SpookHost presentation element, which performs the horror-host introduction on load

Editing notes: Start your customization here. Replace the displayed name, headline, and introduction copy. Keep the theatrical language that matches the theme’s tone — draining the copy of personality will make the page feel visually mismatched with its own styling.

---

​

Profile Pages

​

about.html — Biography and Background

The About page is where the portfolio owner explains who they are beyond their job title. It is designed to feel personal and narrative rather than purely professional, fitting the storytelling character of the theme. What it holds:

• Full biography: background, interests, creative influences, and personal approach to work
• Career history summary or transition story
• Education, certifications, or other formative experiences
• Any personal context that helps a visitor understand the human behind the portfolio

Editing notes:

---

​

Work and Projects

These four pages together cover the professional and technical substance of the portfolio. Visitors looking for evidence of skill and experience will spend the most time across these pages.

​

projects.html — Featured Project Portfolio

The Projects page showcases the portfolio owner’s most important work. It is designed to display visual or descriptive entries for individual projects, with links to live demos, repositories, or detailed write-ups. What it holds:

• Featured project entries, each with a title and description
• Screenshots or preview images stored in the images/ folder
• Links to live deployments, GitHub repositories, or case study pages
• Short descriptions explaining the problem solved, the tools used, and the outcome

Editing notes:

---

​

work.html — Professional Experience

The Work page functions as a structured work-history record. It is the right place for employment history, freelance engagements, contract roles, or volunteer experience that belongs in a professional context. What it holds:

• Job titles, employer names, and employment date ranges
• Role descriptions and key responsibilities
• Notable achievements or contributions for each position
• Any contract, freelance, or consulting history

Editing notes: Present entries in reverse chronological order so the most recent experience appears first. Keep descriptions concise — the Case Studies page is available for deeper project breakdowns.

---

​

skills.html — Skills and Technologies

The Skills page lists the portfolio owner’s technical capabilities, tools, languages, and areas of expertise. It is designed to give visitors a fast overview of what the portfolio owner can do. What it holds:

• Programming languages, frameworks, and libraries
• Design or authoring tools
• Platform experience (cloud providers, operating systems, etc.)
• Soft skills, methodologies, or professional capabilities

Editing notes:

---

​

casestudies.html — Detailed Project Breakdowns

The Case Studies page provides space for in-depth writeups of individual projects or technical challenges. Where the Projects page shows what was built, the Case Studies page explains how and why. What it holds:

• Project background and the problem being solved
• Technical decisions, trade-offs, and architecture notes
• Process documentation, including what changed between early and final versions
• Outcomes, metrics, or lessons learned
• Links to the live project or related pages

Editing notes: Case studies work best when they tell a story with a beginning, a complication, and a resolution. A case study that reads as a list of features is less compelling than one that explains the thinking behind the choices.

---

​

Content Pages

These pages collect written work and third-party validation. They make the portfolio more than a project gallery by showing that the owner thinks, writes, and earns trust from others.

​

articles.html — Article Index

The Articles page serves as a browsable index of shorter written pieces. It is designed to list individual articles with enough context for a visitor to decide which ones to read. What it holds:

• Article titles and publication dates
• Short summaries or excerpts
• Links to the full article, whether hosted on this site or on an external platform
• Topic or category labels

Editing notes:

---

​

writing.html — Writing Archive

The Writing page is the longer-form companion to the Articles page. It is designed for essays, research papers, documentation samples, technical guides, personal writing, or any other extended written work that does not fit neatly into the article format. What it holds:

• Long-form essays or editorial pieces
• Technical documentation samples
• Academic or research writing
• Personal or creative writing relevant to the portfolio

Editing notes: The distinction between Articles and Writing is flexible — use them in whatever way suits the portfolio owner’s output. One approach is to use Articles for shorter pieces under a thousand words and Writing for longer-form work.

---

​

testimonials.html — Testimonials and Feedback

The Testimonials page collects endorsements, recommendations, and feedback from colleagues, clients, employers, or collaborators. Social proof adds credibility that self-description alone cannot provide. What it holds:

• Quoted testimonials with attribution (name, role, and company or context)
• Recommendations from professional contacts
• Client or employer feedback about specific projects or working relationships

Editing notes:

---

​

Utility Pages

​

contact.html — Contact Details

The Contact page gives visitors a clear way to reach the portfolio owner. It is designed to consolidate communication options in one place without requiring a backend form submission. What it holds:

• Email address (linked with mailto:)
• GitHub profile link
• LinkedIn profile link
• Links to any other relevant professional profiles (Dribbble, Behance, Twitter/X, etc.)
• A downloadable résumé or CV link, if applicable

Editing notes: Test every outbound link after editing. Check that the résumé download link points to a real, accessible file and that the email mailto: address is correct.

---

​

placeholders.html — Future Content

The Placeholders page is a staging area for content that has not yet been written, collected, or decided on. It is designed to hold temporary placeholder content so the navigation can remain complete without broken or empty pages. What it holds:

• Placeholder text for sections that are planned but not yet ready
• Notes to yourself about what content should go where
• Temporary filler entries that will be replaced before or after publishing

Editing notes: This is the only page in the theme that is not expected to contain finished content. Everything else should be customized and complete before the site is published.