Wiki

wiki peut faire réfénce à :

suggestions / discussion sur le wiki indiewebcamp lui-même.
page type : la page-wiki comme type de page ou contenu
projects : les projets wiki en rapport avec l'hébergement wiki indieweb

Page type

Article principal : wiki-page

En plus des posts séquentiels / triés-dans-le-temps, bon nombre de personnes dans la communauté IndieWebCamp veulent ou hébergent un wiki ou des pages wiki sur leurs propres sites personnels.

Les pages wiki sont généralement modifiables et versionnées avec un historique de version visible / facilement accessible et des versions navigables. Les pages wiki sont souvent multi-auteurs et on une interface multi-plateforme (comme toute solution d'hébergement de contenu basée sur le web).

Tom Morris a son propre wiki sur http://wiki.tommorris.org/
Modèle:Tantek a un wiki sur http://tantek.pbworks.com
Amber Case a son propre wiki sur http://caseorganic.com/wiki/
...

Il existe aussi différents sites d'hébergement wiki / silos.

Projets

Article principal : wiki-projects

Les projets IndieWebCamp en rapport avec l'hébergement/création/édition wiki :

Federated Wiki
- tel que conçu/créé/développé/lancé lors de l'IndieWebCamp 2011
MediaWiki
- Used by Tom Morris on wiki.tommorris.org.

Voir aussi wiki projects brainstorming.

Fonctionnalités Wiki que Nous Utilisons

At some unlikely point in the far future, we may decide to migrate the wiki off of MediaWiki. If this ever happens, we'll need to be sure whatever replaces it has roughly the same functionality that we use in MediaWiki. Below is a list to collect descriptions of MediaWiki features that we use. Feel free to add to it.

Wiki-style editing - Click "edit" to view page source and "save" to save changes immediately. Conflicts are not merged automatically, and a message is shown if someone else has edited the page in the mean time.
Wiki-style links - MediaWiki provides a syntax for quickly linking between wiki pages, e.g. [[events]].
Nickname templates - We often use sparkline templates to display someone's photo and name in a line of text such as Aaron Parecki. This is done by creating a template with the person's nickname and typing {{aaronpk}} in a line of text.
Signature on edits - Sometimes we add a signature to lines using ~~~~ which is replaced by the logged-in user's signature and a timestamp.
Content templates - Several pages (such as events and 2016/Guest_List) use templates to avoid duplicating complicated wiki markup on the page. The templates themselves are wiki pages and are editing by the community.
IRC notifications - When wiki pages are edited, we get notifications in IRC describing the change.
The ability to embed HTML in the wiki markup – needed e.g. to add microformats to events
The ability to upload images, e.g. clicking "embed file" icon inserts wiki link with [[File:Example.jpg]]. Clicking that wiki link takes you to the form to upload the image.

Fonctionnalités Wiki dont Nous Avons Besoin

Sometimes, MediaWiki does not have a good way to do what we want, so we have to hack around it.

Hotlinked images - We often want to hotlink images to avoid uploading them to the wiki (which is only possible if the image can be CC0 licensed), but we also want to proxy the img src on the resulting page so that the site can be served over https even if the image is http

Voir aussi :

personnalisation mediawiki for all the things we've had to do to make MediaWiki work for us.

Suggestions

Voir :

2016/newskin for latest work on broader design improvements

Suggestions and bug reports for improving the IndieWeb.org wiki. Please provide suggestions as GitHub issues here:

https://github.com/indieweb/wiki/issues

https://github.com/indieweb/wiki/issues?state=open

Brainstorming

Ideas being iterated rather than a specific suggestion for improvement.

Catégoriser les Pages

Problem statement: If we look at the this-week reports (e.g. 2016-07-29 this week) and summaries of wiki pages that have been edited, it's a long list and doesn't provide a lot of information about why any particular page is important / compared to any other page, or any other way of chunking / understanding the long list.

Thoughts:

one possibility would be to present each page with an icon in front according to what "type" or "kind" of page it is.
another possibility is to use such types/kinds to cluster the list of changed pages by type/kind, thus avoiding a need to repeat icons over and over
either way we could also use the "page icon" or "emojicon" on each page in particular to provide an even more specific graphical hook/representation for easier/quicker understanding of what the pages were about

Approaches:

Use MediaWiki "Category:" for coarse top level categorization.
- What categories?
  - Develop adaptively as needed from looking at "this week" and seeing what patterns (sets of pages) emerge. E.g. from 2016-07-29 this week:
    - 📆 event pages for Events + subpages (HWC events), and IWC events /YYYY/city|country
    - project pages for specific projects e.g. ikiwiki, WordPress(/*), p3k, relmeauth.php, WhisperFollow, Monocle etc.
    - "feature" building blocks (including types of content like album, multi-photo, travel, and UI features like search), other things from IndieMark
    - "technology/plumbing" building blocks (like Webmention)
    - people (User: pages)
    - (anti-)patterns e.g. database-antipattern, js;dr
    - silos (GitHub, Google Photos, etc.)
    - companies (e.g. Google)
    - services (e.g. SubToMe, web hosting, Bridgy, silo.pub)
    - history (points of record, e.g. site-deaths, history, timeline, posts about, videos about etc.)
    - technologies (in general, like Perl, other languages, frameworks)
  - (re-)use rough coarse categories from IndieWebCamp 2014 Year in Review separate lists of pages.
- Assign a generic icon (or emoji) for each top level category
Use page-specific page icons or emojicons (both already use templates, so should be automatable) to to customize the icon shown for a page

Fait

Les suggestions qui ont été implémentées.

wiki/resolved

Voir aussi