wikifying

 wikifying  is the practice of capturing information and ideas on the wiki. E.g. "We need to wikify that FAQ, concept, jargon, or etherpad".

Follow the step by step directions on this page to:
 * Step 1: Create your wiki page.
 * Step 2: Edit your wiki page.
 * Step 3: (optional) add your self to chat-names
 * Step 4: (optional) create a sparkline so there is a picture next your chat-name

Then begin to contribute to the wiki.

Why Join the IndieWeb Wiki
As a community, we eschew email in lieu of real-time chat and documentation of the important points on the wiki to make it easier to search and build information and documentation over time.

When you join the wiki you help our community grow and also provide documentation of your journey. This helps the next person who, like you, wants to control their data in the place that they own.

Each person who joins the wiki has a user page they maintain and build over time. You can shape your page to tell your story. As you get started please consider these examples as you look for ideas.

IndieWeb Examples

 * undefined

How to Join the IndieWeb Wiki
Unlike other sites where you choose a username and password, you only need your domain name to log in to this wiki. It uses indielogin.com to authenticate you. If you have not done so already, set up web sign-in on your domain so you can be authenticated and log in.

In addition to being able to log into the wiki, this web sign-in should also allow you to log into and RSVP to events as well as to use many other IndieWeb building blocks like publishing apps and social readers.

Step One: Create your user page
After logging in, visit your user page. Then click Create. You can choose two templates to add a profile to your page.


 * Minimum Profile
 * Infobox Profile

If you want to edit your page at a later date go to your own user page (or click your domain name at the top right). From there, click Edit.

Minimum Profile
The IndieWeb community uses h-cards to identify people online. This is like a business card for your website.

The smallest h-card includes your name and a link to your website. Your Name

Infobox Profile
If you would like to include a profile box like for example, we have created a template for you.

Go to Infobox person and copy the entire template. Then return to the  tab of your user page (or click   if there isn't already a page. Paste the template onto your user page. Replace/fill out the relevant data you'd like to display. You can use the   button at the bottom of the page to preview how things will look before you save them. Once things look the way you'd like them to save your changes. Remember you can always make changes later if you'd like to.

Step Two: Edit Your Wiki page
You can shape your wiki page any way you like. There are some common elements many community members include:

Write down your itches
Next, add an itches section where you capture what you want to work on for your own site, personal online digital presence, and personal digital device usage (e.g. even when offline) in general. E.g.

Itches

 * Add a more extensive h-card on my site
 * Figure out a URL design for my posts
 * Start posting notes manually at permalinks
 * Try checking my site in indiewebify.me
 * Check out IndieMark for additional ideas of things to add to my site

When you start collecting lots of itches, you may want to start prioritizing them, especially by what you're currently working on. Start a "Working on" section for that:

Working On

 * the next thing I'm working on for my site
 * the next next thing I'm working on getting working on my site
 * ... etc.

Focus
As this is the IndieWeb, and this is about your IndieWeb user page, it should be about answering this question, continuously:
 * What is the next thing you want to get working on your personal site?

This means for example that the following are better left out and pursued elsewhere - like on your own site!
 * A personal to do list (of other non-personal-site things) - your IndieWeb user page is about work on your personal site.
 * Asking others to do work for you. Note: requests for help with IndieWeb specific itches/projects are ok, but address them to everyone, not just individuals. This is about what you want to work on - not asking others to do work.
 * Trying to get silos to do things, in general or with specific accounts - instead, document individual silo issues on the specific silo wiki pages, and follow-up there. Your itches should be about your personal site, not silos.

Additional Templates
These pre-defined wiki templates that can be added to a user page:
 * Infobox template: Template:Infobox_person
 * Twitter template: Template:twitter-link
 * Facebook template: Template:facebook-link
 * Mastodon template: Template:mastodon-link

Step Three: Add a chat name
Optionally add yourself to chat-names. This will show your photo by your name in the chat logs and link your name to your website. It will also allow our friendly chat bot Loqi to answer "who is [username]" with information from your wiki user page.

To add a chat name visit chat-names and use the provided template.

Step Four: Add a sparkline
The IndieWeb wiki allows sparklines, a small avatar that contains your photo and your name linked to your user page. This means people can add a text snippet like to any page to display your name linked to your user page with an option avatar displayed next to it.


 * Example:  entered into a wiki page will display:.

Visit the template to add a sparkline.

Why Contribute to the IndieWeb Wiki
Wikifying both in general, and particular subjects, notes, or documents, helps grow the searchable & discoverable commons of the IndieWeb community.

Is it IndieWeb related? Great, add it to the wiki. Not sure? See examples of what (not) to add:
 * FAQ: is this relevant to the IndieWeb wiki?

Finding pages that need improvement
If you're looking for a way to help improve the wiki, consider looking for old pages and help clean them up and improve them! The sections below describe ways you can improve pages, such as fixing typos, ensuring pages have some sort of IndieWeb relevance, adding citations, or even deleting a page.

Here are some ideas for how to find pages that are likely to need improvement.


 * Pages with the Fewest Revisions - These are pages likely to have been defined in chat and need to be expanded. (You can ignore the "redirect pages" in this list.)
 * Short Pages - These pages have very little text. Sometimes that's because a redirect was created incorrectly, or sometimes the page was defined in chat and never expanded.
 * Oldest Pages - This is a list of pages sorted by the oldest date since the last edit. They are likely to have stale information, or may not meet our current standards for wiki pages if they were created many years ago.
 * Lonely Pages - These pages are not linked to by any other page. If the page is relatively complete itself, then consider adding links to it from relevant pages it may link to.

Incremental Wikifying
There's lots of incremental wikifying to help with.
 * fixing typos
 * expanding (and/or simplifying) a definition to include the IndieWeb relevance of the term
 * adding IndieWeb Examples - if you find a page for a technology you support on your site, or a project you use on your site, add yourself to the "IndieWeb Examples" for that page
 * add issues and questions (for FAQs)
 * collect questions/answers from chat and add them to the appropriate wiki page
 * organize the content of a growing page into sections per expand a page

See:
 * expand a page for many more specific suggestions for incremental wikifying.
 * to-do for specific wiki pages that need incremental improvements!

In general, small incremental edits help with understandable diffs or differences that make wiki page updates easier for the community to review and help with corrections when necessary.

Add Citations
Whenever you see Loqi (or anyone frankly) share or post a link in chat to something relevant to the indieweb, please help out by adding those as citations/examples to the wiki, and especially if they're photos, add them to event page(s).

Format citations
Here's how to "text format" citations to add them, from a minimum, to incrementally doing more work (or improving existing citations!)
 * link
 * seriously, it's ok to just add a link, that's helpful!


 * YYYY-MM-DD link
 * adding the article's publication date helps a lot by placing the link in a temporal context


 * YYYY-MM-DD [link article-name]
 * even better, go get the article name which is likely more readable/understandable/searchable/discoverable than the link. Is it a tweet link or lacking a name? Pick a summary sentence instead.


 * YYYY-MM-DD author : [link article-name]
 * even better, add the author to help provide authority or at least the context of who-from


 * YYYY-MM-DD : [link article-name]
 * even better, if the author is a participant in the indieweb community use the –  template for their shortname / chat nickname to link their name, perhaps even provide their icon automatically

Optionally: YYYY-MM-DD [link article-name] "key relevant sentence(s)!"
 * Add a  inline at the end of the citation, with key relevant sentence(s) copy/pasted/quoted from the link, like this:

These are all super-easy (nearly completely) plain-text ways of just pasting/typing the information into the wiki. (Nearly) No code or markup to learn or figure out or debug. Don't worry about not being perfect, others can help with tweaking fixing things.

Keeping wiki pages mostly plain-text-like makes them easier for others to edit and improve as well!

The important thing is to just take the step of adding the information.

If you like or are familiar MediaWiki templates, you can also use:
 * Template:citation

Where to add a citation
If you don't know where in a page to put a citation, add it to the See Also section at the end. wikipagename << YYYY-MM-DD [link article-name] etc.
 * You can even do this from chat by using the << trick like this:

If the citation is criticism, add/move it to the Criticism section of the article.

These are all incremental steps. None are required. All are something you can help with.

Every incremental step you can help with above helps the wiki.

Even just one incremental improvement is helpful!

New pages
Please read relevant to the IndieWeb wiki before creating new pages.

Create new wiki pages for:
 * new concepts or terms being discussed, e.g. in chat
 * start with and a short definition that includes its indieweb relevance! (see next section)
 * they should be directly indieweb-related in some way (this isn't Wikipedia )
 * Archive pages for Etherpad notes from IndieWebCamp and HWC sessions after they’ve finished. Archive the session notes somewhere more findable and linkable.
 * new projects you start using on your personal website; be sure to include your site in the IndieWeb Examples section on the page.

If something is not particularly indieweb-related, e.g. it didn't come up in the discussion of things that are indieweb-related, perhaps consider documenting it on Wikipedia instead (and/or using Wikipedia as a reference/citation).

New pages that don’t immediately define their IndieWeb relevance may be deleted.

Multiword Page Names
When naming of multiword wiki pages, use multiple words with spaces, or dashes for multi-word terms., rather than WikiCase or camelCase.

Definitions include IndieWeb relevance
Definitions should include why something is specifically relevant to the IndieWeb.

E.g. the jargon example above could be improved with IndieWeb relevance like:
 * A jargon term is a specific unobvious word, concept, or technology (like Webmention), or re-use of a word to mean something other than its common meaning (like feed), or sometimes re-using a word as an acronym (like POSSE).

Please also avoid jargonitions, they’re much more harmful in practice than snarkinitions in terms of approachability. We’re ok with not necessarily attracting (or even perhaps detracting?) the Hackernews crowd, much more than scaring away non-developers. Humor at the expense of technology is much more acceptable than making people feel unwelcome with inaccessible text.

Document your decisions
Once you've documented yourself on your User page, and started incrementally documenting your "Itches" and "Working On", as you get work done and deploy to your personal site, document your "major decisions", on your user page or perhaps in a "Implementation Design" section on your project page.

Examples:
 * Falcon - major design decisions made in Falcon so far.

Documenting your major design and implementation decisions will help you better consider when to revisit them, and when to work on new personal site features and functionality instead.

Define jargon
Any time someone uses a jargon term in chat, or other indieweb related communications, go ahead and ask in the channel: This will prompt Loqi to either answer with the definition with the wiki, or to prompt you to define it with a link to create the page on the wiki.
 * What is jargon term

You can then define it by clicking on that link, or answer answer the what is question:
 * A jargon term is a specific unobvious concept, or re-use of a word to mean something other than its common meaning.

See definition for more details on writing good definitions.

Tweetable definitions
Check the definitions on wiki pages, and edit them so they are tweetable, as there is evidence that people will tweet good definitions that are of tweetable length (including a subsequent link to the page) - that's 257 characters (space + 23 characters for the tco'd link).

Progressive disclosure of content
All pages should start with being the best source for basic knowledge on their subject.

Starting with a simple jargon-free Tweetable definition that is understandable by a broader audience, progressively document all the important research and details that are discovered or invented by the community about the subject.

And then incrementally document details only as needed for real world reasons / use-cases that provide benefits to those reading.

Nearly every page on the wiki can be improved in this regard, to provide progressive disclosure of relevant content.

E.g. getting started can (still) be continuously improved in this regard. As can web hosting.

Replacing Redirects
When editing a redirect (a page which is nothing more than a  line), if you are replacing it with actual content, first note in the #indieweb-meta discuss channel that you're going to replace it with actual content, then delete the redirect, and recreate the page with the new content.

Common Page Structure
Most pages on the wiki have evolved to have a fairly common page structure, starting with a simple definition, and then adding additional sections such as:
 * Why
 * How to
 * IndieWeb Examples
 * Brainstorming
 * See Also

For more details on these and more, see:
 * expand a page

Special Case Pages
In addition to the common structure across many pages, there are also several clusters or instances of special case pages.

Standards Pages
The wiki has pages for standards / specifications that were developed on the indieweb wiki, and have started or been formalized at W3C, and thus their pages (and subpages) here have evolved in support of those specifications.

While these are rapidly evolving, take a look at:
 * Webmention
 * Micropub
 * post type discovery

There are also pages that are about the indieweb usage of standards developed elsewhere or in active collaboration across communities, e.g. the pages for various microformats. Though these are generally structured in the common structure noted above, they may as a set have special patterns worth noting:
 * h-entry
 * h-card
 * h-event
 * h-review

(stub) - help expand this section with documentation of patterns across this type of special page.

Historical Pages
Some pages help document history, e.g.:
 * history
 * timeline
 * site-deaths
 * silo-quits

(stub) - help expand this section with documentation of patterns across this type of special page.

Cross-Generation Pages
As certain IndieWeb building-blocks become more widespread, folks from later generations could benefit from re-organized content. In some cases, it may be beneficial to break out "introductory" content (including high-level explanations, examples with screenshots, tools and services, ...) from "developer" content (such as protocol diagrams, code snippets, brainstorming, ...) For example:


 * Webmention is an introduction page, with developer-specific content moved to Webmention-developer.

(stub) - help expand this section with documentation of patterns across this type of special page.

General Suggestions
General suggestions for editing the wiki and adding prose.

In addition to incremental edits, consider the following:


 * Tip: when adding prose to the wiki, consider adding semantic linebreaks, at both sentence terminators, and after long clauses, per https://rhodesmill.org/brandon/2012/one-sentence-per-line/

Related Articles
The above is very much specific to what is good wikifying for IndieWeb in particular.

Here are related articles on good writing, structure, and wikifying in general:
 * Wikipedia Project: How to wikify

Do I have to use the wiki and mediawiki syntax?
While it's nice to put content into the wiki using standard markup for it, we realize not everyone is a wiki fan, knows how to do it, or even may have the time to learn to do it. (Documenting what you've done is both important and work enough.)
 * Alternative: Post on your own site with CC0! An alternate option is to practice the IndieWeb principle of posting on your own site first where you have ultimate control. Then webmention "Indieweb" (for Superfeedr) or dump the link into chat. As long as you license your content as CC0 for that post, someone will surely add it to the wiki on your behalf.
 * Add content, with double linebreaks for paragraphs! Users shouldn't feel guilty for adding content as best as they can (markup/formatting or not) where they feel it's appropriate. Others will come along and clean bits up in the near future. Nor should they hesitate to ask for help in chat if they'd like to learn more about wikifying.

Related chats:
 * https://chat.indieweb.org/2016-05-20#t1463775866966000
 * https://chat.indieweb.org/dev/2017-06-18#t1497799332968000

Where should I add something to the wiki?
When you see an IndieWeb related article, post, concept, and want to add it to the wiki, it may not be obvious where to add it, even just as a "See Also". Here are some tips for where to add something:


 * 1) An existing page it is most relevant to.
 * 2) If there are a couple of pages (e.g. maybe a general concept like privacy, and a specific silo like Facebook), it’s ok to add it to both.
 * 3) If you can think of a few different related pages, then create a new stub page for it, and then add a link to that stub page in the See Also sections of those related pages