Appearance

Get involved ​

Vizoalica is open source and built in the open. It gets better when the people who run it say what works, what does not, and what is missing. You do not need to write code, and small contributions count.

Everything happens on GitHub, so there is one place to look.

Share an ideaWhat would make Vizoalica more useful to you? A rough thought is fine. Start a discussion
Report a problemSomething broke, or a page was confusing. Open an issue
Help build itPick up a small, well-described task, or propose your own. Good first issues

Ways to help ​

  1. Try it and tell us what happened. Follow the quick start. If a step was confusing or broke, that is the most useful thing you can report.
  2. Share an idea in Discussions → Ideas. Others can add to it, and it can become an issue later.
  3. Answer a question, or show how you run it in Show and tell.
  4. Improve these docs. Every page has an Edit this page on GitHub link, so a typo or a clearer sentence is a pull request away.
  5. Pick up an issue. Look for good first issue or help wanted, and comment that you are taking it.
  6. Build something bigger. Talk first: open an idea or an issue, agree the outline, then send a pull request.

What the project holds to ​

Ideas are judged against what Vizoalica is for, so you can tell early whether one fits.

  • Privacy-minimal. It collects no more about visitors than it needs, and never form values, page text, or session replay. See the privacy defaults.
  • Self-hosted and portable. It runs in the operator’s own Cloudflare account, with no service of ours in the middle.
  • Easy to audit. A self-hosting operator can read what it does.
  • Cheap and simple to run. See the cost model.
  • Accessible. The console keeps WCAG 2.2 AA.

A good idea that does not fit is still worth sharing. It may suit an example, a guide, or a fork.

Ground rules ​

Everyone taking part follows the code of conduct. The contributing guide covers setup, pull requests, and keeping credentials and visitor data out of anything you post, and support says where each kind of question goes. To report a vulnerability, use a private advisory, never a public post.