Your server deserves better than a Discord invite
A finished website for a hardcore roleplay server — not a starter, not a wireframe. A landing page, a guides page and a 404 that matches, written out and ready to have your server’s name put in.
Almost no server has a website
Not because they do not want one. Because the quote was four hundred euro, or the free template could not be changed without editing somebody else’s CSS at midnight.
HTML, one stylesheet, one small script. No PHP, no database, no Node on the server. Any host that serves a web page serves this.
Search for DEATH and you have found your server name,
in three places. Search for discord.gg and you have
found every link. That is the whole rebrand.
1.1 MB of WebP where the original had 8 MB of PNG. That is where your players will open it first, on mobile data, once.
Meta tags, Open Graph, Twitter cards, schema.org, a sitemap and a robots.txt. Paste the link in Discord and it renders a proper card.
Three pages, all finished
Every one written out with real copy. You are editing, not starting.
The landing page
A hero with a floating logo, a stats bar, six feature cards, a four-step explainer, four role cards, the rules, a closing call to action and a four-column footer.
Sections are marked in the markup. Delete one and its heading, its nav link and its footer link are the only three things you touch.
Guides & rules
A sticky sidebar, an injury table, the full rules numbered so “rule 3.2” still means the same thing next month, and an FAQ that opens and closes with no JavaScript at all.
In the site this came from, that page was an empty shell that fetched its content from a PHP admin panel. It is plain HTML now.
And a 404
Because a broken link on a server website usually means somebody followed a Discord post from six months ago, and a default Apache error page is a bad way to meet them.
The design is the original. Everything under it is not.
This was a real server’s website. We took the backend out and rebuilt what was left properly.
On the stylesheet. The original loaded Tailwind from a CDN, which ships 120 KB of JavaScript and then builds your CSS in the visitor’s browser on every page load — something Tailwind’s own documentation tells you not to do in production. It is a 22 KB file now. Ten elements across twelve computed properties were compared against the CDN build before the swap; every value matches.
One thin bar at the top
Every page carries a small bar with our mark and a link back here. That is the only thing we ask for.
You are allowed to remove it. No conditions, nothing breaks, nothing phones home. It is one clearly marked block in each file, and the bar itself carries a link to the page that explains how.
If you leave it up, thank you — it is genuinely how people find us, and it is the reason the next one is also free.
<!-- ╔════════════════════════════════════╗
║ VAULT SCRIPTS CREDIT BAR ║
║ Delete to the END marker. ║
╚════════════════════════════════════╝ -->
<div class="relative bg-black ...">
...
</div>
<!-- ╚══ END VAULT SCRIPTS CREDIT BAR ══╝ -->Three files, same markers in each. The full instructions.
What it needs
Cloudflare Pages, Netlify, GitHub Pages, or the cPanel your host already gave you. The first three are free and the docs walk through all of them.
That is the whole toolchain. There is an optional Tailwind config in the download if you want to recompile the stylesheet, and you can ignore it entirely.
It does not talk to your game server at all, so QBCore, Qbox, ESX or a bare server makes no difference. If you want the player count, characters and playtime on your site properly, that needs a backend — and that is a different thing we are building.
Free, and the source is public
MIT licence. Use it commercially, rebrand it, charge a client for it. The whole repository is public so you can read every line before you trust it.
The character art bundled with it is Rockstar’s, included so the template looks like something the moment you open it. Replace it before you go commercial — it is one folder of files.