Initial commit of website source

404.html

@@ -0,0 +1,25 @@
+---
+permalink: /404.html
+layout: default
+---
+
+<style type="text/css" media="screen">
+  .container {
+    margin: 10px auto;
+    max-width: 600px;
+    text-align: center;
+  }
+  h1 {
+    margin: 30px 0;
+    font-size: 4em;
+    line-height: 1;
+    letter-spacing: -1px;
+  }
+</style>
+
+<div class="container">
+  <h1>404</h1>
+
+  <p><strong>Page not found :(</strong></p>
+  <p>The requested page could not be found.</p>
+</div>

Gemfile

@@ -0,0 +1,33 @@
+source "https://rubygems.org"
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+gem "jekyll", "~> 4.3.2"
+# This is the default theme for new Jekyll sites. You may change this to anything you like.
+gem "minima", "~> 2.5"
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+# gem "github-pages", group: :jekyll_plugins
+# If you have any plugins, put them here!
+group :jekyll_plugins do
+  gem "jekyll-feed", "~> 0.12"
+end
+
+# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
+# and associated library.
+platforms :mingw, :x64_mingw, :mswin, :jruby do
+  gem "tzinfo", ">= 1", "< 3"
+  gem "tzinfo-data"
+end
+
+# Performance-booster for watching directories on Windows
+gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin]
+
+# Lock `http_parser.rb` gem to `v0.6.x` on JRuby builds since newer versions of the gem
+# do not have a Java counterpart.
+gem "http_parser.rb", "~> 0.6.0", :platforms => [:jruby]

Gemfile.lock

@@ -0,0 +1,86 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.8.1)
+      public_suffix (>= 2.0.2, < 6.0)
+    colorator (1.1.0)
+    concurrent-ruby (1.2.0)
+    em-websocket (0.5.3)
+      eventmachine (>= 0.12.9)
+      http_parser.rb (~> 0)
+    eventmachine (1.2.7)
+    ffi (1.15.5)
+    forwardable-extended (2.6.0)
+    google-protobuf (3.21.12-x86_64-linux)
+    http_parser.rb (0.8.0)
+    i18n (1.12.0)
+      concurrent-ruby (~> 1.0)
+    jekyll (4.3.2)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      em-websocket (~> 0.5)
+      i18n (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
+      jekyll-watch (~> 2.0)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
+      liquid (~> 4.0)
+      mercenary (>= 0.3.6, < 0.5)
+      pathutil (~> 0.9)
+      rouge (>= 3.0, < 5.0)
+      safe_yaml (~> 1.0)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
+    jekyll-feed (0.17.0)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-sass-converter (3.0.0)
+      sass-embedded (~> 1.54)
+    jekyll-seo-tag (2.8.0)
+      jekyll (>= 3.8, < 5.0)
+    jekyll-watch (2.2.1)
+      listen (~> 3.0)
+    kramdown (2.4.0)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.4)
+    listen (3.8.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    mercenary (0.4.0)
+    minima (2.5.1)
+      jekyll (>= 3.5, < 5.0)
+      jekyll-feed (~> 0.9)
+      jekyll-seo-tag (~> 2.1)
+    pathutil (0.16.2)
+      forwardable-extended (~> 2.6)
+    public_suffix (5.0.1)
+    rake (13.0.6)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.10.1)
+      ffi (~> 1.0)
+    rexml (3.2.5)
+    rouge (4.0.1)
+    safe_yaml (1.0.5)
+    sass-embedded (1.57.1)
+      google-protobuf (~> 3.21)
+      rake (>= 10.0.0)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    unicode-display_width (2.4.2)
+    webrick (1.8.1)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  http_parser.rb (~> 0.6.0)
+  jekyll (~> 4.3.2)
+  jekyll-feed (~> 0.12)
+  minima (~> 2.5)
+  tzinfo (>= 1, < 3)
+  tzinfo-data
+  wdm (~> 0.1.1)
+
+BUNDLED WITH
+   2.3.19

_config.yml

@@ -0,0 +1,51 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely edit after that. If you find
+# yourself editing this file very often, consider using Jekyll's data files
+# feature for the data you need to update frequently.
+#
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
+#
+# If you need help with YAML syntax, here are some quick references for you:
+# https://learn-the-web.algonquindesign.ca/topics/markdown-yaml-cheat-sheet/#yaml
+# https://learnxinyminutes.com/docs/yaml/
+#
+# Site settings
+# These are used to personalize your new site. If you look in the HTML files,
+# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
+# You can create any custom variable you would like, and they will be accessible
+# in the templates via {{ site.myvariable }}.
+
+title: "Modpol"
+email: medlab@colorado.edu
+description: "Turn social platforms into governable spaces"
+baseurl: "" # the subpath of your site, e.g. /blog
+url: "https://modpol.net" # the base hostname & protocol for your site, e.g. http://example.com
+twitter_username: medlabboulder
+
+# Build settings
+theme: minima
+plugins:
+  - jekyll-feed
+
+# Exclude from processing.
+# The following items will not be processed, by default.
+# Any item listed under the `exclude:` key here will be automatically added to
+# the internal "default list".
+#
+# Excluded items can be processed by explicitly listing the directories or
+# their entries' file path in the `include:` list.
+#
+# exclude:
+#   - .sass-cache/
+#   - .jekyll-cache/
+#   - gemfiles/
+#   - Gemfile
+#   - Gemfile.lock
+#   - node_modules/
+#   - vendor/bundle/
+#   - vendor/cache/
+#   - vendor/gems/
+#   - vendor/ruby/

demo.md

@@ -0,0 +1,35 @@
+---
+title: Demo
+permalink: /demo/
+layout: page
+---
+
+## Try the demo server
+
+We have a demo server available where you can try Modpol for Minetest in a multiplayer environment. To conserve resources, it is only online by appointment. Please [contact MEDLab](mailto:medlab@colorado.edu) to schedule an appointment.
+
+To play, follow these instructions. If you have problems, let us know by email.
+
+### Download Minetest
+
+Get the latest version at [Minetest.net](https://www.minetest.net/).
+
+### Join the server
+
+In Minetest, choose the "Join Game" tab. There, enter the following:
+
+* Address: `play.modpol.net`
+* Port: `30000`
+* Name: Choose a name
+* Password: Choose a password
+
+Then click `Connect`. If it is your first time logging in, you will need to type your password again.
+
+### Get comfortable
+
+* To change how your character looks, type `i` to open the inventory menu and choose the `Edit Skin` tab on top.
+* Learn the basic controls and much more at the [Minetest wiki](https://wiki.minetest.net/Getting_Started#Basic_Controls). (Hint: If you've played Minecraft before, the controls are pretty much the same!)
+
+### Enter Modpol
+
+To start interacting with Modpol in the game, type `/mp [Enter]`.

docs.md

@@ -0,0 +1,24 @@
+---
+title: Docs
+permalink: /docs/
+layout: page
+---
+
+## Basics
+
+Modpol is built around groups called *orgs*. At the base is an org with all users in it, called `Root` by default. *Modules* enable people to do things within orgs, such as decide on membership, grant powers to the org, and much more. To get started in Minetest:
+
+* Type the command `/mp`
+* Select the org `Root`
+* Choose one of its modules to make new orgs and craft their behavior
+
+Modules can be nested in each other, so one module can rely on another module to accomplish a process. Users might use a module to unilaterally carry out actions in the game, or the module might require a group decision to do so. Users can also change the modules available to users of a given org. There are currently two ways of doing this:
+
+* Admins can remove modules from the list of modules loaded in `modpol_core/api.lua` and `modpol_minetest/api.lua`. This will make those modules no longer available to any user.
+* Players can change the modules available in a given org from within the program using the `Change modules` module. Removed modules can be re-added in any org by using `Change modules` again.
+
+Modpol should give you the ability to do whatever kind of politics you want with your modules. If there is something you would like to do that is not available, [develop a module for it](https://gitlab.com/medlabboulder/modpol/-/wikis/Module-Writing-Guide) (or ask us for help!).
+
+## Developers
+
+Developer documentation is currently located at the [repo wiki on GitLab](https://gitlab.com/medlabboulder/modpol/-/wikis/home).

index.md

@@ -0,0 +1,33 @@
+---
+layout: page
+permalink: /
+---
+
+    
+## Turn social platforms into governable spaces
+
+![](/assets/empire-modpol.png "empire-modpol")
+
+## Gamers: Form groups, make decisions your way
+
+Modpol enables online communities to design their own governance structures by assembling modules—choosing from existing ones or creating your own.
+
+[Play the Minetest demo server](demo), or download the [Minetest mod at ContentDB](https://content.minetest.net/packages/ntnsndr/modpol/).
+
+## Developers: Adapt our code to your platform
+
+Modpol is written in Lua, and it can be adapted to any platform that uses Lua as an extension language. 
+
+[Explore the code, docs, and wiki at GitLab](https://gitlab.com/medlabboulder/modpol/).
+
+## Visionaries: Shape the future of online governance
+
+Modpol implements a framework called "[modular politics](https://metagov.org/modpol)," a vision for creative, evolutionary systems for online self-governance. It challenges the widespread the tendency for "[implicit feudalism](https://ntnsndr.in/ImplicitFeudalism)," the top-down power structures that are the norm in online spaces. 
+
+[Read more at _Hackernoon_](https://hackernoon.com/modpol-is-a-self-governance-toolkit-for-communities-in-online-worlds).
+
+## Get in touch
+
+Modpol is a project of the [Media Economies Design Lab](https://colorado.edu/lab/medlab) at the University of Colorado Boulder, in collaboration with the [Metagovernance Project](https://metagov.org). 
+
+Find us via [email](mailto:medlab@colorado.edu) or [Matrix](https://app.element.io/#/room/#minetest-modpol:matrix.org).