Deep dives,
written by the community.
Structured write-ups people produce after a deep dive: hardening guides, experiments, toolkits. The wiki credits the author, renders the work in full and links back to its canonical home, where the author stays in control.
Wrote something worth keeping?
Guides, benchmarks, post-mortems and toolkits all fit. Send a public https link, the credit name you want shown and a one-line summary. A maintainer reads every submission before it is listed.
What this section holds
Credited write-ups. The guide keeps its own home; the wiki renders it in full and stores a clean copy as a fallback.
Real credit. Author name, the original post, and an optional link to their vram.wiki profile.
Context. Topics, capacity range and the related setups, so a paper is easy to place.
Human review. Every submission is read and rendered before publication, and only public https links are accepted.
Writing guidelines
Markdown, self-hosted. Write in Markdown and host it yourself (GitHub, a gist, your blog). We render it and always link back to the source.
Stable link. Use a permanent public https URL, not a temporary share link.
License and credit. State a license, and the name or handle you want shown. A vram.wiki profile link is optional.
Say what you tested. Hardware, exact commands or config, results and known limits. A clear structure (goal, setup, steps, results, caveats) beats length.
Human review. Every submission is read before it is listed, and only public https links are accepted. Nothing is embedded automatically.