Updates
This commit is contained in:
2
.gitignore
vendored
2
.gitignore
vendored
@@ -5,3 +5,5 @@
|
||||
|
||||
# Hugo cache
|
||||
/.hugo_build.lock
|
||||
|
||||
.working
|
||||
|
||||
99
CLAUDE.md
Normal file
99
CLAUDE.md
Normal file
@@ -0,0 +1,99 @@
|
||||
# CLAUDE.md
|
||||
|
||||
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
||||
|
||||
## Overview
|
||||
|
||||
CivilSociety.dev is a Hugo-based static website focused on digital sovereignty, civil society, and technology independence. The site uses the Blowfish theme and contains educational content about technology, governance, and open-source principles.
|
||||
|
||||
## Development Commands
|
||||
|
||||
### Development Server
|
||||
```bash
|
||||
hugo server
|
||||
```
|
||||
Starts the development server with live reload at http://localhost:1313
|
||||
|
||||
### Build
|
||||
```bash
|
||||
hugo build
|
||||
```
|
||||
Builds the static site to the `public/` directory
|
||||
|
||||
### Dependencies
|
||||
- Install hugo (static site generator)
|
||||
- Install dart-sass (CSS processing)
|
||||
|
||||
## Deployment
|
||||
|
||||
### Local Docker Build
|
||||
```bash
|
||||
hugo build
|
||||
docker build -t payneio/civilsociety.dev . --file ./Dockerfile
|
||||
docker push payneio/civilsociety.dev
|
||||
```
|
||||
|
||||
### Production Deployment
|
||||
From payne-cloud environment:
|
||||
```bash
|
||||
# First time deployment
|
||||
bin/wild-app-deploy civilsociety
|
||||
|
||||
# Updates
|
||||
kubectl rollout restart deployment civilsociety -n civilsociety
|
||||
```
|
||||
|
||||
## Site Architecture
|
||||
|
||||
### Content Structure
|
||||
- `content/` - All site content in Markdown format
|
||||
- `articles/` - Main articles and blog posts
|
||||
- `foundation/` - Foundational documents (charter, principles, mission)
|
||||
- `learning/` - Educational content (git, linux, software development)
|
||||
- `projects/` - Project documentation
|
||||
- `contribute.md` - Contribution guidelines
|
||||
|
||||
### Configuration
|
||||
- `config/_default/` - Hugo configuration split across multiple files
|
||||
- `hugo.toml` - Main site configuration
|
||||
- `params.toml` - Theme-specific parameters
|
||||
- `menus.en.toml` - Navigation menu structure
|
||||
- `languages.en.toml` - Language settings
|
||||
|
||||
### Theme
|
||||
- Uses the Blowfish theme (located in `themes/blowfish/`)
|
||||
- Theme is included as a git submodule
|
||||
- Custom CSS can be added in `assets/css/custom.css`
|
||||
|
||||
### Static Assets
|
||||
- `static/` - Static files served directly
|
||||
- `assets/` - Assets processed by Hugo
|
||||
- `public/` - Generated output directory (not committed)
|
||||
|
||||
## Content Guidelines
|
||||
|
||||
### Page Organization
|
||||
- Articles use bundle structure with `index.md` and associated images
|
||||
- Featured images should be named `featured.png` or `featured.jpg`
|
||||
- Use front matter for metadata (title, date, tags, etc.)
|
||||
|
||||
### Hugo Features Used
|
||||
- Page bundles for content organization
|
||||
- Taxonomies (tags, categories, authors, series)
|
||||
- Related content based on tags/categories
|
||||
- RSS feeds and JSON output
|
||||
- Multilingual support configured but primarily English
|
||||
|
||||
## Docker Deployment
|
||||
|
||||
The site is containerized using a simple Nginx Alpine image:
|
||||
- Hugo builds static files to `public/`
|
||||
- Dockerfile copies `public/` to Nginx document root
|
||||
- No server-side processing required
|
||||
|
||||
## Development Notes
|
||||
|
||||
- The site focuses on digital sovereignty and civil society topics
|
||||
- Content includes technical tutorials, political philosophy, and project documentation
|
||||
- Uses Google Analytics (G-606W7SWX5E) for tracking
|
||||
- SEO-optimized with proper meta tags and sitemap generation
|
||||
@@ -15,5 +15,12 @@ hugo server
|
||||
hugo build
|
||||
docker build -t payneio/civilsociety.dev . --file ./Dockerfile
|
||||
docker push payneio/civilsociety.dev
|
||||
kubectl apply -f definition.yml
|
||||
|
||||
# From payne-cloud
|
||||
|
||||
# First time...
|
||||
bin/wild-app-deploy civilsociety
|
||||
|
||||
# Update...
|
||||
kubectl rollout restart deployment civilsociety -n civilsociety
|
||||
```
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
# https://blowfish.page/docs/getting-started/
|
||||
|
||||
theme = "blowfish"
|
||||
baseURL = "https://www.civilsociety.dev/"
|
||||
baseURL = "https://civilsociety.dev/"
|
||||
defaultContentLanguage = "en"
|
||||
|
||||
# pluralizeListTitles = "true" # hugo function useful for non-english languages, find out more in https://gohugo.io/getting-started/configuration/#pluralizelisttitles
|
||||
@@ -16,7 +16,7 @@ buildFuture = false
|
||||
|
||||
enableEmoji = true
|
||||
|
||||
# googleAnalytics = "G-XXXXXXXXX"
|
||||
googleAnalytics = "G-606W7SWX5E"
|
||||
|
||||
[pagination]
|
||||
pagerSize = 100
|
||||
|
||||
@@ -2,7 +2,7 @@ disabled = false
|
||||
languageCode = "en"
|
||||
languageName = "English"
|
||||
weight = 1
|
||||
title = "CivilSociety.dev"
|
||||
title = "Civil Society Technology Foundation"
|
||||
|
||||
[params]
|
||||
displayName = "EN"
|
||||
|
||||
@@ -10,86 +10,31 @@
|
||||
# overridden by providing a weight value. The menu will then be
|
||||
# ordered by weight from lowest to highest.
|
||||
|
||||
[[main]]
|
||||
name = "About"
|
||||
pageRef = "foundation"
|
||||
weight = 30
|
||||
|
||||
[[main]]
|
||||
name = "Getting Started"
|
||||
pageRef = "getting-started"
|
||||
weight = 20
|
||||
|
||||
# About
|
||||
name = "Articles"
|
||||
pageRef = "articles"
|
||||
weight = 40
|
||||
|
||||
[[main]]
|
||||
name = "About"
|
||||
pageRef = "about"
|
||||
weight = 30
|
||||
name = "Projects"
|
||||
pageRef = "projects"
|
||||
weight = 50
|
||||
|
||||
[[main]]
|
||||
name = "Charter"
|
||||
pageRef = "charter"
|
||||
parent = "About"
|
||||
weight = 10
|
||||
name = "Wild Cloud"
|
||||
parent = "Projects"
|
||||
pageRef = "projects/wild-cloud"
|
||||
weight = 10
|
||||
|
||||
[[main]]
|
||||
name = "Mission Statement"
|
||||
pageRef = "mission-statement"
|
||||
parent = "About"
|
||||
weight = 20
|
||||
|
||||
[[main]]
|
||||
name = "Core Principles"
|
||||
pageRef = "core-principles"
|
||||
parent = "About"
|
||||
weight = 30
|
||||
|
||||
[[main]]
|
||||
name = "The Importance of Independent Technology"
|
||||
pageRef = "independent-technology"
|
||||
parent = "About"
|
||||
weight = 40
|
||||
|
||||
[[main]]
|
||||
name = "Why Digital Sovereignty Matters"
|
||||
pageRef = "why-digital-sovereignty-matters"
|
||||
parent = "About"
|
||||
weight = 50
|
||||
|
||||
[[main]]
|
||||
name = "Arguments Against Centralization"
|
||||
pageRef = "arguments-against-centralization"
|
||||
parent = "About"
|
||||
weight = 60
|
||||
|
||||
[[main]]
|
||||
name = "Position Statements"
|
||||
pageRef = "position-statements"
|
||||
parent = "About"
|
||||
weight = 70
|
||||
|
||||
[[main]]
|
||||
name = "Governance"
|
||||
pageRef = "projects/governance"
|
||||
parent = "About"
|
||||
weight = 80
|
||||
|
||||
[[main]]
|
||||
|
||||
# Projects
|
||||
|
||||
[[main]]
|
||||
name = "Projects"
|
||||
pageRef = "projects"
|
||||
weight = 40
|
||||
|
||||
[[main]]
|
||||
name = "Sovereign Cloud"
|
||||
parent = "Projects"
|
||||
pageRef = "projects/sovereign-cloud"
|
||||
weight = 20
|
||||
|
||||
[[main]]
|
||||
name = "Learning"
|
||||
pageRef = "learning"
|
||||
weight = 90
|
||||
name = "Learning"
|
||||
pageRef = "learning"
|
||||
weight = 60
|
||||
|
||||
#[[main]]
|
||||
# name = "example sub-menu 2"
|
||||
|
||||
@@ -28,8 +28,8 @@ disableTextInHeader = false
|
||||
# smartTOC = true
|
||||
# smartTOCHideUnfocusedChildren = true
|
||||
|
||||
giteaDefaultServer = "https://git.fsfe.org"
|
||||
forgejoDefaultServer = "https://v8.next.forgejo.org"
|
||||
# giteaDefaultServer = "https://git.fsfe.org"
|
||||
# forgejoDefaultServer = "https://v8.next.forgejo.org"
|
||||
|
||||
[header]
|
||||
layout = "basic" # valid options: basic, fixed, fixed-fill, fixed-gradient, fixed-fill-blur
|
||||
@@ -37,23 +37,23 @@ forgejoDefaultServer = "https://v8.next.forgejo.org"
|
||||
[footer]
|
||||
showMenu = true
|
||||
showCopyright = true
|
||||
showThemeAttribution = true
|
||||
showThemeAttribution = false
|
||||
showAppearanceSwitcher = true
|
||||
showScrollToTop = true
|
||||
|
||||
[homepage]
|
||||
layout = "profile" # valid options: page, profile, hero, card, background, custom
|
||||
#homepageImage = "IMAGE.jpg" # used in: hero, and card
|
||||
showRecent = false
|
||||
showRecentItems = 5
|
||||
showRecent = ["articles"]
|
||||
showRecentItems = 3
|
||||
showMoreLink = false
|
||||
showMoreLinkDest = "/posts/"
|
||||
cardView = false
|
||||
showMoreLinkDest = "/articles/"
|
||||
cardView = true
|
||||
cardViewScreenWidth = false
|
||||
layoutBackgroundBlur = false # only used when layout equals background
|
||||
|
||||
[article]
|
||||
showDate = false
|
||||
showDate = true
|
||||
showViews = false
|
||||
showLikes = false
|
||||
showDateOnlyInArticle = false
|
||||
@@ -75,13 +75,13 @@ forgejoDefaultServer = "https://v8.next.forgejo.org"
|
||||
invertPagination = false
|
||||
showReadingTime = true
|
||||
showTableOfContents = true
|
||||
# showRelatedContent = false
|
||||
# relatedContentLimit = 3
|
||||
showRelatedContent = true
|
||||
relatedContentLimit = 3
|
||||
showTaxonomies = false
|
||||
showAuthorsBadges = false
|
||||
showWordCount = true
|
||||
sharingLinks = [ "linkedin", "twitter", "bluesky", "mastodon", "reddit", "pinterest", "facebook", "email", "whatsapp", "telegram"]
|
||||
showZenMode = false
|
||||
showZenMode = true
|
||||
|
||||
[list]
|
||||
showHero = false
|
||||
|
||||
@@ -1,15 +1,21 @@
|
||||
+++
|
||||
title = 'Welcome to CivilSociety.dev'
|
||||
+++
|
||||
---
|
||||
title: 'Welcome to CivilSociety.dev'
|
||||
---
|
||||
|
||||
[The Importance of Independent Technology](/foundation/independent-technology) - Cornerstone essay on why independent technology matters for civil society
|
||||
As civil society organizations become increasingly dependent on digital tools, the question of who controls that technology becomes a matter of democratic importance.
|
||||
|
||||
[Why Digital Sovereignty Matters](/foundation/why-digital-sovereignty-matters) - Accessible primer on digital sovereignty and its importance
|
||||
The Civil Society Technology Foundation develops and disseminates open-source, self-hosted technologies that enable genuine digital sovereignty. We provide the tools, knowledge, and community support necessary for civil society to operate independently of surveillance-based platforms and extractive business models.
|
||||
|
||||
[Arguments Against Centralization](/foundation/arguments-against-centralization) - Comprehensive resource categorizing various arguments against digital centralization
|
||||
Our work spans software development, educational resources, and community engagement—creating pathways to technological self-determination for organizations that can't afford to compromise their values.
|
||||
|
||||
[Position Statements](/foundation/position-statements) - Our formal positions on key issues affecting digital sovereignty
|
||||
{{< button href="/foundation/" target="_self" >}}
|
||||
Learn More
|
||||
{{< /button >}}
|
||||
|
||||
<div class="flex flex-col gap-8">
|
||||
{{< article link="/articles/independent-technology/" >}}
|
||||
{{< article link="/articles/why-digital-sovereignty-matters/" >}}
|
||||
{{< article link="/articles/arguments-against-centralization/" >}}
|
||||
</div>
|
||||
|
||||
[Getting started](/learning/getting-started)
|
||||
|
||||
<!-- <a class="f6 link dim ba ph3 pv2 mb2 dib black" href="/learning/getting-started">Getting Started</a> -->
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
+++
|
||||
title = 'About the Civil Society Technology Foundation'
|
||||
+++
|
||||
|
||||
The **Civil Society Technology Foundation (CSTF)** is a community-driven organization dedicated to empowering individuals and civil society organizations to reclaim digital sovereignty through open-source tools and self-hosted infrastructure.
|
||||
|
||||
## Our Mission
|
||||
|
||||
We believe that independent, community-controlled technology is essential for a vibrant civil society in the digital age. As digital systems increasingly mediate civic participation, it's vital that these systems remain under the control of the communities they serve, rather than consolidated in the hands of governments or corporations.
|
||||
|
||||
The Civil Society Technology Foundation works to achieve this vision through:
|
||||
|
||||
- **Creating Educational Resources** that build technical literacy and sovereignty awareness
|
||||
- **Developing Reference Implementations** like the Sovereign Cloud for self-hosted infrastructure
|
||||
- **Building Community** around sovereign technology practices and principles
|
||||
- **Advancing Open Standards** that enable interoperability without centralized control
|
||||
- **Supporting Civil Society Organizations** in their journey toward digital independence
|
||||
|
||||
## Who We Are
|
||||
|
||||
- [Charter](/foundation/charter) - The comprehensive founding document for the organization, including structure, governance, and strategic focus areas
|
||||
- [Mission Statement](/foundation/mission-statement) - Our concise mission and approach to digital sovereignty
|
||||
- [Core Principles](/foundation/core-principles) - Detailed explanations of our 11 guiding principles with practical implications
|
||||
|
||||
## What We Believe
|
||||
|
||||
- [The Importance of Independent Technology](/foundation/independent-technology) - Cornerstone essay on why independent technology matters for civil society
|
||||
- [Why Digital Sovereignty Matters](/foundation/why-digital-sovereignty-matters) - Accessible primer on digital sovereignty and its importance
|
||||
- [Arguments Against Centralization](/foundation/arguments-against-centralization) - Comprehensive resource categorizing various arguments against digital centralization
|
||||
- [Position Statements](/foundation/position-statements) - Our formal positions on key issues affecting digital sovereignty
|
||||
9
content/articles/_index.md
Normal file
9
content/articles/_index.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
title: "Articles"
|
||||
cascade:
|
||||
showReadingTime: true
|
||||
showWordCount: true
|
||||
params:
|
||||
heroStyle: background
|
||||
---
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Arguments Against Centralization'
|
||||
+++
|
||||
---
|
||||
title: Arguments Against Centralization
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
## Executive Summary
|
||||
|
||||
|
Before Width: | Height: | Size: 936 KiB After Width: | Height: | Size: 936 KiB |
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'The Importance of Independent Technology in Civil Society'
|
||||
+++
|
||||
---
|
||||
title: The Importance of Independent Technology in Civil Society
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -170,11 +171,11 @@ Despite these challenges, AI also presents significant opportunities for digital
|
||||
|
||||
The path we choose with AI—toward further centralization or toward democratization—will significantly shape the future of digital self-determination. By supporting open, efficient, and community-governed approaches to AI, we can ensure that these powerful tools enhance rather than undermine human agency and collective well-being.
|
||||
|
||||
## Case Study: The Sovereign Cloud
|
||||
## Case Study: Wild Cloud
|
||||
|
||||
The Civil Society Technology Foundation's Sovereign Cloud project exemplifies the principles of independent technology in practice. This reference implementation demonstrates how civil society organizations can regain digital sovereignty through practical, accessible tools.
|
||||
The Civil Society Technology Foundation's Wild Cloud project exemplifies the principles of independent technology in practice. This reference implementation demonstrates how civil society organizations can regain digital sovereignty through practical, accessible tools.
|
||||
|
||||
The Sovereign Cloud provides:
|
||||
Wild Cloud provides:
|
||||
|
||||
- **Self-Hosted Services**: Organizations can run their own email, calendar, file storage, website, and collaboration tools on infrastructure they control, reducing dependency on corporate platforms.
|
||||
|
||||
|
Before Width: | Height: | Size: 1.3 MiB After Width: | Height: | Size: 1.3 MiB |
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Why Digital Sovereignty Matters'
|
||||
+++
|
||||
---
|
||||
title: Why Digital Sovereignty Matters
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
## What Is Digital Sovereignty?
|
||||
|
||||
@@ -186,7 +187,7 @@ Achieving greater digital sovereignty isn't an all-or-nothing proposition. It's
|
||||
4. **Build community infrastructure**: Partner with similar organizations to share resources
|
||||
5. **Center sovereignty in planning**: Make digital autonomy a strategic priority
|
||||
|
||||
The Civil Society Technology Foundation's Sovereign Cloud project provides a reference implementation for organizations seeking to regain digital sovereignty. It demonstrates that practical steps toward greater independence are possible today, even with limited resources.
|
||||
The Civil Society Technology Foundation's Wild Cloud project provides a reference implementation for organizations seeking to regain digital sovereignty. It demonstrates that practical steps toward greater independence are possible today, even with limited resources.
|
||||
|
||||
## Conclusion
|
||||
|
||||
@@ -1,12 +1,48 @@
|
||||
+++
|
||||
title = 'Contribute'
|
||||
+++
|
||||
---
|
||||
title: Contribute
|
||||
---
|
||||
|
||||
# Help us create a strong and lasting technical foundation for Civil Society.
|
||||
{{< lead >}}
|
||||
Help us create a strong and lasting technical foundation for Civil Society.
|
||||
{{< /lead >}}
|
||||
|
||||
- [Move to open technologies](/learning/getting_started).
|
||||
- Join a project working-group.
|
||||
- Propose a project.
|
||||
- Sponsor a working group
|
||||
- [Join a board](/projects/governance).
|
||||
The Civil Society Technology Foundation is a community-driven organization that relies on the support of individuals and organizations who share our vision of digital sovereignty and independent technology. There are many ways you can contribute to our mission:
|
||||
|
||||
### 1. Financial Contributions
|
||||
|
||||
Your financial support is crucial for sustaining our work and expanding our impact. You can make a one-time donation or set up a recurring contribution to help us build and maintain the infrastructure, tools, and resources needed for civil society organizations to thrive in the digital age.
|
||||
|
||||
Civil Society Technology Foundation is a 501(c)3 non-profit incorporated in Washington state. All contributions are tax-deductible.
|
||||
|
||||
### 2. Volunteer Your Time
|
||||
|
||||
We welcome volunteers who can contribute their skills and expertise to our projects. Whether you're a developer, designer, writer, or educator, your involvement can make a significant difference. Join our community and help us create educational resources, develop software, or organize events.
|
||||
|
||||
### 3. Spread the Word
|
||||
|
||||
Share our mission and resources with your network. Help raise awareness about the importance of digital sovereignty and independent technology for civil society. Follow us on social media, share our content, and engage in discussions about these critical issues.
|
||||
|
||||
### 4. Collaborate with Us
|
||||
|
||||
We are always looking for partnerships with like-minded organizations and individuals. If you have a project or initiative that aligns with our mission, let's explore how we can work together to advance digital sovereignty and empower civil society.
|
||||
|
||||
### 5. Join Our Community
|
||||
|
||||
Engage with us through our community forums, mailing lists, and events. Share your ideas, feedback, and experiences. By participating in our community, you can help shape the future of independent technology for civil society.
|
||||
|
||||
### 6. Stay Informed
|
||||
|
||||
Subscribe to our newsletter and follow our blog to stay updated on our latest projects, resources, and events. Being informed is the first step toward active participation in the movement for digital sovereignty.
|
||||
|
||||
### 7. Advocate for Policy Change
|
||||
|
||||
Engage in advocacy efforts to promote policies that support digital sovereignty and independent technology. Your voice can help influence decision-makers and raise awareness about the importance of these issues.
|
||||
|
||||
### 8. Donate Your Expertise
|
||||
|
||||
If you have specialized knowledge or skills that could benefit our projects, consider donating your expertise. Whether it's legal advice, technical guidance, or strategic planning, your contributions can help us achieve our goals more effectively.
|
||||
|
||||
### 9. Become a Member
|
||||
|
||||
Join the Civil Society Technology Foundation as a member to support our mission and gain access to exclusive resources, events, and networking opportunities. Your membership helps us strengthen the community and advance our work in digital sovereignty.
|
||||
|
||||
|
||||
@@ -1,30 +1,22 @@
|
||||
+++
|
||||
title = 'About the Civil Society Technology Foundation'
|
||||
+++
|
||||
---
|
||||
title: About the Civil Society Technology Foundation
|
||||
cascade:
|
||||
params:
|
||||
heroStyle: background
|
||||
---
|
||||
|
||||
The **Civil Society Technology Foundation (CSTF)** is a community-driven organization dedicated to empowering individuals and civil society organizations to reclaim digital sovereignty through open-source tools and self-hosted infrastructure.
|
||||
|
||||
## Our Mission
|
||||
|
||||
We believe that independent, community-controlled technology is essential for a vibrant civil society in the digital age. As digital systems increasingly mediate civic participation, it's vital that these systems remain under the control of the communities they serve, rather than consolidated in the hands of governments or corporations.
|
||||
|
||||
The Civil Society Technology Foundation works to achieve this vision through:
|
||||
|
||||
- **Creating Educational Resources** that build technical literacy and sovereignty awareness
|
||||
- **Developing Reference Implementations** like the Sovereign Cloud for self-hosted infrastructure
|
||||
- **Building Community** around sovereign technology practices and principles
|
||||
- **Advancing Open Standards** that enable interoperability without centralized control
|
||||
- **Supporting Civil Society Organizations** in their journey toward digital independence
|
||||
|
||||
## Who We Are
|
||||
|
||||
- [Charter](/foundation/charter) - The comprehensive founding document for the organization, including structure, governance, and strategic focus areas
|
||||
- [Mission Statement](/foundation/mission_statement) - Our concise mission and approach to digital sovereignty
|
||||
- [Core Principles](/foundation/core_principles) - Detailed explanations of our 11 guiding principles with practical implications
|
||||
{{< article link="/foundation/charter/" >}}
|
||||
{{< article link="/foundation/mission-statement/" >}}
|
||||
{{< article link="/foundation/core-principles/" >}}
|
||||
{{< article link="/foundation/position-statements/" >}}
|
||||
{{< article link="/projects/governance/" >}}
|
||||
|
||||
## What We Believe
|
||||
|
||||
- [The Importance of Independent Technology](/foundation/independent-technology) - Cornerstone essay on why independent technology matters for civil society
|
||||
- [Why Digital Sovereignty Matters](/foundation/why_digital_sovereignty_matters) - Accessible primer on digital sovereignty and its importance
|
||||
- [Arguments Against Centralization](/foundation/arguments_against_centralization) - Comprehensive resource categorizing various arguments against digital centralization
|
||||
- [Position Statements](/foundation/position_statements) - Our formal positions on key issues affecting digital sovereignty
|
||||
{{< article link="/articles/independent-technology/" >}}
|
||||
{{< article link="/articles/why-digital-sovereignty-matters/" >}}
|
||||
{{< article link="/articles/arguments-against-centralization/" >}}
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Charter of Civil Society Technology Foundation'
|
||||
+++
|
||||
---
|
||||
title: Charter of the Civil Society Technology Foundation
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = 'Core Principles'
|
||||
+++
|
||||
|
||||
---
|
||||
title: Core Principles
|
||||
date: 2025-07-06
|
||||
---
|
||||
The Civil Society Technology Foundation operates according to the following core principles that guide all our work, partnerships, and initiatives.
|
||||
|
||||
## 1. Sovereignty by Design
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Mission Statement'
|
||||
+++
|
||||
---
|
||||
title: Mission Statement
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
The Civil Society Technology Foundation (CSTF) empowers individuals and communities to reclaim digital sovereignty through the development and dissemination of open-source, self-hosted technologies.
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Position Statements'
|
||||
+++
|
||||
---
|
||||
title: Position Statements
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
The Civil Society Technology Foundation (CSTF) holds the following positions regarding technology, digital rights, and civil society. These statements represent our core beliefs and guide our work.
|
||||
|
||||
|
||||
164
content/gramsci.md
Normal file
164
content/gramsci.md
Normal file
@@ -0,0 +1,164 @@
|
||||
Perfect — let’s build a simple battle plan (Gramsci-style) for what CivilSociety.dev — or any similar project — could follow to challenge hegemony and build real digital autonomy.
|
||||
|
||||
Here’s the flow:
|
||||
|
||||
|
||||
---
|
||||
|
||||
Battle Plan: Winning the War of Position for Digital Civil Society
|
||||
|
||||
Phase 1: Build Independent Infrastructure
|
||||
|
||||
Launch sovereign services (email, cloud, chat, web hosting) that working-class organizations can use without Big Tech.
|
||||
|
||||
Focus on ease of use and collective ownership (community clouds, co-ops, unions).
|
||||
|
||||
|
||||
Key goal: Create real-world alternatives that people can rely on.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 2: Popular Education
|
||||
|
||||
Teach not just how to use tech, but why digital sovereignty matters.
|
||||
|
||||
Build guides, workshops, videos, and political storytelling that connect tech freedom to everyday life struggles (housing, labor, climate, democracy).
|
||||
|
||||
|
||||
Key goal: Grow thousands of organic intellectuals inside civil society.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 3: Culture Shift
|
||||
|
||||
Create a new "common sense" about tech:
|
||||
|
||||
"We can run our own systems."
|
||||
|
||||
"Freedom is practical, not utopian."
|
||||
|
||||
"Big Tech dependence is a political trap."
|
||||
|
||||
|
||||
Use memes, stories, community campaigns to popularize.
|
||||
|
||||
|
||||
Key goal: Make sovereignty feel normal, not fringe.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 4: Strategic Alliances
|
||||
|
||||
Partner with unions, mutual aid groups, cooperatives, indigenous communities to embed sovereign tech into broader struggles for dignity and justice.
|
||||
|
||||
Wild Cloud becomes the digital backbone of working-class and social movements.
|
||||
|
||||
|
||||
Key goal: Tie tech sovereignty directly to the survival and power of civil society.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Final Objective:
|
||||
|
||||
> Civil society owns its own communication, storage, learning, and organizing tools — breaking the 1%'s hegemony over the digital world.
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
Would you like me to also turn this into a quick visual diagram (like a simple flowchart or map) so it’s super easy to share or present?
|
||||
It could look really clean if you're planning to post, pitch, or organize around it!
|
||||
|
||||
---
|
||||
|
||||
Good — let’s rate how CivilSociety.dev is doing on the Gramscian battle plan we just built.
|
||||
|
||||
I’ll go phase by phase, with a simple scale:
|
||||
Excellent / Good / Needs Growth / Missing
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 1: Build Independent Infrastructure
|
||||
|
||||
> Rating: Excellent
|
||||
|
||||
|
||||
|
||||
Wild Cloud is real, working infrastructure.
|
||||
|
||||
They're offering services like email, cloud storage, chat, hosting, and more — away from Big Tech.
|
||||
|
||||
Clear focus on self-hosting and community control.
|
||||
|
||||
|
||||
Comment:
|
||||
They've nailed the first step — they’re not just talking, they’re building.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 2: Popular Education
|
||||
|
||||
> Rating: Good
|
||||
|
||||
|
||||
|
||||
The Learning section is strong: it explains not just the technical but also the political reasons for sovereignty.
|
||||
|
||||
It’s accessible but could be pushed further into mass popular education — for example, shorter videos, memes, hands-on toolkits, or alliances with schools/unions.
|
||||
|
||||
|
||||
Comment:
|
||||
Good foundation — needs scaling up to reach beyond tech-savvy audiences.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 3: Culture Shift
|
||||
|
||||
> Rating: Needs Growth
|
||||
|
||||
|
||||
|
||||
They challenge Big Tech’s common sense implicitly through projects and writing.
|
||||
|
||||
But they're not (yet) visibly changing broader public attitudes or launching mass storytelling campaigns.
|
||||
|
||||
No evidence yet of heavy cultural production (memes, viral media, mass campaigns, popular slogans).
|
||||
|
||||
|
||||
Comment:
|
||||
This is their big opportunity: to widen the cultural battle and make digital sovereignty part of everyday imagination.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Phase 4: Strategic Alliances
|
||||
|
||||
> Rating: Needs Growth
|
||||
|
||||
|
||||
|
||||
So far, the focus seems internal: building tools, education, and philosophy.
|
||||
|
||||
No clear, public partnerships yet with unions, housing co-ops, indigenous groups, or grassroots movements that desperately need digital independence.
|
||||
|
||||
|
||||
Comment:
|
||||
Strategic alliances with civil society movements would supercharge their impact — this is a crucial next step.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Overall Rating:
|
||||
|
||||
Overall:
|
||||
|
||||
> CivilSociety.dev is very strong at building and explaining alternatives — now it needs to scale up cultural influence and strategic partnerships to fully realize a Gramscian digital movement.
|
||||
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
title: "Learning"
|
||||
---
|
||||
|
||||
Resources for building technical skills and understanding digital sovereignty.
|
||||
@@ -1,9 +0,0 @@
|
||||
+++
|
||||
title = 'Getting Started'
|
||||
+++
|
||||
|
||||
The Soverign Cloud project is in active development.
|
||||
|
||||
```bash
|
||||
https://github.com/payneio/sovereign-cloud.git
|
||||
```
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Git: Distributed Version Control for Digital Independence'
|
||||
+++
|
||||
---
|
||||
title: "Git: Distributed Version Control for Digital Independence"
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'The Internet: Infrastructure for Civil Society'
|
||||
+++
|
||||
---
|
||||
title: "The Internet: Infrastructure for Civil Society"
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -256,7 +257,7 @@ The Civil Society Technology Foundation works toward an Internet that serves civ
|
||||
|
||||
### 1. Self-Hosted Infrastructure
|
||||
|
||||
Our Sovereign Cloud project demonstrates how civil society organizations can regain control over their digital infrastructure by running their own services on hardware they control. This approach:
|
||||
Our Wild Cloud project demonstrates how civil society organizations can regain control over their digital infrastructure by running their own services on hardware they control. This approach:
|
||||
|
||||
- Reduces dependency on commercial platforms
|
||||
- Enhances privacy and security
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Language Models: Understanding AI in the Context of Civil Society'
|
||||
+++
|
||||
---
|
||||
title: "Language Models: Understanding AI in the Context of Civil Society"
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Linux: The Operating System for Digital Sovereignty'
|
||||
+++
|
||||
---
|
||||
title: "Linux: The Operating System for Digital Sovereignty"
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -128,7 +129,7 @@ Linux comes in many "distributions" (or "distros")—different versions packaged
|
||||
- **Armbian**: For single-board computers and low-cost infrastructure
|
||||
- **OpenWrt**: For network devices and community networks
|
||||
|
||||
The Civil Society Technology Foundation's Sovereign Cloud project uses lightweight Linux distributions as the foundation for self-hosted infrastructure, allowing organizations to run essential services on hardware they control.
|
||||
The Civil Society Technology Foundation's Wild Cloud project uses lightweight Linux distributions as the foundation for self-hosted infrastructure, allowing organizations to run essential services on hardware they control.
|
||||
|
||||
## Common Myths About Linux
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Open Source: The Foundation of Digital Freedom'
|
||||
+++
|
||||
---
|
||||
title: "Open Source: The Foundation of Digital Freedom"
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -108,9 +109,9 @@ Despite its importance, several misconceptions persist about open source:
|
||||
|
||||
**Reality**: Open source licenses give you the right to modify your own copy, not to force changes on others. This means you maintain control over your specific implementation while benefiting from the freedom to adapt it as needed.
|
||||
|
||||
## Open Source in Practice: The Sovereign Cloud
|
||||
## Open Source in Practice: Wild Cloud
|
||||
|
||||
The Civil Society Technology Foundation's Sovereign Cloud project demonstrates open source principles in action. This reference implementation for self-hosted infrastructure:
|
||||
The Civil Society Technology Foundation's Wild Cloud project demonstrates open source principles in action. This reference implementation for self-hosted infrastructure:
|
||||
|
||||
- Uses only open source components that can be freely inspected and modified
|
||||
- Enables organizations to maintain full control over their infrastructure
|
||||
@@ -118,7 +119,7 @@ The Civil Society Technology Foundation's Sovereign Cloud project demonstrates o
|
||||
- Provides adaptable solutions that respect the diversity of civil society needs
|
||||
- Builds capacity for technological self-determination rather than dependency
|
||||
|
||||
By combining carefully selected open source tools into a cohesive system, the Sovereign Cloud shows how open source can address practical needs while embodying the values of digital freedom.
|
||||
By combining carefully selected open source tools into a cohesive system, Wild Cloud shows how open source can address practical needs while embodying the values of digital freedom.
|
||||
|
||||
## Practical Steps Toward Open Source Adoption
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Software Development: Building Digital Infrastructure for Civil Society'
|
||||
+++
|
||||
---
|
||||
title: "Software Development: Building Digital Infrastructure for Civil Society"
|
||||
date: 202-01-15
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -1 +1,10 @@
|
||||
# Working groups.
|
||||
---
|
||||
title: "Projects"
|
||||
cascade:
|
||||
showReadingTime: false
|
||||
showWordCount: false
|
||||
showDate: false
|
||||
params:
|
||||
heroStyle: background
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
+++
|
||||
title = 'Education'
|
||||
+++
|
||||
---
|
||||
title: 'Education'
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
Curating and developing education resources.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = 'Governance'
|
||||
weight = 10
|
||||
+++
|
||||
---
|
||||
title: 'Governance'
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
Transparency is paramount.
|
||||
|
||||
|
||||
@@ -1,75 +0,0 @@
|
||||
+++
|
||||
title = 'Sovereign Cloud Tech Notes'
|
||||
+++
|
||||
|
||||
The Sovereign Cloud is under active development.
|
||||
|
||||
## Core Components
|
||||
|
||||
The Sovereign Cloud is being built on a lightweight Kubernetes distribution (K3s) that provides the foundation for deploying and managing containerized applications. This architecture offers several key advantages:
|
||||
|
||||
- **K3s**: A certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, edge, IoT, or appliance settings
|
||||
- Visibility layer
|
||||
- **MetalLB**: Assigns network IPs to services, allowing clean exposure of applications within your LAN
|
||||
- **Traefik**: Ingress controller that handles subdomain routing and TLS termination within your cloud
|
||||
- **ExternalDNS**: Automatically registers cloud resources as subdomains with your external DNS provider (currently supporing CloudFlare)
|
||||
- **CoreDNS**: Provides split-horizon DNS for both public and private services
|
||||
- **cert-manager**: Automatically manages TLS certificates via Let's Encrypt and internal CA
|
||||
- Volatility layer
|
||||
- **Vanilla Kubernetes**: Kubernetes manifests, configured with kustomize, applied with kubectl.
|
||||
- Persistece layer
|
||||
- **Longhorn**: Cluster-wide block storage.
|
||||
- **PostgreSQL/MariaDB**: Databases for applications requiring persistent storage
|
||||
|
||||
## Security Features
|
||||
|
||||
The Sovereign Cloud incorporates several security features:
|
||||
|
||||
- **Automatic TLS certificates**: All services use HTTPS with valid certificates
|
||||
- **Network isolation**: Clear separation between public-facing and internal-only services
|
||||
- **Split-horizon DNS**: Different resolution for internal vs. external access
|
||||
- **Certificate-based authentication**: For administrative access
|
||||
- **Regular updates**: Streamlined process for keeping components secure
|
||||
- **Backup system**: Automated backups with encrypted off-site options
|
||||
|
||||
## Management Interfaces
|
||||
|
||||
The Sovereign Cloud includes a web-based dashboard for monitoring and managing your infrastructure:
|
||||
|
||||
- **Soveign Cloud Home**: A web application that is the central management interface for your cloud
|
||||
- **Kubernetes Dashboard**: Web UI for full visibility of your Kubernetes cluster
|
||||
- **Application-specific interfaces**: Each application provides its own management UI
|
||||
|
||||
## Why K3s?
|
||||
|
||||
K3s offers a lightweight, simplified version of Kubernetes without sacrificing core functionality. It’s designed to be easy to install, easy to manage, and efficient enough to run in places where full Kubernetes would be too heavy — like edge devices, small clusters, or developer environments.
|
||||
|
||||
By stripping away unnecessary extras and bundling everything into a single binary, K3s dramatically reduces the complexity and resource demands of a Kubernetes installation. This makes it much faster to get started and much easier to operate over time.
|
||||
|
||||
For teams who want the power of Kubernetes without all the operational overhead, K3s provides a practical, open-source alternative that stays true to Kubernetes principles while removing a lot of the friction.
|
||||
|
||||
## Application Packaging
|
||||
|
||||
For the Sovereign Cloud project, we chose a simple, transparent approach to application packaging based on two principles: reproducibility and openness.
|
||||
|
||||
Each application is defined by a maintained Dockerfile. This ensures that anyone can rebuild the application from source without relying on external or proprietary tools. Keeping Dockerfiles clear and self-contained supports long-term sustainability and prevents hidden dependencies.
|
||||
|
||||
For deployment, we use plain Kubernetes manifests managed through Kustomize. Kustomize allows us to build a clean, declarative base for each application, then apply environment-specific overlays without introducing unnecessary complexity. It keeps the configuration understandable and versioned in Git, supporting collaboration and peer review across organizations.
|
||||
|
||||
By avoiding heavier tooling, we prioritize clarity and control over pseudo-convenience. Our goal is for anyone — technical teams within civil society or otherwise — to be able to read, audit, and reproduce the full deployment process without needing specialized knowledge or access to private infrastructure.
|
||||
|
||||
This approach keeps the system open, portable, and maintainable over the long term, aligning with Sovereign Cloud's goal of building infrastructure _for civil society, by civil society_.
|
||||
|
||||
### Why Not Helm?
|
||||
|
||||
While Helm is popular for managing Kubernetes applications, it introduces unnecessary complexity for many real-world deployments. Helm doesn't eliminate the need for careful configuration — it simply shifts it. Instead of managing plain YAML files directly, you now manage Helm charts, templates, and values files. This can actually make it harder to understand exactly what is being deployed.
|
||||
|
||||
Helm also creates hidden state inside your cluster, making upgrades and rollbacks dependent on Helm itself rather than on clear, versioned files in Git. If something goes wrong, you're often troubleshooting Helm releases and secrets instead of just fixing a Kubernetes manifest.
|
||||
|
||||
We value simplicity, transparency, and full control over infrastructure. Using plain YAML, lightweight templates, and Git provides a more reliable and auditable system. With a small amount of scripting, the same flexibility Helm promises can be achieved without introducing another layer of abstraction.
|
||||
|
||||
### Why Kustomize?
|
||||
|
||||
Kustomize provides a simple, powerful way to manage Kubernetes configurations without introducing hidden complexity. It works directly with plain YAML files — letting you layer changes cleanly and predictably.
|
||||
|
||||
Unlike templating systems that mix logic into your configuration, Kustomize keeps everything declarative. You start with a base set of manifests and apply structured overlays to customize them, without ever touching the originals. This approach keeps deployments transparent, easy to audit, and easy to version in Git.
|
||||
@@ -1,14 +1,15 @@
|
||||
+++
|
||||
title = 'Sovereign Cloud'
|
||||
+++
|
||||
---
|
||||
title: Wild Cloud
|
||||
date: 2025-07-06
|
||||
---
|
||||
|
||||
The Sovereign Cloud is the Civil Society Technology Foundation's reference implementation for personal and organizational self-hosted infrastructure. This project empowers individuals and organizations to run their own digital services without dependency on centralized corporate platforms.
|
||||
Wild Cloud is the Civil Society Technology Foundation's reference implementation for personal and organizational self-hosted infrastructure. This project empowers individuals and organizations to run their own digital services without dependency on centralized corporate platforms.
|
||||
|
||||
## Overview
|
||||
|
||||
The Sovereign Cloud provides a complete, accessible solution for operating essential digital services on infrastructure you control. It combines carefully selected open-source components into a cohesive system that balances security, usability, and maintainability.
|
||||
Wild Cloud provides a complete, accessible solution for operating essential digital services on infrastructure you control. It combines carefully selected open-source components into a cohesive system that balances security, usability, and maintainability.
|
||||
|
||||
By deploying the Sovereign Cloud, organizations can:
|
||||
By deploying Wild Cloud, organizations can:
|
||||
|
||||
- Host their own email, calendar, file storage, website, and collaboration tools
|
||||
- Maintain full control over their data and communications
|
||||
@@ -20,7 +21,7 @@ The Soverign Cloud project aims to start you with a simple self-hosted cloud sol
|
||||
|
||||
### Architecture
|
||||
|
||||
The Soverign cloud allows individuals and organizations (cloud admins) to install and manage a full Kubernetes cluster (using K3s) made of one or multiple computers on their own premises. Kubernetes manages much of the complexity of maintaining the health of your cloud and managing the applications deployed in it.
|
||||
Wild Cloud allows individuals and organizations (cloud admins) to install and manage a full Kubernetes cluster (using K3s) made of one or multiple computers on their own premises. Kubernetes manages much of the complexity of maintaining the health of your cloud and managing the applications deployed in it.
|
||||
|
||||
### Applications
|
||||
|
||||
@@ -37,13 +38,14 @@ Admins can deploy various applications into their cloud, including:
|
||||
|
||||
## Getting Started
|
||||
|
||||
The Soverign Cloud project is currently being built out. When v1 is ready, it will be freely available on GitHub. Instructions for getting started with your cloud will be included in the repository after it is cloned.
|
||||
The Wild Cloud project is currently being built out on GitHub.
|
||||
|
||||
{{< github repo="civil-society-dev/wild-cloud" showThumbnail=true >}}
|
||||
|
||||
See our [Tech Notes](tech-notes) page for more information on current development.
|
||||
|
||||
## Community Support
|
||||
|
||||
The Sovereign Cloud is supported by a community of practitioners who share knowledge, troubleshooting tips, and enhancements. The Civil Society Technology Foundation provides:
|
||||
Wild Cloud is supported by a community of practitioners who share knowledge, troubleshooting tips, and enhancements. The Civil Society Technology Foundation provides:
|
||||
|
||||
- Documentation and tutorials
|
||||
- Installation guides for different environments
|
||||
@@ -53,7 +55,7 @@ The Sovereign Cloud is supported by a community of practitioners who share knowl
|
||||
|
||||
## Philosophy
|
||||
|
||||
The Sovereign Cloud embodies the Civil Society Technology Foundation's core principles:
|
||||
Wild Cloud embodies the Civil Society Technology Foundation's core principles:
|
||||
|
||||
- **Sovereignty by Design**: Users control their data and computing environment
|
||||
- **Open Source, Always**: All components are free to use, study, modify, and share
|
||||
Submodule themes/blowfish updated: 0d03681d20...2f12b8d0d9
Reference in New Issue
Block a user