Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/modernharp/StrangerThingsIntroMaker/llms.txt

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

Because the Stranger Things Intro Creator is a pure static site — no server, no database, no backend logic — deployment is straightforward on any platform that can serve static files. Pick the option below that best fits your workflow: a zero-config cloud host like Vercel or Netlify, GitHub Pages for repository-native hosting, or a self-managed web server for full infrastructure control.

​
Building for Production

Before deploying, generate an optimized production build: 
npm run build
The build process bundles and minifies the HTML, CSS, and JavaScript into a static output directory. That directory contains everything a web server needs to serve the app; no runtime environment is required beyond a standard HTTP server. Check your terminal output or the project’s README for the exact name of the build output directory.

​
Deploy to Vercel

Vercel is the recommended platform for its zero-config experience and automatic continuous deployment.
1

Push your repository to GitHub

Make sure your local repository (including any customizations) is pushed to a GitHub repository under your account.
2

Import the repository on Vercel

Go to vercel.com, sign in, and click Add New → Project. Select your GitHub repository from the list.
3

Accept the auto-detected settings

Vercel automatically detects the framework and pre-fills the build command and output directory. No manual configuration is needed — accept the defaults and proceed.
4

Click Deploy

Click Deploy. Vercel builds the project and provides you with a live URL within seconds.
Vercel automatically redeploys your site on every push to the main branch, so your live instance stays up to date with your repository without any manual steps.

​
Deploy to Netlify

1

Push your repository to GitHub

Ensure your repository is available on GitHub (or GitLab / Bitbucket — Netlify supports all three).
2

Create a new site on Netlify

Log in to netlify.com, click Add new site, and select Import an existing project. Choose GitHub as the Git provider and authorize Netlify if prompted.
3

Select the repository and accept defaults

Pick your repository from the list. Netlify will detect the build settings automatically. Confirm the build command and publish directory, then proceed.
4

Click Deploy Site

Click Deploy Site. Netlify runs the build and publishes the result to a *.netlify.app subdomain. You can attach a custom domain from the site settings at any time.

​
Deploy to GitHub Pages

1

Enable GitHub Pages in the repository settings

Navigate to your repository on GitHub, go to Settings → Pages, and enable GitHub Pages for the repository.
2

Set the publishing source

Choose a source for your Pages deployment:
  • Dedicated branch — push your build output to a dedicated gh-pages branch (tools like the gh-pages npm package automate this).
  • docs/ folder on main — configure your build to output into a docs/ directory and commit it.
  • GitHub Actions — use a workflow (for example the official actions/deploy-pages action) to build and publish automatically on every push.
3

Access your deployed site

Once the Pages build completes, your instance will be live at:
https://<your-github-username>.github.io/StrangerThingsIntroMaker/
Replace <your-github-username> with your actual GitHub username.

​
Custom Domain

All three platforms above support custom domains at no extra cost:
  1. In your hosting platform’s dashboard, navigate to the Domains or Custom Domain settings for your site and add your domain.
  2. At your DNS registrar, create either:
    • A CNAME record pointing your subdomain (e.g., intro.yourdomain.com) to the platform-provided hostname, or
    • A records pointing your apex domain to the platform’s IP addresses (refer to your platform’s documentation for the exact values).
  3. Wait for DNS propagation (typically a few minutes to a few hours), then verify the domain in the platform dashboard.

​
Nginx / Self-Managed Server

If you prefer to run your own web server, copy the production build output to your server and use a minimal Nginx configuration like the following: 
server {
    listen 80;
    server_name yourdomain.com;
    root /var/www/StrangerThingsIntroMaker/<build-output-directory>;
    index index.html;

    location / {
        try_files $uri $uri/ /index.html;
    }
}
Replace yourdomain.com with your actual domain and replace <build-output-directory> with the name of the directory produced by your build step. The try_files directive ensures that the single-page app handles all routes correctly.
Always serve the Stranger Things Intro Creator over HTTPS in production. Browsers increasingly restrict features on insecure origins, and your users’ shareable links should be served securely. Use a hosting provider that handles TLS automatically (Vercel, Netlify, and GitHub Pages all do), or configure Let’s Encrypt with Certbot on your self-managed server.

​
Next Steps

Have an improvement, bug fix, or new feature in mind? See the Contributing Guidelines to learn how to submit a pull request to the upstream project.

Build docs developers (and LLMs) love

Get started for freeTalk to us