Publishing on Vivum
How to publish
Vivum is an index, not a host. You publish your article independently — on GitHub Pages or any public URL — and submit the link here. You retain full ownership. Vivum lists your article, provides a community discussion layer, and can trigger formal peer review once a threshold is reached.
Step 1 — Write your article
Choose any web-native format. The only requirement is that the article is primarily interactive — the web medium should contribute something a PDF cannot: live parameter sliders, explorable simulations, interactive figures, embedded analysis tools, or step-by-step interactive tutorials.
Both novel research and educational explainers are welcome.
| Distill template | HTML + Svelte. The canonical format for interactive research articles. Template on GitHub → |
|---|---|
| Observable | Reactive JavaScript notebooks. Excellent for data-driven articles. observablehq.com → |
| Shiny / Quarto | R-native. Ideal for statistical analyses and bioinformatics. shiny.posit.co → |
| Plotly Dash | Python-native. Strong for biomedical data and genomics. dash.plotly.com → |
| Jupyter Book | Executable books with embedded widgets. jupyterbook.org → |
| Custom HTML/JS | No framework required. If you can host a static HTML file, you can publish on Vivum. |
Step 2 — Host it publicly
Your article needs a stable public URL. GitHub Pages is the most common choice — free, version-controlled, and permanent as long as the repository exists.
| GitHub Pages | Free. Deploy from any public repository. pages.github.com → |
|---|---|
| Netlify | Free tier. Continuous deployment from Git. |
| Vercel | Free tier. Fast global CDN. Good for JS build pipelines. |
| shinyapps.io | Free tier for Shiny applications. |
| Any static host | Amazon S3, Cloudflare Pages, Render, or your own server. Any stable HTTPS URL is accepted. |
Step 3 — Submit to Vivum
Once your article is live, submit it using the form. Your article enters the public feed immediately, where the community can read, comment, upvote, and nominate it for peer review.
Submitting a GitHub repository URL alongside the live URL is strongly encouraged — it allows readers to inspect the code, reproduce the analysis, and verify interactive claims independently.
Step 4 — Keeping your article up to date
Because Vivum links to your article rather than hosting it, you control every update. If you make a significant change — new results, a revised methodology, corrected figures — visit your article's page on Vivum and use the Version history section to log what changed. This keeps the record transparent for readers and reviewers.
Minor edits like typo fixes or styling tweaks don't need to be logged. Reserve version notes for changes that affect the scientific content.
What happens after submission
| Immediately | Your article enters the moderation queue. Once cleared (usually within 24 hours), it appears in the Vivum feed. |
|---|---|
| At threshold | Once community score, comment count, and nominations cross a combined threshold, your article enters the formal review queue. |
| After review | A reviewer publishes a structured note covering significance, reproducibility, and clarity. Your article receives a DOI via Zenodo and a reviewed status on Vivum. It becomes formally citable. |