Skip to main content

Documentation Index

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

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

Fortune Seeker’s content — every heading, bio card, project entry, skill sigil, and testimonial — is defined as plain JavaScript data arrays inside the source page components. To make the template your own, locate the relevant data object in the source file for that page and replace the placeholder values with your details. No routing changes or component rewrites are needed for content updates.

​
Content Overview

About / Bio

The three-card “Past / Present / Future” spread on the About page.

Projects

The Major Arcana grid of project cards with tech stacks and links.

Skills

The six skill sigils, each mapped to a school of magic.

Work History

The vertical timeline of roles, companies, and descriptions.

Blog Posts

The Scribe’s Pages article list with dates and excerpts.

Testimonials

The Channeled Reviews cards with quotes and authors.

​
Updating Your Bio

The About page renders a three-card tarot spread that maps your career arc to The Past, The Present, and The Future. Each card has a title, subtitle, icon component, and freeform content string. 
// Three-card spread data
const cards = [
  {
    title: "The Past",
    subtitle: "Foundations",
    icon: <HourglassIcon />,
    content: "Your early career story...",
    delay: 0.2
  },
  {
    title: "The Present",
    subtitle: "Mastery",
    icon: <FlameIcon />,
    content: "Your current work...",
    delay: 0.4
  },
  {
    title: "The Future",
    subtitle: "Ascension",
    icon: <EyeIcon />,
    content: "Your goals and aspirations...",
    delay: 0.6
  }
];
Replace the content string on each card with your own narrative. The delay values control the Framer Motion entrance stagger — increase the gap for a more dramatic reveal or set them all to 0 to animate simultaneously.

​
Updating Projects

The Projects page (labelled Major Arcana in the nav) displays up to four project cards in a responsive grid. Each card carries a thematic arcana name alongside the real project title, making it easy to lean into the divination aesthetic or tone it down. 
// Project card data
const projects = [
  {
    id: "ecommerce",
    title: "E-Commerce Platform",
    arcana: "The Merchant",
    numeral: "I",
    description: "Your project description...",
    tech: ["Next.js", "TypeScript", "Stripe", "Tailwind"],
    link: "https://your-project.com",
    github: "https://github.com/you/project"
  }
  // Add up to 4 cards for the grid
];
FieldPurpose
idUnique string key for React
titleReal project name shown on the card
arcanaThematic subtitle — rename or remove as you like
numeralRoman numeral displayed as a decorative badge
techArray of technology tags rendered as pill badges
linkLive demo URL (leave empty to hide the button)
githubRepository URL (leave empty to hide the button)
The four placeholder projects are E-Commerce Platform, Analytics Dashboard, AI Writing Assistant, and Atmospheric Oracle. Replace them in order or add/remove entries to fit your actual work.

​
Updating Skills

The Skills page (labelled Cast Spells) renders six skill sigils, each associated with a school of magic drawn from classic RPG lore. The default mapping is:
SkillSchool
ReactEvocation
TypeScriptAbjuration
Node.jsConjuration
TailwindIllusion
GraphQLDivination
PythonTransmutation
To update, edit the skills array in the Skills page component: 
// Skill sigil data
const skills = [
  {
    name: "React",
    type: "Evocation",   // Your chosen magic school label
    path: "M 10 50 ..." // SVG path for the sigil glyph
  }
];
The path field accepts any valid SVG path string. Each sigil is rendered inside a fixed-size SVG viewport, so keep path coordinates within a 0 0 100 100 viewBox for consistent sizing.

​
Updating Work History

The Work History page (labelled Pendulum Swing) renders a vertical timeline. Each entry needs a year range, a job title, a company name, and a short description. 
const workHistory = [
  {
    year: "2023 - Present",
    title: "Senior Alchemist (Frontend)",
    company: "Tech Coven Inc.",
    desc: "Description of your role..."
  }
];
The timeline is rendered top-to-bottom in array order, so put your most recent role first.

​
Updating Blog Posts

The Blog page (labelled Scribe’s Pages) displays a list of articles. Each entry uses a Roman numeral (num) as a decorative index alongside the title, publication date, and a one-line excerpt. 
const articles = [
  {
    num: "I",
    title: "Your Article Title",
    date: "Oct 31, 2023",
    excerpt: "A short teaser sentence."
  }
];
The template ships with three placeholder articles. You can link each entry to an external blog post or CMS page by adding a url field and wiring it to the card’s anchor tag in the Blog component.

​
Navigation Labels

Fortune Seeker’s sidebar and mobile menu are driven by a navLinks array. Each entry maps a route path to its thematic display label: 
const navLinks = [
  { path: "/",            label: "The Reading"      },
  { path: "/about",       label: "The Reader"       },
  { path: "/projects",    label: "Major Arcana"     },
  { path: "/skills",      label: "Cast Spells"      },
  { path: "/work",        label: "Pendulum Swing"   },
  { path: "/case-studies",label: "Deep Reading"     },
  { path: "/blog",        label: "Scribe's Pages"   },
  { path: "/testimonials",label: "Channeled Reviews"},
  { path: "/contact",     label: "Send a Sigil"     },
];
You can rename any label without touching the path — the route will keep working as-is. If you prefer conventional labels (e.g. “About” instead of “The Reader”), simply update the string. See the Routes page if you also need to add or remove entries from this array.
All content data in the deployed template lives inside the compiled assets/main.js bundle. Editing that file directly is possible but fragile — any rebuild will overwrite your changes. For a maintainable workflow, fork the source repository where each page’s data objects live in individual component files alongside their JSX, making updates straightforward and rebuild-safe.

Build docs developers (and LLMs) love

Get started for freeTalk to us