<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.hackersanddesigners.nl//api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vicky</id>
	<title>Hackers &amp; Designers - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.hackersanddesigners.nl//api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Vicky"/>
	<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Special:Contributions/Vicky"/>
	<updated>2026-04-28T10:45:57Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20629</id>
		<title>Offshore:Admin Hacks</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20629"/>
		<updated>2017-03-09T02:15:14Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* ADMIN HACK    06.03.2017    16:29        52°24&amp;#039;16.1&amp;quot;N 4°53&amp;#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[File:boat.gif]]&lt;br /&gt;
&lt;br /&gt;
==ADMIN HACK    06.03.2017    16:29        52°24&#039;16.1&amp;quot;N 4°53&#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==&lt;br /&gt;
&lt;br /&gt;
When you live on a boat, in the Netherlands, it is not possible to register your address there unless you are the lucky owner of one of the 2500 official houseboat addresses in Amsterdam. I moved to Amsterdam from Belgium in September last year. One month after, I bought an 8m motor cruiser boat with no working motor and really old batteries. The interior was covered with lacquer paint applied by the previous owner without paint hardener, which meant that if you would touch the walls, you’d be covered in paint. I knew it was quite some project to take on, but the price was tempting and I was ready for an adventure after graduating from university. &lt;br /&gt;
&lt;br /&gt;
Since buying an official houseboat address was never an option for me, I had to find an alternative way to be able to register in the Netherlands. At first I registered myself as an [https://www.amsterdam.nl/veelgevraagd/?productid=%7B78A87674-890E-426F-8FF0-8452BF095699%7D RNI] which basically is a registration for someone that doesn’t live in the Netherlands. You need this registration to be able to receive your BSN number. With this [https://www.amsterdam.nl/veelgevraagd/?productid=%7BD9EEC2D8-7BA7-4DEA-A931-1D2ACB207608%7D BSN] number you’re able to work in the Netherlands. After registering for the RNI I thought I was good with my administration until my manager, at the hostel I work at two days a week, came to me and informed me I had to get an official address or else they wouldn’t be able to extend my contract. Apparently the RNI registration is only valid for four months. I didn’t know. &lt;br /&gt;
&lt;br /&gt;
For this, I’m super glad I speak Dutch because it took me quite some time studying official websites to figure out what to do. At first I found an administrative construction that enables  [http://startpuntgrensarbeid.benelux.int cross-border workers] of the BeNeLux to be registered in one country and work in the other. Due to this lead, I didn’t look further and thought once again everything was fine. A month later I got an email from the HR department from the hostel: this construction was only for people that really lived in a city situated next to a border, so surely not for me. &lt;br /&gt;
&lt;br /&gt;
Informing with other people on what they did, I found out that I could register at a [https://www.amsterdam.nl/veelgevraagd/?productid=%7BB4A56660-8158-4DBA-A959-21DBAC61210D%7D#case_%7B1FEB8645-6EFE-45B8-A08F-72E15AD0463E%7D briefadres]. This is an address of a friend or family member that lives in the Netherlands and is willing to collect your mail. This registration can only be done by the main tenant and just two people can be registered at one briefadres. &lt;br /&gt;
&lt;br /&gt;
It was time to start looking for this type of address. I knew housing is a big problem in Amsterdam, but I didn’t know a lot of my friends were also not able to register at their place, even if they rented an apartment or room. This situation was created by the housing shortage in Amsterdam and the need to register to be able to work in the Netherlands. An owner of a house would let out an apartment without giving the tenant the possibility to register at that address, this way the owner could register himself or other people there and together with the rent also get money for providing someone a registration.&lt;br /&gt;
&lt;br /&gt;
After one month of looking for a possible briefadres I got really desperate, since my work contract was expiring so I made an appointment at the city hall and went there instead of calling them all the time and spending fortunes on callcredit. At the city hall I got the best service ever, I apparently charmed one of the employees there with my Flemish accent, explained my whole situation and he put a lot of effort to find a way to register: at my job. &lt;br /&gt;
This is a service they provide for expats living in hotels. I just needed proof of extension of my contract and a permission from my job, which I both got. Just 5 days before my contract expired, on my birthday January 25th, I was able to register for one year at a briefadres! &lt;br /&gt;
&lt;br /&gt;
So far for the registration, but my administrative struggle wasn’t over. Basically everything you have to apply for in the Netherlands is really a hustle when you don’t have a physical mailbox. When you work for a Dutch company you are also obliged to have a health insurance. I already have one in Belgium which has much much better conditions than what Dutch health insurance companies have to offer, but I had no choice. I had to apply. They send you the insurance card by mail. You can apply for [https://mijn.toeslagen.nl zorgtoeslag] (a compensation for health insurance) online, only not when you have a briefadres, then they have to mail you papers and you have to post them back. For a [https://www.digid.nl/ DigID] (login system for government websites) you need a mailbox. I can go on and on and on. &lt;br /&gt;
&lt;br /&gt;
Basically what I suggest you to do if you want to live off-the-grid  in the Netherlands and come from another country: rent a room for some months first and fix your administration before starting to live on a boat, in a yurt, or on a trailer.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20628</id>
		<title>Offshore:Admin Hacks</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20628"/>
		<updated>2017-03-09T02:06:58Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[File:boat.gif]]&lt;br /&gt;
&lt;br /&gt;
==ADMIN HACK    06.03.2017    16:29        52°24&#039;16.1&amp;quot;N 4°53&#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==&lt;br /&gt;
&lt;br /&gt;
When you live on a boat, in the Netherlands, it is not possible to register your address there unless you are the lucky owner of one of the 2500 official houseboat addresses in Amsterdam. I moved to Amsterdam from Belgium in September last year. One month after, I bought an 8m motor cruiser boat with no working motor and really old batteries. The interior was covered with lacquer paint applied by the previous owner without paint hardener, which meant that if you would touch the walls, you’d be covered in paint. I knew it was quite some project to take on, but the price was tempting and I was ready for an adventure after graduating from university. &lt;br /&gt;
&lt;br /&gt;
Since buying an official houseboat address was never an option for me, I had to find an alternative way to be able to register in the Netherlands. At first I registered myself as an RNI which basically is a registration for someone that doesn’t live in the Netherlands. You need this registration to be able to receive your BSN number. With this BSN number you’re able to work in the Netherlands. After registering for the RNI I thought I was good with my administration until my manager, at the hostel I work at two days a week, came to me and informed me I had to get an official address or else they wouldn’t be able to extend my contract. Apparently the RNI registration is only valid for four months. I didn’t know. &lt;br /&gt;
&lt;br /&gt;
For this, I’m super glad I speak Dutch because it took me quite some time studying official websites to figure out what to do. At first I found an administrative construction that enables  cross-border workers of the BeNeLux to be registered in one country and work in the other. Due to this lead, I didn’t look further and thought once again everything was fine. A month later I got an email from the HR department from the hostel: this construction was only for people that really lived in a city situated next to a border, so surely not for me. &lt;br /&gt;
&lt;br /&gt;
Informing with other people on what they did, I found out that I could register at a briefadres. This is an address of a friend or family member that lives in the Netherlands and is willing to collect your mail. This registration can only be done by the main tenant and just two people can be registered at one briefadres. &lt;br /&gt;
&lt;br /&gt;
It was time to start looking for this type of address. I knew housing is a big problem in Amsterdam, but I didn’t know a lot of my friends were also not able to register at their place, even if they rented an apartment or room. This situation was created by the housing shortage in Amsterdam and the need to register to be able to work in the Netherlands. An owner of a house would let out an apartment without giving the tenant the possibility to register at that address, this way the owner could register himself or other people there and together with the rent also get money for providing someone a registration.&lt;br /&gt;
&lt;br /&gt;
After one month of looking for a possible briefadres I got really desperate, since my work contract was expiring so I made an appointment at the city hall and went there instead of calling them all the time and spending fortunes on callcredit. At the city hall I got the best service ever, I apparently charmed one of the employees there with my Flemish accent, explained my whole situation and he put a lot of effort to find a way to register: at my job. &lt;br /&gt;
This is a service they provide for expats living in hotels. I just needed proof of extension of my contract and a permission from my job, which I both got. Just 5 days before my contract expired, on my birthday January 25th, I was able to register for one year at a briefadres! &lt;br /&gt;
&lt;br /&gt;
So far for the registration, but my administrative struggle wasn’t over. Basically everything you have to apply for in the Netherlands is really a hustle when you don’t have a physical mailbox. When you work for a Dutch company you are also obliged to have a health insurance. I already have one in Belgium which has much much better conditions than what Dutch health insurance companies have to offer, but I had no choice. I had to apply. They send you the insurance card by mail. You can apply for zorgtoeslag (a compensation for health insurance) online, only not when you have a briefadres, then they have to mail you papers and you have to post them back. For a DigID (login system for government websites) you need a mailbox. I can go on and on and on. &lt;br /&gt;
&lt;br /&gt;
Basically what I suggest you to do if you want to live off-the-grid  in the Netherlands and come from another country: rent a room for some months first and fix your administration before starting to live on a boat, in a yurt, or on a trailer.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20627</id>
		<title>Offshore:Admin Hacks</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20627"/>
		<updated>2017-03-09T02:06:40Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* ADMIN HACK    06.03.2017    16:29        52°24&amp;#039;16.1&amp;quot;N 4°53&amp;#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[File:boat.jpg]]&lt;br /&gt;
&lt;br /&gt;
==ADMIN HACK    06.03.2017    16:29        52°24&#039;16.1&amp;quot;N 4°53&#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==&lt;br /&gt;
&lt;br /&gt;
When you live on a boat, in the Netherlands, it is not possible to register your address there unless you are the lucky owner of one of the 2500 official houseboat addresses in Amsterdam. I moved to Amsterdam from Belgium in September last year. One month after, I bought an 8m motor cruiser boat with no working motor and really old batteries. The interior was covered with lacquer paint applied by the previous owner without paint hardener, which meant that if you would touch the walls, you’d be covered in paint. I knew it was quite some project to take on, but the price was tempting and I was ready for an adventure after graduating from university. &lt;br /&gt;
&lt;br /&gt;
Since buying an official houseboat address was never an option for me, I had to find an alternative way to be able to register in the Netherlands. At first I registered myself as an RNI which basically is a registration for someone that doesn’t live in the Netherlands. You need this registration to be able to receive your BSN number. With this BSN number you’re able to work in the Netherlands. After registering for the RNI I thought I was good with my administration until my manager, at the hostel I work at two days a week, came to me and informed me I had to get an official address or else they wouldn’t be able to extend my contract. Apparently the RNI registration is only valid for four months. I didn’t know. &lt;br /&gt;
&lt;br /&gt;
For this, I’m super glad I speak Dutch because it took me quite some time studying official websites to figure out what to do. At first I found an administrative construction that enables  cross-border workers of the BeNeLux to be registered in one country and work in the other. Due to this lead, I didn’t look further and thought once again everything was fine. A month later I got an email from the HR department from the hostel: this construction was only for people that really lived in a city situated next to a border, so surely not for me. &lt;br /&gt;
&lt;br /&gt;
Informing with other people on what they did, I found out that I could register at a briefadres. This is an address of a friend or family member that lives in the Netherlands and is willing to collect your mail. This registration can only be done by the main tenant and just two people can be registered at one briefadres. &lt;br /&gt;
&lt;br /&gt;
It was time to start looking for this type of address. I knew housing is a big problem in Amsterdam, but I didn’t know a lot of my friends were also not able to register at their place, even if they rented an apartment or room. This situation was created by the housing shortage in Amsterdam and the need to register to be able to work in the Netherlands. An owner of a house would let out an apartment without giving the tenant the possibility to register at that address, this way the owner could register himself or other people there and together with the rent also get money for providing someone a registration.&lt;br /&gt;
&lt;br /&gt;
After one month of looking for a possible briefadres I got really desperate, since my work contract was expiring so I made an appointment at the city hall and went there instead of calling them all the time and spending fortunes on callcredit. At the city hall I got the best service ever, I apparently charmed one of the employees there with my Flemish accent, explained my whole situation and he put a lot of effort to find a way to register: at my job. &lt;br /&gt;
This is a service they provide for expats living in hotels. I just needed proof of extension of my contract and a permission from my job, which I both got. Just 5 days before my contract expired, on my birthday January 25th, I was able to register for one year at a briefadres! &lt;br /&gt;
&lt;br /&gt;
So far for the registration, but my administrative struggle wasn’t over. Basically everything you have to apply for in the Netherlands is really a hustle when you don’t have a physical mailbox. When you work for a Dutch company you are also obliged to have a health insurance. I already have one in Belgium which has much much better conditions than what Dutch health insurance companies have to offer, but I had no choice. I had to apply. They send you the insurance card by mail. You can apply for zorgtoeslag (a compensation for health insurance) online, only not when you have a briefadres, then they have to mail you papers and you have to post them back. For a DigID (login system for government websites) you need a mailbox. I can go on and on and on. &lt;br /&gt;
&lt;br /&gt;
Basically what I suggest you to do if you want to live off-the-grid  in the Netherlands and come from another country: rent a room for some months first and fix your administration before starting to live on a boat, in a yurt, or on a trailer.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=File:Boat.gif&amp;diff=20626</id>
		<title>File:Boat.gif</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=File:Boat.gif&amp;diff=20626"/>
		<updated>2017-03-09T02:05:30Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20625</id>
		<title>Offshore:Admin Hacks</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20625"/>
		<updated>2017-03-09T02:00:18Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* ADMIN HACK    06.03.2017    16:29        52°24&amp;#039;16.1&amp;quot;N 4°53&amp;#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==ADMIN HACK    06.03.2017    16:29        52°24&#039;16.1&amp;quot;N 4°53&#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==&lt;br /&gt;
&lt;br /&gt;
When you live on a boat, in the Netherlands, it is not possible to register your address there unless you are the lucky owner of one of the 2500 official houseboat addresses in Amsterdam. I moved to Amsterdam from Belgium in September last year. One month after, I bought an 8m motor cruiser boat with no working motor and really old batteries. The interior was covered with lacquer paint applied by the previous owner without paint hardener, which meant that if you would touch the walls, you’d be covered in paint. I knew it was quite some project to take on, but the price was tempting and I was ready for an adventure after graduating from university. &lt;br /&gt;
&lt;br /&gt;
Since buying an official houseboat address was never an option for me, I had to find an alternative way to be able to register in the Netherlands. At first I registered myself as an RNI which basically is a registration for someone that doesn’t live in the Netherlands. You need this registration to be able to receive your BSN number. With this BSN number you’re able to work in the Netherlands. After registering for the RNI I thought I was good with my administration until my manager, at the hostel I work at two days a week, came to me and informed me I had to get an official address or else they wouldn’t be able to extend my contract. Apparently the RNI registration is only valid for four months. I didn’t know. &lt;br /&gt;
&lt;br /&gt;
For this, I’m super glad I speak Dutch because it took me quite some time studying official websites to figure out what to do. At first I found an administrative construction that enables  cross-border workers of the BeNeLux to be registered in one country and work in the other. Due to this lead, I didn’t look further and thought once again everything was fine. A month later I got an email from the HR department from the hostel: this construction was only for people that really lived in a city situated next to a border, so surely not for me. &lt;br /&gt;
&lt;br /&gt;
Informing with other people on what they did, I found out that I could register at a briefadres. This is an address of a friend or family member that lives in the Netherlands and is willing to collect your mail. This registration can only be done by the main tenant and just two people can be registered at one briefadres. &lt;br /&gt;
&lt;br /&gt;
It was time to start looking for this type of address. I knew housing is a big problem in Amsterdam, but I didn’t know a lot of my friends were also not able to register at their place, even if they rented an apartment or room. This situation was created by the housing shortage in Amsterdam and the need to register to be able to work in the Netherlands. An owner of a house would let out an apartment without giving the tenant the possibility to register at that address, this way the owner could register himself or other people there and together with the rent also get money for providing someone a registration.&lt;br /&gt;
&lt;br /&gt;
After one month of looking for a possible briefadres I got really desperate, since my work contract was expiring so I made an appointment at the city hall and went there instead of calling them all the time and spending fortunes on callcredit. At the city hall I got the best service ever, I apparently charmed one of the employees there with my Flemish accent, explained my whole situation and he put a lot of effort to find a way to register: at my job. &lt;br /&gt;
This is a service they provide for expats living in hotels. I just needed proof of extension of my contract and a permission from my job, which I both got. Just 5 days before my contract expired, on my birthday January 25th, I was able to register for one year at a briefadres! &lt;br /&gt;
&lt;br /&gt;
So far for the registration, but my administrative struggle wasn’t over. Basically everything you have to apply for in the Netherlands is really a hustle when you don’t have a physical mailbox. When you work for a Dutch company you are also obliged to have a health insurance. I already have one in Belgium which has much much better conditions than what Dutch health insurance companies have to offer, but I had no choice. I had to apply. They send you the insurance card by mail. You can apply for zorgtoeslag (a compensation for health insurance) online, only not when you have a briefadres, then they have to mail you papers and you have to post them back. For a DigID (login system for government websites) you need a mailbox. I can go on and on and on. &lt;br /&gt;
&lt;br /&gt;
Basically what I suggest you to do if you want to live off-the-grid  in the Netherlands and come from another country: rent a room for some months first and fix your administration before starting to live on a boat, in a yurt, or on a trailer.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20624</id>
		<title>Offshore:Admin Hacks</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Offshore:Admin_Hacks&amp;diff=20624"/>
		<updated>2017-03-09T01:59:03Z</updated>

		<summary type="html">&lt;p&gt;Vicky: Created page with &amp;quot;==ADMIN HACK    06.03.2017    16:29        52°24&amp;#039;16.1&amp;quot;N 4°53&amp;#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==  When you live on a boat, in the Netherlands, it is not possible...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==ADMIN HACK    06.03.2017    16:29        52°24&#039;16.1&amp;quot;N 4°53&#039;12.1&amp;quot;E    inside: 16.7°C      outside: 9°C==&lt;br /&gt;
&lt;br /&gt;
When you live on a boat, in the Netherlands, it is not possible to register your address there unless you are the lucky owner of one of the 2500 official houseboat addresses in Amsterdam. I moved to Amsterdam from Belgium in September last year. One month after, I bought an 8m motor cruiser boat with no working motor and really old batteries. The interior was covered with lacquer paint applied by the previous owner without paint hardener, which meant that if you would touch the walls, you’d be covered in paint. I knew it was quite some project to take on, but the price was tempting and I was ready for an adventure after graduating from university. &lt;br /&gt;
Since buying an official houseboat address was never an option for me, I had to find an alternative way to be able to register in the Netherlands. At first I registered myself as an RNI which basically is a registration for someone that doesn’t live in the Netherlands. You need this registration to be able to receive your BSN number. With this BSN number you’re able to work in the Netherlands. After registering for the RNI I thought I was good with my administration until my manager, at the hostel I work at two days a week, came to me and informed me I had to get an official address or else they wouldn’t be able to extend my contract. Apparently the RNI registration is only valid for four months. I didn’t know. &lt;br /&gt;
For this, I’m super glad I speak Dutch because it took me quite some time studying official websites to figure out what to do. At first I found an administrative construction that enables  cross-border workers of the BeNeLux to be registered in one country and work in the other. Due to this lead, I didn’t look further and thought once again everything was fine. A month later I got an email from the HR department from the hostel: this construction was only for people that really lived in a city situated next to a border, so surely not for me. &lt;br /&gt;
Informing with other people on what they did, I found out that I could register at a briefadres. This is an address of a friend or family member that lives in the Netherlands and is willing to collect your mail. This registration can only be done by the main tenant and just two people can be registered at one briefadres. &lt;br /&gt;
It was time to start looking for this type of address. I knew housing is a big problem in Amsterdam, but I didn’t know a lot of my friends were also not able to register at their place, even if they rented an apartment or room. This situation was created by the housing shortage in Amsterdam and the need to register to be able to work in the Netherlands. An owner of a house would let out an apartment without giving the tenant the possibility to register at that address, this way the owner could register himself or other people there and together with the rent also get money for providing someone a registration.&lt;br /&gt;
&lt;br /&gt;
After one month of looking for a possible briefadres I got really desperate, since my work contract was expiring so I made an appointment at the city hall and went there instead of calling them all the time and spending fortunes on callcredit. At the city hall I got the best service ever, I apparently charmed one of the employees there with my Flemish accent, explained my whole situation and he put a lot of effort to find a way to register: at my job. &lt;br /&gt;
This is a service they provide for expats living in hotels. I just needed proof of extension of my contract and a permission from my job, which I both got. Just 5 days before my contract expired, on my birthday January 25th, I was able to register for one year at a briefadres! &lt;br /&gt;
&lt;br /&gt;
So far for the registration, but my administrative struggle wasn’t over. Basically everything you have to apply for in the Netherlands is really a hustle when you don’t have a physical mailbox. When you work for a Dutch company you are also obliged to have a health insurance. I already have one in Belgium which has much much better conditions than what Dutch health insurance companies have to offer, but I had no choice. I had to apply. They send you the insurance card by mail. You can apply for zorgtoeslag (a compensation for health insurance) online, only not when you have a briefadres, then they have to mail you papers and you have to post them back. For a DigID (login system for government websites) you need a mailbox. I can go on and on and on. Basically what I suggest you to do if you want to live off-the-grid  in the Netherlands and come from another country: rent a room for some months first and fix your administration before starting to live on a boat, in a yurt, or on a trailer.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20623</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20623"/>
		<updated>2017-03-09T01:57:14Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* H&amp;amp;D articles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by the theme “Get Prepped. Investigating means of going on and off the grid” H&amp;amp;D developed a means to reflect on and question our daily work and living environments specifically focussing on dependence of systems, grids, and networks. H&amp;amp;D invited Vicky de Visser to write a series of articles that provide a context to ongoing H&amp;amp;D activities.&lt;br /&gt;
Do not hesitate to contact us to share your thoughts, questions or ideas for contributions: info@hackersanddesigners.nl.&lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;br /&gt;
*[[Offshore:Admin Hacks|Offshore: Admin Hacks]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20622</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20622"/>
		<updated>2017-03-09T01:56:50Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* H&amp;amp;D articles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by the theme “Get Prepped. Investigating means of going on and off the grid” H&amp;amp;D developed a means to reflect on and question our daily work and living environments specifically focussing on dependence of systems, grids, and networks. H&amp;amp;D invited Vicky de Visser to write a series of articles that provide a context to ongoing H&amp;amp;D activities.&lt;br /&gt;
Do not hesitate to contact us to share your thoughts, questions or ideas for contributions: info@hackersanddesigners.nl.&lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;br /&gt;
*[[Offshore:Admin Hacks|Admin Hacks]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20531</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20531"/>
		<updated>2017-02-13T21:25:52Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* The importance of going on and off the grid */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Approaching Grids==&lt;br /&gt;
The process of going ‘on and off-the grid’ is a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. To be able to reflect on the roles, meanings and impacts of different grids we are relying on as hackers and designers, this first article will explore the nature of grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
Serving as a broad examination of how ‘a grid’ can affect our interactions this submersion into the world of grids will be followed by further writings that highlight more specific examples and cases, and by doing so hopefully creating a curious and experimental path towards an alternative or new grid.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is “a pattern or structure made from horizontal and vertical lines crossing each other to form squares.”  Since going off-grid for sure does not mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
In her book “Gender” [2] sociologist Lisa Wade describes these grids as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people and enable a more efficient execution of goals, than we as individuals are capable of if we would try to reach the same goals alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it is almost impossible for an individual to step out of them and they are not always set up with the goal of meeting the needs individual members of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be is formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is] “The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles, which provide a script for individual interaction.”&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position in society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society or a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids it seems rather impossible to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. The relation between participants and grids is described as the grid/group theory by several anthropologists.&lt;br /&gt;
&lt;br /&gt;
==The Grid/Group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] The intention of the theory was to show how rituals and traditions are relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” There would be four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk is not seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
Thus the grids I would like to discuss here are remote support infrastructures with an anticipated goal initiated by the developer or are based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and therefore can not be neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
So what does it mean to be on a grid as an individual, being part of different groups and subgroups? What are different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual–being put on certain coordinates when born into this world, placed in a predefined context and time, we are certainly bound to participate in the grids that are designed for us. This may be through the laws of the country you live in, the laws of nature, or even the structure of your own body. Those grids have clear limits, do’s and don’ts. If you don’t participate they can have an extensive impact on yourself as an individual. As we grow up we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to approach work, and so on. These grids imposed upon us by external factors come with differences in, for instance strength of their force and extend of the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on someone’s individual freedom, as to not participating in certain technological progress will cut into the freedom to socially interact but might have a rather small impact due to smaller influence of that grid on one’s personal life. &lt;br /&gt;
Individuals might choose to hop on a specific grid-train because they strongly believe in the benefits of participating in that specific grid. These benefits can be personal, but can also have a positive impact on one’s surroundings.&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can also imply negative outcomes. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is often the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology.&lt;br /&gt;
Although going off-the-grid can have big benefits it is not always easy to do so as Denney describes: “Where a group is strong there is a clear boundary between members and non-members, and though it may be possible for an individual to leave the group, that will have high costs in that membership if the group confers many benefits. As a result, members of the group are able to exert considerable pressure on the individual to conform to its requirements.” [5]&lt;br /&gt;
&lt;br /&gt;
Although there is the possibility to go off-grid by choice, it can also be forced upon a person. It can be due to an inability to participate, for example, because of remoteness, unavailability of facilities, or an absence of resources. &lt;br /&gt;
Choosing individually or collectively to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grids and structures, since a grid needs its participants to enable its existence.&lt;br /&gt;
&lt;br /&gt;
==The importance of going on and off the grid==&lt;br /&gt;
As hackers, designers, artists and net-workers, there are several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. While considering means to challenge new as well asand established grids that fabricate our environment questions emerge such as: What are the conflicts we encounter while participating in different grids? What kind of demands arise when we choose to go off the grid? What is the influence of established grids on us? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into [https://en.wikipedia.org/wiki/Grey_goo Grey Goo]? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
Written by Vicky De Visser, edited by Anja Groten. &lt;br /&gt;
Published on February 13th, 2017.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20530</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20530"/>
		<updated>2017-02-13T21:24:49Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* The importance of going on and off the grid */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Approaching Grids==&lt;br /&gt;
The process of going ‘on and off-the grid’ is a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. To be able to reflect on the roles, meanings and impacts of different grids we are relying on as hackers and designers, this first article will explore the nature of grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
Serving as a broad examination of how ‘a grid’ can affect our interactions this submersion into the world of grids will be followed by further writings that highlight more specific examples and cases, and by doing so hopefully creating a curious and experimental path towards an alternative or new grid.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is “a pattern or structure made from horizontal and vertical lines crossing each other to form squares.”  Since going off-grid for sure does not mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
In her book “Gender” [2] sociologist Lisa Wade describes these grids as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people and enable a more efficient execution of goals, than we as individuals are capable of if we would try to reach the same goals alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it is almost impossible for an individual to step out of them and they are not always set up with the goal of meeting the needs individual members of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be is formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is] “The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles, which provide a script for individual interaction.”&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position in society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society or a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids it seems rather impossible to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. The relation between participants and grids is described as the grid/group theory by several anthropologists.&lt;br /&gt;
&lt;br /&gt;
==The Grid/Group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] The intention of the theory was to show how rituals and traditions are relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” There would be four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk is not seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
Thus the grids I would like to discuss here are remote support infrastructures with an anticipated goal initiated by the developer or are based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and therefore can not be neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
So what does it mean to be on a grid as an individual, being part of different groups and subgroups? What are different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual–being put on certain coordinates when born into this world, placed in a predefined context and time, we are certainly bound to participate in the grids that are designed for us. This may be through the laws of the country you live in, the laws of nature, or even the structure of your own body. Those grids have clear limits, do’s and don’ts. If you don’t participate they can have an extensive impact on yourself as an individual. As we grow up we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to approach work, and so on. These grids imposed upon us by external factors come with differences in, for instance strength of their force and extend of the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on someone’s individual freedom, as to not participating in certain technological progress will cut into the freedom to socially interact but might have a rather small impact due to smaller influence of that grid on one’s personal life. &lt;br /&gt;
Individuals might choose to hop on a specific grid-train because they strongly believe in the benefits of participating in that specific grid. These benefits can be personal, but can also have a positive impact on one’s surroundings.&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can also imply negative outcomes. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is often the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology.&lt;br /&gt;
Although going off-the-grid can have big benefits it is not always easy to do so as Denney describes: “Where a group is strong there is a clear boundary between members and non-members, and though it may be possible for an individual to leave the group, that will have high costs in that membership if the group confers many benefits. As a result, members of the group are able to exert considerable pressure on the individual to conform to its requirements.” [5]&lt;br /&gt;
&lt;br /&gt;
Although there is the possibility to go off-grid by choice, it can also be forced upon a person. It can be due to an inability to participate, for example, because of remoteness, unavailability of facilities, or an absence of resources. &lt;br /&gt;
Choosing individually or collectively to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grids and structures, since a grid needs its participants to enable its existence.&lt;br /&gt;
&lt;br /&gt;
==The importance of going on and off the grid==&lt;br /&gt;
As hackers, designers, artists and net-workers, there are several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. While considering means to challenge new as well asand established grids that fabricate our environment questions emerge such as: What are the conflicts we encounter while participating in different grids? What kind of demands arise when we choose to go off the grid? What is the influence of established grids on us? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into [Grey Goo https://en.wikipedia.org/wiki/Grey_goo]? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
Written by Vicky De Visser, edited by Anja Groten. &lt;br /&gt;
Published on February 13th, 2017.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20529</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20529"/>
		<updated>2017-02-13T21:23:19Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Approaching Grids==&lt;br /&gt;
The process of going ‘on and off-the grid’ is a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. To be able to reflect on the roles, meanings and impacts of different grids we are relying on as hackers and designers, this first article will explore the nature of grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
Serving as a broad examination of how ‘a grid’ can affect our interactions this submersion into the world of grids will be followed by further writings that highlight more specific examples and cases, and by doing so hopefully creating a curious and experimental path towards an alternative or new grid.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is “a pattern or structure made from horizontal and vertical lines crossing each other to form squares.”  Since going off-grid for sure does not mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
In her book “Gender” [2] sociologist Lisa Wade describes these grids as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people and enable a more efficient execution of goals, than we as individuals are capable of if we would try to reach the same goals alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it is almost impossible for an individual to step out of them and they are not always set up with the goal of meeting the needs individual members of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be is formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is] “The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles, which provide a script for individual interaction.”&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position in society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society or a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids it seems rather impossible to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. The relation between participants and grids is described as the grid/group theory by several anthropologists.&lt;br /&gt;
&lt;br /&gt;
==The Grid/Group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] The intention of the theory was to show how rituals and traditions are relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” There would be four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk is not seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
Thus the grids I would like to discuss here are remote support infrastructures with an anticipated goal initiated by the developer or are based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and therefore can not be neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
So what does it mean to be on a grid as an individual, being part of different groups and subgroups? What are different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual–being put on certain coordinates when born into this world, placed in a predefined context and time, we are certainly bound to participate in the grids that are designed for us. This may be through the laws of the country you live in, the laws of nature, or even the structure of your own body. Those grids have clear limits, do’s and don’ts. If you don’t participate they can have an extensive impact on yourself as an individual. As we grow up we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to approach work, and so on. These grids imposed upon us by external factors come with differences in, for instance strength of their force and extend of the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on someone’s individual freedom, as to not participating in certain technological progress will cut into the freedom to socially interact but might have a rather small impact due to smaller influence of that grid on one’s personal life. &lt;br /&gt;
Individuals might choose to hop on a specific grid-train because they strongly believe in the benefits of participating in that specific grid. These benefits can be personal, but can also have a positive impact on one’s surroundings.&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can also imply negative outcomes. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is often the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology.&lt;br /&gt;
Although going off-the-grid can have big benefits it is not always easy to do so as Denney describes: “Where a group is strong there is a clear boundary between members and non-members, and though it may be possible for an individual to leave the group, that will have high costs in that membership if the group confers many benefits. As a result, members of the group are able to exert considerable pressure on the individual to conform to its requirements.” [5]&lt;br /&gt;
&lt;br /&gt;
Although there is the possibility to go off-grid by choice, it can also be forced upon a person. It can be due to an inability to participate, for example, because of remoteness, unavailability of facilities, or an absence of resources. &lt;br /&gt;
Choosing individually or collectively to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grids and structures, since a grid needs its participants to enable its existence.&lt;br /&gt;
&lt;br /&gt;
==The importance of going on and off the grid==&lt;br /&gt;
As hackers, designers, artists and net-workers, there are several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. While considering means to challenge new as well asand established grids that fabricate our environment questions emerge such as: What are the conflicts we encounter while participating in different grids? What kind of demands arise when we choose to go off the grid? What is the influence of established grids on us? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
Written by Vicky De Visser, edited by Anja Groten. &lt;br /&gt;
Published on February 13th, 2017.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20528</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20528"/>
		<updated>2017-02-13T21:20:59Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Approaching Grids==&lt;br /&gt;
The process of going ‘on and off-the grid’ is a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. To be able to reflect on the roles, meanings and impacts of different grids we are relying on as hackers and designers, this first article will explore the nature of grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
Serving as a broad examination of how ‘a grid’ can affect our interactions this submersion into the world of grids will be followed by further writings that highlight more specific examples and cases, and by doing so hopefully creating a curious and experimental path towards an alternative or new grid.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is “a pattern or structure made from horizontal and vertical lines crossing each other to form squares.”  Since going off-grid for sure does not mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
In her book “Gender” [2] sociologist Lisa Wade describes these grids as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people and enable a more efficient execution of goals, than we as individuals are capable of if we would try to reach the same goals alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it is almost impossible for an individual to step out of them and they are not always set up with the goal of meeting the needs individual members of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be is formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is] “The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles, which provide a script for individual interaction.”&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position in society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society or a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids it seems rather impossible to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. The relation between participants and grids is described as the grid/group theory by several anthropologists.&lt;br /&gt;
&lt;br /&gt;
==The Grid/Group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] The intention of the theory was to show how rituals and traditions are relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” There would be four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk is not seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
Thus the grids I would like to discuss here are remote support infrastructures with an anticipated goal initiated by the developer or are based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and therefore can not be neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
So what does it mean to be on a grid as an individual, being part of different groups and subgroups? What are different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual–being put on certain coordinates when born into this world, placed in a predefined context and time, we are certainly bound to participate in the grids that are designed for us. This may be through the laws of the country you live in, the laws of nature, or even the structure of your own body. Those grids have clear limits, do’s and don’ts. If you don’t participate they can have an extensive impact on yourself as an individual. As we grow up we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to approach work, and so on. These grids imposed upon us by external factors come with differences in, for instance strength of their force and extend of the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on someone’s individual freedom, as to not participating in certain technological progress will cut into the freedom to socially interact but might have a rather small impact due to smaller influence of that grid on one’s personal life. &lt;br /&gt;
Individuals might choose to hop on a specific grid-train because they strongly believe in the benefits of participating in that specific grid. These benefits can be personal, but can also have a positive impact on one’s surroundings.&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can also imply negative outcomes. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is often the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology.&lt;br /&gt;
Although going off-the-grid can have big benefits it is not always easy to do so as Denney describes: “Where a group is strong there is a clear boundary between members and non-members, and though it may be possible for an individual to leave the group, that will have high costs in that membership if the group confers many benefits. As a result, members of the group are able to exert considerable pressure on the individual to conform to its requirements.” [5]&lt;br /&gt;
&lt;br /&gt;
Although there is the possibility to go off-grid by choice, it can also be forced upon a person. It can be due to an inability to participate, for example, because of remoteness, unavailability of facilities, or an absence of resources. &lt;br /&gt;
Choosing individually or collectively to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grids and structures, since a grid needs its participants to enable its existence.&lt;br /&gt;
&lt;br /&gt;
==The importance of going on and off the grid==&lt;br /&gt;
As hackers, designers, artists and net-workers, there are several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. While considering means to challenge new as well asand established grids that fabricate our environment questions emerge such as: What are the conflicts we encounter while participating in different grids? What kind of demands arise when we choose to go off the grid? What is the influence of established grids on us? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20527</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20527"/>
		<updated>2017-02-13T21:18:37Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by the theme “Get Prepped. Investigating means of going on and off the grid” H&amp;amp;D developed a means to reflect on and question our daily work and living environments specifically focussing on dependence of systems, grids, and networks. H&amp;amp;D invited Vicky de Visser to write a series of articles that provide a context to ongoing H&amp;amp;D activities.&lt;br /&gt;
Do not hesitate to contact us to share your thoughts, questions or ideas for contributions: info@hackersanddesigners.nl.&lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20526</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20526"/>
		<updated>2017-02-13T17:51:14Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* On the grid */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;xx&lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==Let&#039;s investigate how to go on or off grid as H&amp;amp;D==&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20525</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20525"/>
		<updated>2017-02-13T17:51:06Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;xx&lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
xx &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==Let&#039;s investigate how to go on or off grid as H&amp;amp;D==&lt;br /&gt;
xx&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20524</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20524"/>
		<updated>2017-02-13T17:35:07Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by the theme “Get Prepped. Investigating means of going on and off the grid” H&amp;amp;D developed a public program to reflect and question our daily work and living environments specifically focussing on dependence of systems, grids, and networks. H&amp;amp;D invited Vicky de Visser to write a series of articles that provide a context to ongoing H&amp;amp;D activities.&lt;br /&gt;
Do not hesitate to contact us to share your thoughts, questions or ideas for contributions: info@hackersanddesigners.nl.&lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20523</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20523"/>
		<updated>2017-02-13T15:59:51Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Advantages to (prepare to) go on or off grid for H&amp;amp;D */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] One reason it was designed was to show how rituals and traditions were relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” According to them there are four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk isn’t seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
To conclude, we can assume that the grids we want to talk about are remote support infrastructures with an anticipated goal initiated by the developer or based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and cannot be politically neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
What does it mean to be on a grid as an individual, part of different groups and subgroups? &lt;br /&gt;
What are the different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual put on a certain coordinates when born into this world, placed in a predefined context and time, we are certainly forced by external structures to participate in the grids they designed for us. This can for example be the laws of a country you live in, the laws of nature, or even the structure of your own body. They have clear limits, do’s and don’ts, and if you don’t participate in them they can sometimes have an extensive impact on yourself as an individual. As we grow up in our environments we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to work, and so on. In these grids posed upon us by external factors there is a difference to be found in the strength of their force and the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on your individual freedom, as to not participating in certain technological progress will also cut into your the freedom of your social interactions, but will rather have a smaller impact due to smaller influence of that grid on personal lives. &lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can imply more negative results than benefits for an individual. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is al lot of times the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology. Although there is the possibility to go off-grid by choice it can also be forced upon a person. It can be due to an inability to participate by, for example, remoteness, no available facilities, or an absence of resources. &lt;br /&gt;
Choosing collective or individual to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grid and structures, since a grid needs its participants to enable its existence. &lt;br /&gt;
&lt;br /&gt;
==Let&#039;s investigate how to go on or off grid as H&amp;amp;D==&lt;br /&gt;
With H&amp;amp;D we would like to challenge new and established grids that make up our environment. To do that we would like to examine questions as: What are the conflicts we encounter while participating in different grids? What kind of conflicts rise when we choose to go off the grid? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As hackers, designers, artists or net-workers, there are a several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20522</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20522"/>
		<updated>2017-02-13T15:58:03Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1] we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] One reason it was designed was to show how rituals and traditions were relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” According to them there are four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk isn’t seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
To conclude, we can assume that the grids we want to talk about are remote support infrastructures with an anticipated goal initiated by the developer or based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and cannot be politically neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
What does it mean to be on a grid as an individual, part of different groups and subgroups? &lt;br /&gt;
What are the different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual put on a certain coordinates when born into this world, placed in a predefined context and time, we are certainly forced by external structures to participate in the grids they designed for us. This can for example be the laws of a country you live in, the laws of nature, or even the structure of your own body. They have clear limits, do’s and don’ts, and if you don’t participate in them they can sometimes have an extensive impact on yourself as an individual. As we grow up in our environments we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to work, and so on. In these grids posed upon us by external factors there is a difference to be found in the strength of their force and the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on your individual freedom, as to not participating in certain technological progress will also cut into your the freedom of your social interactions, but will rather have a smaller impact due to smaller influence of that grid on personal lives. &lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can imply more negative results than benefits for an individual. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is al lot of times the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology. Although there is the possibility to go off-grid by choice it can also be forced upon a person. It can be due to an inability to participate by, for example, remoteness, no available facilities, or an absence of resources. &lt;br /&gt;
Choosing collective or individual to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grid and structures, since a grid needs its participants to enable its existence. &lt;br /&gt;
&lt;br /&gt;
==Advantages to (prepare to) go on or off grid for H&amp;amp;D==&lt;br /&gt;
With H&amp;amp;D we would like to challenge new and established grids that make up our environment. To do that we would like to examine questions as: What are the conflicts we encounter while participating in different grids? What kind of conflicts rise when we choose to go off the grid? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As hackers, designers, artists or net-workers, there are a several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
[1] Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017. &lt;br /&gt;
&lt;br /&gt;
[2] Wade, L., Ferree, M. M. Gender: Ideas, Interactions, Institutions. New York: Norton Independant publishers, 2014. &lt;br /&gt;
&lt;br /&gt;
[3] Shaun Hargreaves Heap, S. ed, Ross, A. ed. Understanding the enterprise culture. Edinburgh: Edinburgh University Press, 1992&lt;br /&gt;
&lt;br /&gt;
[4] Verweij, M., Luan, S., Nowacki, M. PS: Political Science and Politics: How to Test Cultural Theory: Suggestions for future research. Vol. 44, No., pp. 745-748. Published by: American Political Science Association, October 2011. &lt;br /&gt;
&lt;br /&gt;
Douglas, M., Cultural Bias, London: Royal Anthropological Institute, 1978.&lt;br /&gt;
&lt;br /&gt;
Thompson, M., Ellis, R., and Wildavsky, A., Cultural Theory. Colorado: Westview Press, 1990.&lt;br /&gt;
&lt;br /&gt;
Wildavsky, A. Choosing Preferences by Constructing Institutions: A cultural theory of preference formation. American Political Science Review 81: 1. 3-21, 1987.&lt;br /&gt;
&lt;br /&gt;
[5] Denney, D. Risk and Society. London: Sage publishers, 2005.&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20521</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20521"/>
		<updated>2017-02-13T15:55:09Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary &amp;lt;ref&amp;gt; Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017.&amp;lt;/ref&amp;gt;  we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] One reason it was designed was to show how rituals and traditions were relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” According to them there are four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk isn’t seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
To conclude, we can assume that the grids we want to talk about are remote support infrastructures with an anticipated goal initiated by the developer or based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and cannot be politically neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
What does it mean to be on a grid as an individual, part of different groups and subgroups? &lt;br /&gt;
What are the different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual put on a certain coordinates when born into this world, placed in a predefined context and time, we are certainly forced by external structures to participate in the grids they designed for us. This can for example be the laws of a country you live in, the laws of nature, or even the structure of your own body. They have clear limits, do’s and don’ts, and if you don’t participate in them they can sometimes have an extensive impact on yourself as an individual. As we grow up in our environments we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to work, and so on. In these grids posed upon us by external factors there is a difference to be found in the strength of their force and the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on your individual freedom, as to not participating in certain technological progress will also cut into your the freedom of your social interactions, but will rather have a smaller impact due to smaller influence of that grid on personal lives. &lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can imply more negative results than benefits for an individual. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is al lot of times the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology. Although there is the possibility to go off-grid by choice it can also be forced upon a person. It can be due to an inability to participate by, for example, remoteness, no available facilities, or an absence of resources. &lt;br /&gt;
Choosing collective or individual to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grid and structures, since a grid needs its participants to enable its existence. &lt;br /&gt;
&lt;br /&gt;
==Advantages to (prepare to) go on or off grid for H&amp;amp;D==&lt;br /&gt;
With H&amp;amp;D we would like to challenge new and established grids that make up our environment. To do that we would like to examine questions as: What are the conflicts we encounter while participating in different grids? What kind of conflicts rise when we choose to go off the grid? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As hackers, designers, artists or net-workers, there are a several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20520</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20520"/>
		<updated>2017-02-13T15:53:10Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary &amp;lt;ref&amp;gt;Oxford dictionary, “grid”. https://en.oxforddictionaries.com/definition/grid, accesed on 13-2-2017.&amp;lt;/ref&amp;gt;  we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] One reason it was designed was to show how rituals and traditions were relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” According to them there are four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk isn’t seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
To conclude, we can assume that the grids we want to talk about are remote support infrastructures with an anticipated goal initiated by the developer or based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and cannot be politically neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
What does it mean to be on a grid as an individual, part of different groups and subgroups? &lt;br /&gt;
What are the different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual put on a certain coordinates when born into this world, placed in a predefined context and time, we are certainly forced by external structures to participate in the grids they designed for us. This can for example be the laws of a country you live in, the laws of nature, or even the structure of your own body. They have clear limits, do’s and don’ts, and if you don’t participate in them they can sometimes have an extensive impact on yourself as an individual. As we grow up in our environments we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to work, and so on. In these grids posed upon us by external factors there is a difference to be found in the strength of their force and the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on your individual freedom, as to not participating in certain technological progress will also cut into your the freedom of your social interactions, but will rather have a smaller impact due to smaller influence of that grid on personal lives. &lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can imply more negative results than benefits for an individual. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is al lot of times the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology. Although there is the possibility to go off-grid by choice it can also be forced upon a person. It can be due to an inability to participate by, for example, remoteness, no available facilities, or an absence of resources. &lt;br /&gt;
Choosing collective or individual to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grid and structures, since a grid needs its participants to enable its existence. &lt;br /&gt;
&lt;br /&gt;
==Advantages to (prepare to) go on or off grid for H&amp;amp;D==&lt;br /&gt;
With H&amp;amp;D we would like to challenge new and established grids that make up our environment. To do that we would like to examine questions as: What are the conflicts we encounter while participating in different grids? What kind of conflicts rise when we choose to go off the grid? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As hackers, designers, artists or net-workers, there are a several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20519</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20519"/>
		<updated>2017-02-13T15:49:52Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1]  we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
The Grid/Group theory was developed by anthropologists Mary Douglas, Michael Thompson and Steve Rayner.[4] One reason it was designed was to show how rituals and traditions were relevant to modern society. Douglas, Thompson and Rayner describe the group as “the extent to which an individual’s interactions are confined within a specific group of people who form a sub-group within the larger community.” According to them there are four different social models defined by their group/grid balance. These models are: hierarchism, egalitarianism, individualism and fatalism. The hierarchists, who have a high grid and high group balance, show respect for authority and are conformative to the dominant norms in a society. Egalitarians who have a low grid, high group balance, tend to identify with the group holding outsiders responsible for risk. Individualists with low grid, low group balance act independent and are entrepreneurial, avoiding and anticipating to risks by themselves. They are willing to take risks and recognise personal benefit in these actions. The last group, a group with a high grid and low group structure are called fatalists. This group’s approach to risk isn’t seen as a collective problem that has to be solved but a personal trust in fate or luck. [5]&lt;br /&gt;
&lt;br /&gt;
To conclude, we can assume that the grids we want to talk about are remote support infrastructures with an anticipated goal initiated by the developer or based on the need of the participator. The grid’s effectiveness and impact is strongly connected to the position and relation it has with the participating individuals, and cannot be politically neutral. &lt;br /&gt;
&lt;br /&gt;
==On the grid==&lt;br /&gt;
What does it mean to be on a grid as an individual, part of different groups and subgroups? &lt;br /&gt;
What are the different ways to be on a grid, or to be using the facilities of an infrastructure? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an individual put on a certain coordinates when born into this world, placed in a predefined context and time, we are certainly forced by external structures to participate in the grids they designed for us. This can for example be the laws of a country you live in, the laws of nature, or even the structure of your own body. They have clear limits, do’s and don’ts, and if you don’t participate in them they can sometimes have an extensive impact on yourself as an individual. As we grow up in our environments we get a slow but steady introduction into already established grids. It goes from how to eat, walk, talk, draw, to what study to chose, how to work, and so on. In these grids posed upon us by external factors there is a difference to be found in the strength of their force and the impact on an individual or group when they opt out. Choosing to not obey governmental law will probably have a big impact on your individual freedom, as to not participating in certain technological progress will also cut into your the freedom of your social interactions, but will rather have a smaller impact due to smaller influence of that grid on personal lives. &lt;br /&gt;
&lt;br /&gt;
==Off the grid==&lt;br /&gt;
Although grids can imply a lot of benefits for a participant like providing health care, ensuring safety and enabling efficient transportation, the same grids can imply more negative results than benefits for an individual. Deciding to go off the grid will enable an individual to function without the use of that particular remote support system. Going off-the-grid by choice is al lot of times the result of a conscious and extensive process of comparing the pro’s and con’s of this action. It can be in favor of this person’s or group’s privacy, independence, economic situation, environmental impact or ideology. Although there is the possibility to go off-grid by choice it can also be forced upon a person. It can be due to an inability to participate by, for example, remoteness, no available facilities, or an absence of resources. &lt;br /&gt;
Choosing collective or individual to go off-grid can not only have big impact on your personal environment but also on the external world. It can evoke change or undermine established grid and structures, since a grid needs its participants to enable its existence. &lt;br /&gt;
&lt;br /&gt;
==Advantages to (prepare to) go on or off grid for H&amp;amp;D==&lt;br /&gt;
With H&amp;amp;D we would like to challenge new and established grids that make up our environment. To do that we would like to examine questions as: What are the conflicts we encounter while participating in different grids? What kind of conflicts rise when we choose to go off the grid? How can we initiate processes that enable change in existing grids? How can we experiment and imagine a sustainable work method and environment that allows us to develop new technologies? How can we think about consequences of projects, research, and interventions we undertake? How can we embrace our interests in technology and experiment without turning our surroundings into Grey Goo? Can we use existing grids to find new working methods with different impacts? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As hackers, designers, artists or net-workers, there are a several grids that are almost inseparably connected to our professional and social environments. These grids seem to occur in four main categories: our way of communicating with each other, the valuation of our work, the facilities we use, and our own practice. As we observe a rise of conflicts in our environments in the fields of privacy, efficiency, monetary value system, time investment, resources, accommodation, transport, ecology, morals and methods, we are proposing to re-evaluate the grids we became accustomed to and take action to prepare ourselves and be ready to take position. Shall we participate or leave familiar grids and start a quest to look for alternative options and create new grids and solutions within our environment?&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20518</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20518"/>
		<updated>2017-02-13T15:21:21Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1]  we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grids there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids for Hackers&amp;amp;Designers==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids and their impact==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Going on and off the grid==&lt;br /&gt;
insert text &lt;br /&gt;
&lt;br /&gt;
outro&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20517</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20517"/>
		<updated>2017-02-13T15:20:50Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In 2017 Hackers&amp;amp;Designers will focus on the thematic thread and the process of going ‘off-the grid’,  – a crucial societal topic and ongoing discussion at stake in both design/art and developer practices. &lt;br /&gt;
To be able to reflect on the roles, meanings and impacts of the different grids we are navigating on as hackers and designers, this first article will give an overview of the nature of different grids, what they are, what they can be, where they come from, and what their impact is on our work- and personal environments. &lt;br /&gt;
This introductory article will be a very broad examination of what ‘a grid’ can mean to our social interactions. After this submersion into the world of grids, the following articles will have a case based way to approach the ‘wild’ grid with experimental curiosity and will be based on the outlines of this introduction.&lt;br /&gt;
&lt;br /&gt;
When looking up ‘grids’ in the Cambridge Dictionary [1]  we find that a grid is ‘a pattern or structure made from horizontal and vertical lines crossing each other to form squares.’  Since going off-grid for sure doesn’t mean stepping out of a graphical structure, a more clear explanation for the grids we can go on or off can be found in anthropologic studies and literature about cultural motives and infrastructures. &lt;br /&gt;
&lt;br /&gt;
Sociologist Lisa Wade describes these grids in her book “Gender” [2] as “persistent patterns of social interaction aimed at meeting the needs of a society that can’t easily be met by individuals alone”. Grid systems are there to provide a structure or connection between several people to be able to do things more efficiently, than we would be able when we would handle them alone. &lt;br /&gt;
Sociologists also tend to call these grids institutions and distinguish five main grids in our society: education, family, religion, polity, and economy. The problem with these big institutions is that once they are established, it’s almost impossible for an individual to step out from them and they are not always set up with the goal of meeting the needs of a society. &lt;br /&gt;
&lt;br /&gt;
A more accurate description of what grids can be was formulated by Shaun Hargreaves Heap and Angus Ross in “Understanding the enterprise culture” [3]: [A grid is]‘The set of rules which govern individuals in their personal interactions. Strong or “high” grid means strongly defined roles which provide a script for individual interaction.’&lt;br /&gt;
While Lisa Wade assumes that grids always have a serving position for society, the previous definition is neutral in its judgement on whether the intention or impact of those grids are designed or put into place to serve society, or at least a certain social group. &lt;br /&gt;
&lt;br /&gt;
While studying the nature of grid there is a strong impossibility to disconnect them from their relation with the participants. Without participants, there is no grid. A grid cannot exist without its initiators, actors, and participants. This relation between participants and grids is described as the grid/group theory by several anthropologists. &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids for Hackers&amp;amp;Designers==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids and their impact==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Going on and off the grid==&lt;br /&gt;
insert text &lt;br /&gt;
&lt;br /&gt;
outro&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20516</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20516"/>
		<updated>2017-02-12T21:24:14Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by a year theme H&amp;amp;D invites the public to reflect and question our daily work and living environments. From 2017, we are pleased to introduce a series of articles that will provide a theoretic context to our activities. &lt;br /&gt;
&lt;br /&gt;
As we are open for discussion and dialog, you’re always welcome to contact us [mailto:vicky@hackersanddesigners.nl here] with your thoughts, questions or contributions. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20515</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20515"/>
		<updated>2017-02-12T21:19:39Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by a year theme H&amp;amp;D invites the public to reflect and question our daily work and living environments as Hackers&amp;amp;Designers. From 2017, we are pleased to introduce a series of articles that will provide a theoretic context to our activities. &lt;br /&gt;
&lt;br /&gt;
As we are open for discussion and dialog, you’re always welcome to contact us [mailto:vicky@hackersanddesigners.nl here] with your thoughts, questions or contributions. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20514</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20514"/>
		<updated>2017-02-12T21:15:53Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by a year theme H&amp;amp;D invites the public to reflect and question our daily work and living environments as Hackers&amp;amp;Designers. We are pleased to introduce a series of articles that will provide a theoretic context to our activities. &lt;br /&gt;
&lt;br /&gt;
As we are open for discussion and dialog, you’re always welcome to contact us [mailto:vicky@hackersanddesigners.nl here] vicky@hackersanddesingers.nl with your thoughts, questions or contributions. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20513</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20513"/>
		<updated>2017-02-12T21:15:21Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by a year theme H&amp;amp;D invites the public to reflect and question our daily work and living environments as Hackers&amp;amp;Designers. We are pleased to introduce a series of articles that will provide a theoretic context to our activities. &lt;br /&gt;
&lt;br /&gt;
As we are open for discussion and dialog, you’re always welcome to contact us [vicky@hackersanddesigners.nl here] vicky@hackersanddesingers.nl with your thoughts, questions or contributions. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20512</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20512"/>
		<updated>2017-02-12T21:11:37Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;By developing an elaborate hands-on program guided by a year theme H&amp;amp;D invites the public to reflect and question our daily work and living environments as Hackers&amp;amp;Designers. Next to our hands-on workshops, we are pleased to introduce a series of articles that will provide a theoretic context to our activities. As we are open for discussion and dialog, you’re always welcome to contact us at vicky@hackersanddesingers.nl with your thoughts, questions or contributions. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017: Get prepped! Investigating means of going on and off the grid&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20511</id>
		<title>Grids:Remote support infrastructures</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Grids:Remote_support_infrastructures&amp;diff=20511"/>
		<updated>2017-02-12T16:29:23Z</updated>

		<summary type="html">&lt;p&gt;Vicky: Created page with &amp;quot;Intro   ==The Grid/group theory==  insert text  ==Grids for Hackers&amp;amp;Designers== insert text  ==Grids and their impact== insert text  ==Going on and off the grid== insert text...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Intro &lt;br /&gt;
&lt;br /&gt;
==The Grid/group theory== &lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids for Hackers&amp;amp;Designers==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Grids and their impact==&lt;br /&gt;
insert text&lt;br /&gt;
&lt;br /&gt;
==Going on and off the grid==&lt;br /&gt;
insert text &lt;br /&gt;
&lt;br /&gt;
outro&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20510</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20510"/>
		<updated>2017-02-12T16:18:09Z</updated>

		<summary type="html">&lt;p&gt;Vicky: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;intro articles. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017&#039;&#039;&#039;&lt;br /&gt;
*[[Grids:Remote support infrastructures|Grids: Remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20509</id>
		<title>Hackers &amp; Designers Research</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Hackers_%26_Designers_Research&amp;diff=20509"/>
		<updated>2017-02-12T16:16:51Z</updated>

		<summary type="html">&lt;p&gt;Vicky: Created page with &amp;quot;intro articles.   == H&amp;amp;D articles ==  &amp;#039;&amp;#039;&amp;#039;2017&amp;#039;&amp;#039;&amp;#039; *Grids_remote support infrastructures&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;intro articles. &lt;br /&gt;
&lt;br /&gt;
== H&amp;amp;D articles ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2017&#039;&#039;&#039;&lt;br /&gt;
*[[Grids_remote support infrastructures|Grids_remote support infrastructures]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=Main_Page&amp;diff=20508</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=Main_Page&amp;diff=20508"/>
		<updated>2017-02-12T15:35:30Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Hackers &amp;amp; Designers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;span style=&amp;quot;background:rgb(255, 255, 0);font-size:24pt&amp;quot;&amp;gt;Welcome to the Hackers &amp;amp; Designers wiki&amp;amp;ndash;content creator.&amp;lt;/span&amp;gt;&amp;lt;br/&amp;gt; This wiki is used as content management system for the H&amp;amp;D website (front-end implementation here [http://hackersanddesigners.nl here]) and as a co-publishing platform for on and offline publications.&lt;br /&gt;
&lt;br /&gt;
=Content=&lt;br /&gt;
&amp;lt;div style=&amp;quot;background:#99ff80;&amp;quot;&amp;gt; &lt;br /&gt;
==Hackers &amp;amp; Designers==&lt;br /&gt;
* [[Hackers_%26_Designers|About H&amp;amp;D]]&lt;br /&gt;
* [[HD-meet-ups|H&amp;amp;D meet-ups]]&lt;br /&gt;
* [[Hackers_%26_Designers_Summer_Academy|H&amp;amp;D Summer Academy]]&lt;br /&gt;
* [[Hackers_%26_Designers_Research|H&amp;amp;D Research]]&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to =&lt;br /&gt;
==edit this wiki==&lt;br /&gt;
&#039;&#039;&#039;If this is your first time writing and editing articles in a wiki&#039;&#039;&#039;   &lt;br /&gt;
&lt;br /&gt;
* have a look at the [[Wiki_Tutorial|Wiki tutorial]],&lt;br /&gt;
* or read the brief introduction about [[Want_to_join_us%3F|How to join us?]].&lt;br /&gt;
&lt;br /&gt;
==create a new page?==&lt;br /&gt;
* Use the [[Form:PeopleOrganisations]] to create an page for a person or organisation.&lt;br /&gt;
* Use the [[Form:AddOrEditEvent]] to create a page for and Event. eg, Meetup, Workshop Etc.&lt;br /&gt;
* After creating a page don&#039;t forget to link up/create the relevant pages (if you feel that way inclined) by clicking the &amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;&#039;&#039;&#039;RED&#039;&#039;&#039;&amp;lt;/span&amp;gt;  hyperlink to create a new page&lt;br /&gt;
* After using the form to create the initial page, you can choose to edit the page in the Wiki editor if you would like, by clicking the edit button to the top right of the page and, if you would like to use the creation/edit form again, simply click the Edit with Form button instead.&lt;br /&gt;
&lt;br /&gt;
=Process=&lt;br /&gt;
Ad one of those categories to every article, according to the state the article is in.&lt;br /&gt;
* [[:Category:WriteMe|WriteMe]]: Articles that need to be written&lt;br /&gt;
* [[:Category:EditMe|EditMe]]: Articles that need to be edited&lt;br /&gt;
* [[:Category:Ready_to_be_published|Ready to be published]]: Articles that are ready to publish&lt;br /&gt;
* [[:Category:Published|Published]]: Articles that have been published&lt;br /&gt;
* [[:Category:Print|Print]]: Artciles that will be printed&lt;br /&gt;
* [[:Category:Web|Web]]: Articles that will be published on the website&lt;br /&gt;
&lt;br /&gt;
==[[Collected matter]]==&lt;br /&gt;
&lt;br /&gt;
=To Do=&lt;br /&gt;
[[Terminal | Sandberg Terminal Workshop]]&lt;br /&gt;
&lt;br /&gt;
[[Python | Sandberg Python Workshop]]&lt;br /&gt;
&lt;br /&gt;
[[Thoughts on publishing and editorial design matters | Some thoughts on publishing and editorial design matters]]&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.wikimedia.org/p/hackdesign Real-time co-writing pad for general info and note collective taking]&lt;br /&gt;
&lt;br /&gt;
[[Published and Destroyed]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2255</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2255"/>
		<updated>2015-11-18T18:56:45Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
===H&amp;amp;D Wiki categories structure:===&lt;br /&gt;
&#039;&#039;&#039;State&#039;&#039;&#039; &lt;br /&gt;
* EditMe&lt;br /&gt;
* WriteMe&lt;br /&gt;
* Published&lt;br /&gt;
* Ready to be published&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
* Print&lt;br /&gt;
* Web&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
* eg Arduino&lt;br /&gt;
* eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1a. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
One way to publish a print publication from an online environment is printing a webpage by using CSS. A user can just click ‘Print Page’, a pop-up print preview will appear and the custom CSS will translate the webpage and media to a printable, in pages divided print publication.&lt;br /&gt;
The design is also made with code/text, which means that you can use text editors such as Etherpad to collaborate on content with several people at the same time. The negative side on using this set-up is that you if you decide to not use a single page website you’ll have to print each article separate and later bind it into a book. This way no table of contents will be created or there will be no option to apply different lay outing for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Differences Between CSS For The Web And CSS For Print &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You also have to consider the differences between a webpage and a printed publication. What will happen with image galleries, sliders, menu’s and the like? If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The back-end code in the browser needs to do heavy lifting to support all the requests coming from the front-end.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the back-end involves restructuring the HTML to support preview. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The user has to select a printer before a print render is generated for a preview. When printing, the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;From CSS and HTML to print with Prince.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After you prepared your HTML and CSS for the website, and the layout for the book is set with CSS, Prince or another API can be used for translating the HTML language to a PDF. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can download a free trial of the ‘Prince’ application and install it with ‘Terminal’. The Terminal runs ‘Prince’ and uses it to translate the website into a pdf. Prince is not an open source program but can be used as a trail. This means the front page of the pdf includes a logo of the prince software.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler: This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This WikiMedia plug-in allows previous compiled books to be added to the bookshelf. The bookshelves can be used to print previously published editions of a publication by other users. This way we can compile one &#039;official&#039; documentation book and let other people print it.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2242</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2242"/>
		<updated>2015-11-18T14:14:51Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* H&amp;amp;D Wiki categories structure: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
===H&amp;amp;D Wiki categories structure:===&lt;br /&gt;
&#039;&#039;&#039;State&#039;&#039;&#039; &lt;br /&gt;
* EditMe&lt;br /&gt;
* WriteMe&lt;br /&gt;
* Published&lt;br /&gt;
* Ready to be published&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
* Print&lt;br /&gt;
* Web&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
* eg Arduino&lt;br /&gt;
* eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1a. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
// edit It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Interaction&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 //edit You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1b. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
//edit&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler: This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
//edit &amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2240</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2240"/>
		<updated>2015-11-18T14:13:37Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Categorisation of the content */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
===H&amp;amp;D Wiki categories structure:===&lt;br /&gt;
&#039;&#039;&#039;State&#039;&#039;&#039; &lt;br /&gt;
* EditMe&lt;br /&gt;
* WriteMe&lt;br /&gt;
* Published&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1a. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
// edit It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Interaction&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 //edit You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1b. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
//edit&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler: This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
//edit &amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2238</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2238"/>
		<updated>2015-11-18T14:11:02Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1a. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
// edit It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Interaction&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 //edit You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1b. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
//edit&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler: This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
//edit &amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2237</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2237"/>
		<updated>2015-11-18T14:10:26Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1A. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
// edit It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Interaction&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 //edit You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1B. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
//edit&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler: This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
//edit &amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2234</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2234"/>
		<updated>2015-11-18T13:33:33Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1A. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Interaction&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1B. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 These are the basics how a book can be compiled using HTML and CSS. In doing so, we also developed a set of conventions for marking up a book in HTML. HTML has the wonderful class attribute which lets anyone extend the semantics of HTML documents while building on HTML’s universally known semantics. So, in our book, we used a rich set of HTML elements and added a bunch of-class names. This is how we developed a microformat for books.&lt;br /&gt;
From CSS and HTML to print with Prince. &lt;br /&gt;
Now that the HTML and CSS is ready for the website and the layout for the book is set with CSS, Prince or another API can be used for translating the HTML language to a PDF. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;API’s&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Prince&lt;br /&gt;
Download the ‘Prince’ application and install it with ‘Terminal’. &lt;br /&gt;
The Terminal runs ‘prince’ and translates it to a pdf. Prince is not an open source program but can be used as a trail. This means the front page of the pdf includes a logo of the prince software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
&amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2232</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2232"/>
		<updated>2015-11-18T13:33:08Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1A. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
Interaction You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1B. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 These are the basics how a book can be compiled using HTML and CSS. In doing so, we also developed a set of conventions for marking up a book in HTML. HTML has the wonderful class attribute which lets anyone extend the semantics of HTML documents while building on HTML’s universally known semantics. So, in our book, we used a rich set of HTML elements and added a bunch of-class names. This is how we developed a microformat for books.&lt;br /&gt;
From CSS and HTML to print with Prince. &lt;br /&gt;
Now that the HTML and CSS is ready for the website and the layout for the book is set with CSS, Prince or another API can be used for translating the HTML language to a PDF. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;API’s&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Prince&lt;br /&gt;
Download the ‘Prince’ application and install it with ‘Terminal’. &lt;br /&gt;
The Terminal runs ‘prince’ and translates it to a pdf. Prince is not an open source program but can be used as a trail. This means the front page of the pdf includes a logo of the prince software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
* Service&lt;br /&gt;
* Bundler This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
* Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
* Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
* Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
* User needs to know the commands for the LaTex mark-up&lt;br /&gt;
* LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
* LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
* pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
&amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2231</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2231"/>
		<updated>2015-11-18T13:31:32Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Publishing print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1A. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
Interaction You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1B. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 These are the basics how a book can be compiled using HTML and CSS. In doing so, we also developed a set of conventions for marking up a book in HTML. HTML has the wonderful class attribute which lets anyone extend the semantics of HTML documents while building on HTML’s universally known semantics. So, in our book, we used a rich set of HTML elements and added a bunch of-class names. This is how we developed a microformat for books.&lt;br /&gt;
From CSS and HTML to print with Prince. &lt;br /&gt;
Now that the HTML and CSS is ready for the website and the layout for the book is set with CSS, Prince or another API can be used for translating the HTML language to a PDF. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;API’s&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Prince&lt;br /&gt;
Download the ‘Prince’ application and install it with ‘Terminal’. &lt;br /&gt;
The Terminal runs ‘prince’ and translates it to a pdf. Prince is not an open source program but can be used as a trail. This means the front page of the pdf includes a logo of the prince software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Offline content generator the package:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
*Service&lt;br /&gt;
*Bundler&lt;br /&gt;
&amp;gt; This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
*Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
	•	Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
	•	Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
	•	User needs to know the commands for the LaTex mark-up&lt;br /&gt;
	•	LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
	•	LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
	•	pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
&amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2226</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2226"/>
		<updated>2015-11-18T13:10:47Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Making the documentation public: publishing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Workflow====&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to website====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
====Translation Wiki to print====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Publishing web===&lt;br /&gt;
Write. James? Lucian?&lt;br /&gt;
&lt;br /&gt;
===Publishing print===&lt;br /&gt;
&#039;&#039;&#039;1A. Web to print: HTML to Print with CSS and print preview&#039;&#039;&#039;&lt;br /&gt;
It may seem a bit strange that content not particularly destined for the web should be maintained as HTML and formatted with CSS. HTML becomes  a handy format to standardise on, far easier to deal with than having everything in a Word document or a traditional desktop publishing package.&lt;br /&gt;
The most exciting reason to use HTML/CSS is the fact that you can go back and forth between code and visual manipulation thanks to the element inspector of browsers. With Javascript on top of it, you can access every object in the DOM and its properties or do programmatic manipulations. This back-and-forth between hand and code manipulations is new to print production.&lt;br /&gt;
The second strong reason for this set-up is that because the design is made with code/text, it means you can use collaborative text editors such as Etherpad to design with several people at the same time.&lt;br /&gt;
The negative side on using this set-up is that you if you decide to not use a singel page website you’ll have to print each article separate and later bind it into a book. &lt;br /&gt;
This way no table of contents will be created or there will be no different layouts created for indexes, special chapters, or glossaries. &lt;br /&gt;
&lt;br /&gt;
Interaction You also have to consider what’s going to happen with image sliders and the like. If your webpage has a slideshow with ten images at the top, that’s not going to translate well to paper. The most basic level of interaction on the web is a link. This too becomes problematic. On your computer, you can simply click a link to see where it goes, on paper this functionality is lost so you need a good way to take all those inline links and show the reader where they lead.&lt;br /&gt;
 The Differences Between CSS For The Web And CSS For Print&lt;br /&gt;
The biggest difference, and conceptual shift, is that printed documents refer to a page model that is of a fixed size. Whereas on the web we are constantly reminded that we have no idea of the size of the viewport, in print the fixed size of each page has a bearing on everything that we do. Due to this fixed page size, we have to consider our document as a collection of pages, paged media, rather than the continuous media that is a web page.&lt;br /&gt;
Paged media introduces concepts that make no sense on the web. For example, you need to be able to generate page numbers, put chapter titles in margins, break content appropriately in order that figures don’t become disassociated from their captions. You might need to create cross-references and footnotes, indexes and tables of content from your document. You could import the document into a desktop publishing package and create all of this by hand, however, the work would then need redoing the next time you update the copy. This is where CSS comes in, whose specifications are designed for use in creating paged media.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Print Preview&#039;&#039;&#039;&lt;br /&gt;
When you want to print your website a print preview window appears. The backend code in the browser process needs to do the heavy lifting to support all the requests coming from the front end.&lt;br /&gt;
To start, the browser process needs to get the list of printers and printer options using platform specific APIs. Cloud print already has code to generate html options code from a PPD/XPS, which is useful here. Though to make this work on Windows XP, which does support XPS, the browser also need to be able to query for common options from printers.&lt;br /&gt;
&lt;br /&gt;
The majority of the work in the backend involves restructuring the messy printing pipeline to support preview. The current Linux printing pipeline works differently from Windows and Mac. Once all the platforms are brought in line, the printing pipeline needs to be broken up into two pieces: PDF generation and printing. The current printing pipeline waits for the user to select a printer before generating the print output using platform specific code and sending the output to the printer. The actual printing process uses pipelining: the renderer generates printing metadata one page at a time, so it can generate them while the PrintJobWorker in the browser process sends them to the printer at the same time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1B. Web to print: HTML to Print with CSS and Prince&#039;&#039;&#039;&lt;br /&gt;
The book These are the basics how a book can be compiled using HTML and CSS. In doing so, we also developed a set of conventions for marking up a book in HTML. HTML has the wonderful class attribute which lets anyone extend the semantics of HTML documents while building on HTML’s universally known semantics. So, in our book, we used a rich set of HTML elements and added a bunch of-class names. This is how we developed a microformat for books.&lt;br /&gt;
From CSS and HTML to print with Prince. &lt;br /&gt;
Now that the HTML and CSS is ready for the website and the layout for the book is set with CSS, Prince or another API can be used for translating the HTML language to a PDF. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;API’s&#039;&#039;&#039;&lt;br /&gt;
Prince&lt;br /&gt;
Download the ‘Prince’ application and install it with ‘Terminal’. &lt;br /&gt;
The Terminal runs ‘prince’ and translates it to a pdf. Prince is not an open source program but can be used as a trail. This means the front page of the pdf includes a logo of the prince software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Wiki to print&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&#039;Collection and the Offline Content Generator&#039;&#039;&#039;&lt;br /&gt;
After doing some research we found out that WikiMedia had already developed an open source plug-in, called Collections created by The Wiki Publisher Project.The extension makes it possible to select pages to create pdf’s or compile books. The user can create different chapters and arrange articles. Then the compiled pages are send to the OCG (Offline Content Generator). The OCG invokes a /Bundler to spider the articles and fetch all images, stylesheets, etc required to render them. One of several /Backends are then invoked to convert the bundle into a PDF, ZIM file, or other appropriate output format. This convertion to a pdf happens on wiki servers. We wanted to use this open source plug-in and adjust the code to fit our needs. (eg layout, page size, content table,…) &lt;br /&gt;
&lt;br /&gt;
For rendering on your own server (not using the wiki content generator) we installed the Offline Content Generator. This way we were able to change the layout of the output files. (pdf’s) &lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Offline content generator the package:&#039;&#039;&#039; &lt;br /&gt;
*Service&lt;br /&gt;
*Bundler&lt;br /&gt;
&amp;gt; This tool grabs all the dependencies for a given set of articles and creates a directory or zip file. &lt;br /&gt;
*Latexer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Latex&#039;&#039;&#039;&lt;br /&gt;
LaTex is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is available as free language.&lt;br /&gt;
	•	Several extensions are available for LaTex called: ‘packages’ or ‘styles’ (better image placement, implementation of mathematic formula,...)&lt;br /&gt;
	•	Create a text file in LaTex mark-up, which LaTex reads to produce the final document.&lt;br /&gt;
	•	User needs to know the commands for the LaTex mark-up&lt;br /&gt;
	•	LaTex automatically adjusts fonts, text size, line heights or text flow.&lt;br /&gt;
	•	LaTex is not flexible for lay outing, but you’re able to write your own macro’s or download them from others at CTAN &lt;br /&gt;
	•	pdfTex: engine or pdf compiler. This converts the LaTeX mark-up to a pdf.&lt;br /&gt;
&lt;br /&gt;
To be able to use the LaTeX mark-up, you have to install LaTeX distribution and an Editor. We used the TexMaker editor for Mac because this editor enables you to see quick previews of the Pdf file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookshelf&#039;&#039;&#039;&lt;br /&gt;
Previous compiled books are added to the of a registered user on the wiki page. The bookshelves can be used to print previously published editions of a publication.&lt;br /&gt;
&amp;gt; good for Hackers and Designers because….. &amp;lt;&amp;lt;&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Pandoc&#039;&#039;&#039; &lt;br /&gt;
This program converts files from one mark-up language to another. In this case, we used it convert the WikiMedia mark-up to HTML for our website, and to LaTex mark-up for the print publication.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mark-up&#039;&#039;&#039; &lt;br /&gt;
A mark-up language is a notation used to annotate a document’s content to give information regarding the structure of the text or instructions for how it is to be displayed. &lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2223</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2223"/>
		<updated>2015-11-18T13:06:45Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Categorisation of the content */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;State&#039;&#039;&#039;&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Media&#039;&#039;&#039;&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&#039;&#039;&#039;Topic / Tags&#039;&#039;&#039;&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2222</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2222"/>
		<updated>2015-11-18T13:06:12Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Categorisation of the content */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|State&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Media&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Topic / Tags&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2221</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2221"/>
		<updated>2015-11-18T13:05:54Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Categorisation of the content */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|State&lt;br /&gt;
|EditMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|WriteMe&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Ready to be published&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Media&lt;br /&gt;
|Print&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|Web&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Topic / Tags&lt;br /&gt;
|eg Arduino&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2220</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2220"/>
		<updated>2015-11-18T13:03:21Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Making the documentation public: publishing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2219</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2219"/>
		<updated>2015-11-18T13:02:58Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Translation Wiki to print */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2217</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2217"/>
		<updated>2015-11-18T13:02:44Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Translation Wiki to website */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2216</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2216"/>
		<updated>2015-11-18T13:02:33Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Making the documentation public: publishing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2215</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2215"/>
		<updated>2015-11-18T13:01:49Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Making the documentation public: publishing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
After building and filling our back-end documentation platform we had to translate the content to a website and print publication format. For print we looked into two options: creating a publication from the website and creating a publication directly from the WikiMedia page. The process will be discussed here. &lt;br /&gt;
&lt;br /&gt;
===Currently used set-up===&lt;br /&gt;
&#039;&#039;&#039;Hackers &amp;amp; Designers documentation platform.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Back-End&lt;br /&gt;
|WikiMedia Page&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Front-End&lt;br /&gt;
|Website of Hackers &amp;amp; Designers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Print publication&lt;br /&gt;
|Generated from the wiki&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
===Workflow===&lt;br /&gt;
organisation &amp;gt; preparation &amp;gt; communication &amp;gt; collaborative note taking and input assembly &amp;gt; editing &amp;gt; publication &amp;gt; printing &amp;gt; distribution  &lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to website===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki-markup to the HTML markup language&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Lay-out website&lt;br /&gt;
|CSS&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
===Translation Wiki to print===&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Pandoc&lt;br /&gt;
|translates wiki markup to LaTeX mark-up&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|Python Scripts&lt;br /&gt;
|Initiates several actions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|LaTeX&lt;br /&gt;
|Lay-outing of content from WikiMedia page and generating PDF&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
	<entry>
		<id>https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2208</id>
		<title>How to document a summer academy</title>
		<link rel="alternate" type="text/html" href="https://wiki.hackersanddesigners.nl//index.php?title=How_to_document_a_summer_academy&amp;diff=2208"/>
		<updated>2015-11-18T12:48:51Z</updated>

		<summary type="html">&lt;p&gt;Vicky: /* Categorisation of the content */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Choosing the right technical workflow for your hybrid publication&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;[[Vicky De Visser]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Content creation==&lt;br /&gt;
Before planning on how to gather the documentation we had to ask ourselves: what is to be documented? &lt;br /&gt;
&lt;br /&gt;
There are three different moment where content can be created and has to be documented: &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Although the academy wasn’t started yet, there was already a lot of content that was generated by the organising staff. They did research, choose a subject, plan schedules and dates, get the word out by printed and online media and process motivations of applicants. It can be good to already document this process. By documenting the organisation flow you can create a base or structure for the upcoming summer school program and it is useful for sharing information about the future academy with applicants. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;During the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
During the summer academy different formats of content were provided to the students. Analyse and estimate this before your academy starts. This way you can start looking for a suitable platform where everything can be documented. It wil save you a lot of time after the summer school is finished. &lt;br /&gt;
Organising this summer academy was our first time and we had to learn the hard way. It took us quiet some time to set up a good platform after the summer academy was over. &lt;br /&gt;
&lt;br /&gt;
For collaborative note taking we experimented with Pirate Pad and Ether Pad. Both are online text editors where different users can take and edit notes in the same document. We really liked these editors.&lt;br /&gt;
&lt;br /&gt;
Pictures were taken both by the organisation as participants. After the academy we had to email every participant several times to ask them to send their pictures. Using a platform that can be used during the academy can make it easier to upload the photo’s or other content at once. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;After the summer academy&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
After the academy is finished, you can ask participants and teachers to write a review. This can be helpful feedback if you want to organise an other one the year after.&lt;br /&gt;
&lt;br /&gt;
==Choosing the right back-end to collect the documentation==&lt;br /&gt;
To compile all the content we wanted to bundle co-writing, co-editing and content management all on the same platform. We looked for a back-end where we could do some real time documenting on, that was easy accessible, had a good way of ordering information, had a short learning curve for participants and supported several kinds of mediafiles. &lt;br /&gt;
The lectures, workshops, screenings, excursions, party and exhibition provided a big variety of media such as videos, sound files, notes, images, and code as well as objects and long texts that wouldn’t be suitable for only an online publication. &lt;br /&gt;
&lt;br /&gt;
For this task we chose to use WikiMedia. It supports the several file formats and is easy editable by different users. It’s easy understandable structure and user guide is beneficial for changing collaborations and teams. This academy we didn’t have the opportunity to test WikiMedia as a back-end and content collector for students to upload their content as a WikiMedia page because we still had to built it. We used it after the academy to gather the information collected by writing emails and uploading code and pictures to a dropbox repository. During this filling of our WikiMedia back-end we encountered several hierarchy and workflow problems.&lt;br /&gt;
&lt;br /&gt;
==Categorisation of the content==&lt;br /&gt;
&lt;br /&gt;
We wanted to sort the documentation to be able to publish a well structured and logic documentation. We sorted the content by categorising the WikiMedia pages. Andre Castro recommended us to use a categorisation system sorted by state, media and topic. &lt;br /&gt;
&lt;br /&gt;
Because not all media such as videos, sound files and links aren’t suitable for print publication we added a media category so we could divide articles in a suitable print version and not suitable print version. &lt;br /&gt;
&lt;br /&gt;
It is important to consider that making a structure can inherit the danger of guiding the contributed content too much. Leave space for adding things that weren’t thought of before. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;H&amp;amp;D Wiki categories structure:&#039;&#039;&#039;&lt;br /&gt;
State&lt;br /&gt;
	•	EditMe&lt;br /&gt;
	•	WriteMe‏‎ &lt;br /&gt;
	•	Published&lt;br /&gt;
	•	Ready to be published&lt;br /&gt;
&lt;br /&gt;
Media&lt;br /&gt;
	•	print&lt;br /&gt;
	•	web&lt;br /&gt;
&lt;br /&gt;
Topic / Tags&lt;br /&gt;
	•	eg Arduino&lt;br /&gt;
	•	eg HTML 2 Print&lt;br /&gt;
&lt;br /&gt;
==Co-editing==&lt;br /&gt;
After receiving the contributions, the organisation and participants must then select the most viable and implementable ones. The challenge of the selection process is that most submissions are not always useful, have an other hierarchy or are difficult to implement in the publication. Organisations have to deal with the submitted ideas in a very subtle way as throughout the process they don’t want to reject submissions and risk of alienating them which may eventually lead to disengagement.&lt;br /&gt;
It’s advised to give the participants a short introduction in how to collect and document the content. This way the organisers can prevent an extensive editing process afterwards. &lt;br /&gt;
&lt;br /&gt;
Wikimedia let’s users adjust articles and write comments on the changes that were made in an article. Participants have the possibility to go back in time and compare older versions of the same article. This way content will not get lost after over-editing an article. &lt;br /&gt;
&lt;br /&gt;
==Making the documentation public: publishing==&lt;br /&gt;
&lt;br /&gt;
[[Category:DIY Manual]]&lt;br /&gt;
[[Category:WriteMe]]&lt;br /&gt;
[[Category:Print]]&lt;/div&gt;</summary>
		<author><name>Vicky</name></author>
	</entry>
</feed>