import PublicLayout from '../layouts/PublicLayout.astro';
---
<PublicLayout title="About" description="Learn about Likwid, a modular governance engine for distributed organizations, open source communities, and civic movements.">
<article class="about-page">
<header class="page-header">
<h1>About Likwid</h1>
<p class="lead">
Likwid is a modular governance engine designed for organizations that need
structured, transparent, and auditable decision-making processes.
</p>
</header>
<section class="content-section">
<h2>What Problem Does Likwid Solve?</h2>
<p>
Most organizations—whether open source projects, political movements, or member associations—struggle
with collective decision-making. They often rely on informal processes, ad-hoc polls, or tools designed
for other purposes (forums, chat platforms, issue trackers).
</p>
<p>
These approaches fail in predictable ways:
</p>
<ul class="problem-list">
<li><strong>Lack of structure</strong> — Discussions drift without resolution. Decisions are made implicitly or by whoever speaks loudest.</li>
<li><strong>No audit trail</strong> — When moderation happens, there's no record of why. Shadow banning and hidden decisions erode trust.</li>
<li><strong>Limited voting methods</strong> — Simple majority voting fails for complex decisions with multiple options or competing priorities.</li>
<li><strong>Participation barriers</strong> — Members who can't attend synchronous meetings or follow high-volume discussions are effectively excluded.</li>
</ul>
<p>
Likwid addresses these problems by providing governance as infrastructure: a system that structures
deliberation, enforces transparency, and supports sophisticated decision-making methods.
</p>
</section>
<section class="content-section">
<h2>What Likwid Is</h2>
<div class="is-grid">
<div class="is-item">
<h4>A Governance Engine</h4>
<p>Likwid provides the core infrastructure for collective decision-making: proposals, deliberation, voting, and implementation tracking.</p>
</div>
<div class="is-item">
<h4>Modular by Design</h4>
<p>Every component is a plugin. Communities choose their voting methods, delegation rules, moderation policies, and integrations.</p>
</div>
<div class="is-item">
<h4>Transparent by Default</h4>
<p>All moderation actions are logged with reasons. There is no shadow banning. Audit trails are cryptographically verifiable.</p>
</div>
<div class="is-item">
<h4>Self-Hostable</h4>
<p>Organizations control their own data. Likwid runs on your infrastructure with no vendor lock-in.</p>
</div>
</div>
</section>
<section class="content-section">
<h2>What Likwid Is Not</h2>
<div class="isnot-grid">
<div class="isnot-item">
<h4>Not a Social Network</h4>
<p>Likwid is not designed for casual conversation, content sharing, or social interactions. It's governance infrastructure.</p>
</div>
<div class="isnot-item">
<h4>Not a Simple Poll Tool</h4>
<p>While Likwid supports voting, it's designed for complex decisions with deliberation phases, multiple options, and sophisticated tallying methods.</p>
</div>
<div class="isnot-item">
<h4>Not a Forum</h4>
<p>Discussions in Likwid are structured and goal-oriented. They're part of a decision process, not open-ended conversation.</p>
</div>
<div class="isnot-item">
<h4>Not a CRM or Membership System</h4>
<p>Likwid handles governance, not member management, donations, or communications. It integrates with those systems.</p>
</div>
</div>
</section>
<section class="content-section">
<h2>Who Is Likwid For?</h2>
<div class="audience-section">
<div class="audience-block">
<h4>Open Source & FLOSS Communities</h4>
<p>
Projects that need to make technical and organizational decisions collectively.
Maintainers, contributors, and users participating in governance alongside code contribution.
Integration with development workflows (GitLab, Forgejo, Gitea) and documentation systems.
