<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Doikayt Field Guide</sitename>
    <dbname>mediawiki</dbname>
    <base>https://wiki.doikayt.org/index.php/Main_Page</base>
    <generator>MediaWiki 1.46.0</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">DoikaytFieldGuide</namespace>
      <namespace key="5" case="first-letter">DoikaytFieldGuide talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="106" case="first-letter">Form</namespace>
      <namespace key="107" case="first-letter">Form talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Main Page</title>
    <ns>0</ns>
    <id>1</id>
    <revision>
      <id>24</id>
      <parentid>1</parentid>
      <timestamp>2026-07-22T00:41:59Z</timestamp>
      <contributor>
        <username>Admin</username>
        <id>2</id>
      </contributor>
      <comment>qwiki: main-page.md</comment>
      <origin>24</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3038" sha1="arbrqf8qvtgi5lkzchmrzf4q4feujux" xml:space="preserve">&lt;span id="digital-mobilization-field-guide"&gt;&lt;/span&gt;
= Digital Mobilization Field Guide =

A technical field guide to digital products, and services that support the operations of organizations aligned with the pro-labor, pro-human rights, pro-free speech and anti-imperialist agenda of Doikayt Mobilization Labs. [TBD: need link]

&lt;span id="target-audience"&gt;&lt;/span&gt;
== Target Audience ==

&lt;span id="profile"&gt;&lt;/span&gt;
=== Profile ===

You are in the right place if you are a ''technician'' working as IT staff or as a volunteer at a movement-aligned organizations, where you are tasked with:

* identification,
* evaluation,
* configuration,
* customization and
* ongoing maintenance and support of software and hardware that supports your group’s mission.

&lt;span id="proficiency-assumptions"&gt;&lt;/span&gt;
=== Proficiency Assumptions ===

You should be at least at ‘power user’ level, comfortable with:

* config files
* command line directives
* IT operations basics
** Web, Internet, and cloud concepts
** basic security

&lt;span id="unique-challenges"&gt;&lt;/span&gt;
=== Unique Challenges ===

You likely need to deal with constraints that technicians in corporate, government and military settings don’t worry much about:

* shoe-string budgets,
* deplatforming risks, and
* ethical considerations

See [[New Submissions]] for further discussion of how these criteria factor into our structured protocol for recommending new products and services.

&lt;span id="site-organization"&gt;&lt;/span&gt;
== Site Organization ==

Content is organized as a shallow hierarchy, moving from broad generalized domains of organizational concern to operational areas within a domain (and potentially, an intervening sub-area) – all the way down to the level of individual tools (one per page).

* ''Domain →''
** ''Operational Area →''
*** ''Operational Sub-area →''
**** ''Task →''
***** ''Candidate Tool''

See [[Site Organization]] for more details.

&lt;span id="how-to-contribute"&gt;&lt;/span&gt;
== How To Contribute ==

* Request an account from chris@datalackey.com
* [[Project:New Submission|Click here]] to submit a new tool, or click ‘New Submission’ in the sidebar from anywhere on the site

&lt;span id="long-term-vision"&gt;&lt;/span&gt;
== Long Term Vision ==

&lt;span id="wiki---database"&gt;&lt;/span&gt;
=== Wiki -&amp;gt; Database ===

We have formalized the procedure for adding new content to this site so that each entry for a recommended tool has a known structure (schema). We plan to leverage this known structure when we start feeding a database with this site’s content.

&lt;span id="database---tool-for-ai-agent"&gt;&lt;/span&gt;
=== Database -&amp;gt; Tool for AI Agent ===

Longer term we plan to expose our content as a tool that be consumed by AI language models via [https://en.wikipedia.org/wiki/Model_Context_Protocol Model Context Protocol]. The goal is to enable conversations along the lines of: “I am looking for a low (or no) cost tool to streamline the process of submitting my organization’s weekly events to various community calendars.”

[[Category:Meta]]</text>
      <sha1>arbrqf8qvtgi5lkzchmrzf4q4feujux</sha1>
    </revision>
  </page>
</mediawiki>
