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.

The Welcome, Mortals repository includes structured issue templates that make it straightforward to report a problem or request an addition. Using a template ensures your report includes the context needed to understand and act on the feedback — no back-and-forth to gather basic details like which page is affected or which browser you were using.

Issue templates

The .github/ISSUE_TEMPLATE/ folder contains three templates, each suited to a different type of submission.

Bug Report

bug_report.md — Use this template to report broken links, missing images, layout problems, or any other unexpected behavior in the theme.

Feature Request

feature_request.md — Use this template to request new pages, additional design options, new interactions, or other additions to the theme.

Custom Request

custom.md — Use this template for any other type of request that doesn’t fit the bug or feature categories.

Choose a Template

Open the issue submission page to select the right template and submit your report directly to the repository.

What to include in a bug report

A useful bug report lets the maintainer reproduce the problem without needing to ask follow-up questions. When you open a bug report, include:
  • Affected page — which HTML page the issue occurs on (for example, projects.html or contact.html)
  • Browser and device — the browser name and version, and whether you were on desktop or mobile
  • Description — what you expected to happen, what actually happened, and the steps to reproduce it
  • Screenshot — a screenshot or screen recording when possible, especially for layout or visual problems
If the issue only occurs at a specific viewport width or after a particular interaction (such as the spider scare appearing), include those details in the description. Intermittent or interaction-triggered bugs are harder to reproduce without that context.

What to include in a feature request

A clear feature request helps communicate both the desired addition and why it would be useful. When you open a feature request, include:
  • Description of the requested addition — what you’d like to see added or changed, described as specifically as possible
  • Use case — how the addition would be used and why it would improve the theme for portfolio owners or their visitors
  • Examples or references — links, sketches, or descriptions of similar implementations if you have them
Feature requests are welcomed but are not guarantees of implementation. The most useful requests are specific, actionable, and connected to a clear use case rather than a general direction.

Submit an issue

Select the appropriate template and open your report at the link below: Report an issue or request an addition →

Possible future enhancements

The README documents a set of enhancements that have been identified as worthwhile additions to the theme. These are not committed features — they represent directions the theme could grow if time and scope allow.
  • Visible reduced-motion toggle — A control that visitors can activate directly on the site to switch to a calmer experience, without relying solely on the operating system’s reduced-motion preference setting.
  • Seasonal alternate palettes — Additional color palette options tied to different times of year, allowing portfolio owners to vary the theme’s visual mood beyond the default Halloween-orange-and-purple scheme.
  • Themed 404.html page — A custom error page styled as a locked crypt door, consistent with the haunted-house aesthetic, rather than a default browser or host error page.
  • Optional screenshot thumbnails for the theme collection — Thumbnail images that could be added to the main Portfolio Themes Templates collection listing, giving visitors a quick visual preview of the Welcome, Mortals theme before clicking through to the demo.
  • Additional issue form categories — Expanded issue templates to cover more specific types of feedback as the theme collection grows and more submission types are needed.
If you’d like to advocate for one of these or suggest a variation, open a feature request using the template linked above.

Repository relationship

Welcome, Mortals is maintained as a standalone repository and linked from the main Portfolio Themes Templates collection. If you arrived here through the collection, both repositories are relevant:
RepositoryPurpose
welcome-mortals-github-pages-themeSource files, documentation, issue templates, and live demo for this theme
portfolio-themes-templatesMain collection directory linking to all themes including Welcome, Mortals
File issues about the Welcome, Mortals theme itself — broken layout, missing files, interaction problems, or theme-specific requests — in the Welcome, Mortals repository using the templates above.

Build docs developers (and LLMs) love