# Marc's thoughts on method: -Take a look at Federation vs Wiki. Which style is better plain text or markdown. -Who is the audience? -Can we create a pattern, a template for all of these pages? -What role can / should wikipedia play? Again, who is the audience?
Can we sketch a curriculum for medical school for wiki doctors? An MD might learn biology, anatomy and ethics. We might teach networking, wiki and federation. Graduates could solve new user problems but not host a wiki farm or run a hospital for that matter.
digraph { rankdir=LR node [style=filled fillcolor=red] "FedWiki College" node [style=filled fillcolor=lightblue] Onboarding Wiki Federation Networking node [style=filled fillcolor=yellow] "FedWiki College" -> Onboarding "FedWiki College" -> Networking "FedWiki College" -> Wiki "FedWiki College" -> Federation Onboarding -> Origins Onboarding -> Reader Onboarding -> Writer Onboarding -> CoThink Onboarding -> Etc Wiki -> Medium Wiki -> Plugins Wiki -> Editing Wiki -> Workflow Networking -> Clients Networking -> Servers Networking -> Networks Networking -> Payloads Federation -> Hosting Federation -> Indexing Federation -> Style Federation -> Migration }
# Onboarding New FedWiki Users Origins Stories Reader Writer CoThink BookWriter Educator Community ActivistOrganizer PluginCreator FedWiki TeacherGuideMentor SubdomainHost
# Wiki
Medium: page, title, slug, story, item, types, journal, actions and revisions.
Plugins: paragraphs, images, markdown, html, maps, diagrams, data and visualizations.
Editing: login, keystrokes, markup, about pages, drag items, drop zones, refresh, wiki mode.
Workflow: lineup, search, neighborhood, hamburger menu, sitemaps, twins, refresh.
Hosting: Subdomains, rosters, pods, identities, charters, habits, meetups, backchannels
Indexing: Advanced search, federation activity, site indexes, full text search.
Style: Hypertext, title case, refactoring, link words, pronouns, simplicity
Migration: Export, import, shell tools, dns updates, compatibilities, configuration, plugmatic
Clients: browsers, location bar, urls, caches, cookies, sessions, cross-origin.
Servers: protocols, app servers, reverse proxy, domain names, wildcards, upgrades, login, ssh, virtual machines.
Network: addresses, dhcp, sockets, ping, bandwidth, routing, carriers, wifi, security.
Payloads: rest, json, status codes, mime-type, unicode, latency, throughput.
.
Wiki's imagined actors involved in the federation as a tool to develop uses cases in the original design.