https://ps.wdka.nl/wiki/api.php?action=feedcontributions&feedformat=atom&user=Lucia+Dossin 2026-04-11T05:27:30Z User contributions MediaWiki 1.45.1 https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1769 2015-08-08T08:06:58Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> * '''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house<br /> &lt;/div&gt;<br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[Pcounter]]''' - Printing from a Macbook to the MFP (xerox)<br /> * '''[[Printstudio]]'''<br /> * '''[[Letterpress]]'''<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[The Software HUB]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1732 2015-07-10T14:34:52Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1731 2015-07-10T13:58:50Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> &lt;p style=&quot;text-align: center; width: 480px;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;Publication Station rules.&lt;/p&gt;<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1730 2015-07-10T13:58:35Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> &lt;p style=&quot;text-align: center; width: 600px;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;Publication Station rules.&lt;/p&gt;<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1729 2015-07-10T13:58:01Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> &lt;p style=&quot;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;Publication Station rules.&lt;/p&gt;<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1728 2015-07-10T13:52:57Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1727 2015-07-10T13:51:33Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =&lt;span style=&quot;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;Publication Station Wiki - &lt;/span&gt;&lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1726 2015-07-10T13:50:19Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1725 2015-07-10T13:49:57Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px;font-family: 'Comic Sans MS',cursive,sans-serif !important;&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1724 2015-07-10T13:49:35Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px;font-family: 'Comic Sans MS',cursive,sans-serif !important&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1723 2015-07-10T13:45:57Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1722 2015-07-10T13:45:47Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px; font-family: 'Comic Sans MS'&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1721 2015-07-10T13:44:42Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1720 2015-07-10T13:44:22Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px; font-family: 'Comic Sans'&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1719 2015-07-10T13:44:01Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px; font-family: Comic Sans&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Alternatieve_Software&diff=1718 2015-07-10T10:27:04Z

<p>Lucia Dossin: /* Externe artikelen over alternatieven software */</p> <hr /> <div>== Alternatieve Software ==<br /> <br /> Deze pagina bevat een lijst voor mogelijke alternatieve software tegenhangers van bijvoorbeeld '''Adobe en Autodesk'''<br /> <br /> ===Beeldbewerkings Software:===<br /> *[http://www.pixelmator.com/ Pixelmator]<br /> *[https://affinity.serif.com/en-gb/ Affinity Designer]<br /> *[https://affinity.serif.com/en-gb/photo/ Affinit Photo]<br /> *[http://www.bohemiancoding.com/sketch/ Sketch]<br /> <br /> ===3D Software===<br /> *[http://3d-coat.com/ http://3d-coat.com/]<br /> <br /> ==Open source software==<br /> *[http://gimp.org Gimp]<br /> *[http://inkscape.org Inkscape]<br /> *[http://sk1project.org sK1 Project]<br /> *[http://www.blender.org Blender]<br /> *[http://www.scribus.net/ Scribus]<br /> <br /> ==Externe artikelen over alternatieven software==<br /> *[http://www.sitepoint.com/linux-design-tools/ sitepoint.com/linux-design-tools]<br /> *[http://artistx.org/blog/software/ Artistx/software] Artistx is een linux multimedia studio distributie.<br /> *[http://wiki.scribus.net/canvas/Scribus Scribus How To's]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Alternatieve_Software&diff=1717 2015-07-10T10:26:31Z

<p>Lucia Dossin: /* Open source software */</p> <hr /> <div>== Alternatieve Software ==<br /> <br /> Deze pagina bevat een lijst voor mogelijke alternatieve software tegenhangers van bijvoorbeeld '''Adobe en Autodesk'''<br /> <br /> ===Beeldbewerkings Software:===<br /> *[http://www.pixelmator.com/ Pixelmator]<br /> *[https://affinity.serif.com/en-gb/ Affinity Designer]<br /> *[https://affinity.serif.com/en-gb/photo/ Affinit Photo]<br /> *[http://www.bohemiancoding.com/sketch/ Sketch]<br /> <br /> ===3D Software===<br /> *[http://3d-coat.com/ http://3d-coat.com/]<br /> <br /> ==Open source software==<br /> *[http://gimp.org Gimp]<br /> *[http://inkscape.org Inkscape]<br /> *[http://sk1project.org sK1 Project]<br /> *[http://www.blender.org Blender]<br /> *[http://www.scribus.net/ Scribus]<br /> <br /> ==Externe artikelen over alternatieven software==<br /> *[http://www.sitepoint.com/linux-design-tools/ sitepoint.com/linux-design-tools]<br /> *[http://artistx.org/blog/software/ Artistx/software] Artistx is een linux multimedia studio distributie.</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1716 2015-07-10T07:58:18Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1715 2015-07-10T07:56:27Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC ; width:600px;&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1714 2015-07-10T07:55:43Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC ; width:600px;&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario_jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1713 2015-07-10T07:55:07Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC url('http://publicationstation.wdka.hro.nl/wiki/images/7/79/Mario-jackson.gif') no-repeat; width:600px; height: 400px;&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> <br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1712 2015-07-10T07:54:32Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC url('http://publicationstation.wdka.hro.nl/wiki/images/7/79/Mario-jackson.gif') no-repeat;width:600px;&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1711 2015-07-10T07:53:29Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> * [[software|publication station Software]]<br /> * [[Devicelab]]<br /> * [[Presentations]]<br /> &lt;/div&gt;<br /> [[File:Mario-jackson.gif]]<br /> <br /> http://pzwiki.wdka.nl/mediadesign/Help:Graduation_work</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=File:Mario-jackson.gif&diff=1710 2015-07-10T07:52:04Z

<p>Lucia Dossin: </p> <hr /> <div></div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1537 2015-07-08T09:03:10Z

<p>Lucia Dossin: /* Responsive web CSS */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print (a pdf). Our goal was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using Pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and leaving only structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for responsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In Word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a better (semantic) structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually.<br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be linear and many interactive posibilities open up. We decided to keep the website largely linear because it seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the footnotes were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, as this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all mobile websites. Even though these challenges also belong to our research topic, they do not represent the most innovative aspects of it. For this reason, documentation regarding this output seems redundant to us.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1536 2015-07-08T09:02:35Z

<p>Lucia Dossin: /* Responsive web CSS */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print (a pdf). Our goal was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using Pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and leaving only structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for responsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In Word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a better (semantic) structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually.<br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be linear and many interactive posibilities open up. We decided to keep the website largely linear because it seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the footnotes were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, as this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all mobile websites. Even though these challenges also belong to our research topic, they do not represent the most innovative aspects of it. For this reason, documentation regarding this output seems redundant.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1533 2015-07-08T08:52:00Z

<p>Lucia Dossin: /* Web CSS */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print (a pdf). Our goal was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using Pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and leaving only structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for responsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In Word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a better (semantic) structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually.<br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be linear and many interactive posibilities open up. We decided to keep the website largely linear because it seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the footnotes were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, as this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1532 2015-07-08T08:47:55Z

<p>Lucia Dossin: /* About the process */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print (a pdf). Our goal was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using Pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and leaving only structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for responsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In Word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a better (semantic) structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually.<br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1531 2015-07-08T08:45:34Z

<p>Lucia Dossin: /* Cleaning up the HTML */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In Word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a better (semantic) structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually.<br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1526 2015-07-08T08:21:46Z

<p>Lucia Dossin: /* Introduction */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design can be exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1525 2015-07-08T08:18:46Z

<p>Lucia Dossin: /* Introduction */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is then made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=File:All-in-one-publishing-pdf.pdf&diff=1488 2015-06-26T12:20:54Z

<p>Lucia Dossin: Lucia Dossin uploaded a new version of &amp;quot;File:All-in-one-publishing-pdf.pdf&amp;quot;</p> <hr /> <div></div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1487 2015-06-26T09:32:25Z

<p>Lucia Dossin: /* About the process */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is than made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait of this iteration. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1486 2015-06-26T09:31:54Z

<p>Lucia Dossin: /* About the process */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is than made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits list in github can be a good portrait. Available at: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1485 2015-06-26T09:30:56Z

<p>Lucia Dossin: /* About the process */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is the development a workflow in which HTML and CSS files are used as the primary source for a publication. This publication is than made available for print, epub and a responsive website. This approach was chosen because it can potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For largely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created and tested using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously. The commits can be a good portrait: https://github.com/arjensuijker/all-in-one-publishing/commits/master<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> [[File:Pdf annotations.jpg]]<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similar. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> This resulted in the following command for windows:<br /> <br /> &lt;source lang=&quot;winbatch&quot;&gt;<br /> type &quot;css\style.css&quot; &quot;css\epub.css&quot; &quot;css\print.css&quot; &gt; &quot;css\epub_composite.css&quot;<br /> pandoc container.html -o book.epub --epub-cover-image=img\cover.jpg --epub-stylesheet=css\epub_composite.css<br /> &lt;/source&gt;<br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future research subject is the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render them obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |(RESPONSIVE) WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1484 2015-06-26T07:20:14Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas|Browser as your Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted|Wordpress Basics - Self-hosted]]<br /> * [[Courses/Wordpress-Intermediate |Wordpress Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> <br /> [[File:Pope_pubSt.jpg|330px|center]]<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> *[[software|publication station Software]]<br /> *[[Devicelab]]<br /> &lt;/div&gt;</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Main_Page_Old&diff=1483 2015-06-26T07:19:16Z

<p>Lucia Dossin: </p> <hr /> <div>__NOEDITSECTION__ __NOTOC__<br /> [[File:Guttenberg.jpg|right]]<br /> <br /> &lt;div style=&quot;background:#FF27DD;width:600px&quot;&gt;<br /> =Publication Station Wiki - &lt;span style=&quot;color:white&quot;&gt;publicationstation.wdka.hro.nl/wiki&lt;/span&gt;=<br /> &lt;/div&gt;<br /> <br /> * &lt;span style=&quot;background:#FF6600&quot;&gt;'''[[Pcounter]]''' - Printen vanaf een Macbook naar de MFP (xerox kopieermachines) in het Publication Station&lt;/span&gt;<br /> <br /> * &lt;span style=&quot;background:#00FFCC&quot;&gt;'''[[Publisher:Main_Page|Publisher]]''' - WdKA experimental publishing house &lt;/span&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Tutorials &amp; Resources==<br /> * '''[[Grafiwiki]]''' - online resource on graphic techniques (mainly in Dutch)<br /> * '''[[tutorials/wiki tutorial|wiki tutorial]]''' - how to edit this wiki<br /> <br /> * [[publicationstation|Publication Station beschrijvingen]]<br /> * [[lasercutter|Publication Station Laser Cutter]]<br /> * [[Alternatieve Software|Alternatieve Software]]<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Teaching Material: Open Aanbod / Open Courses / Workshops==<br /> * [[Courses/EPUB|EPUB Essentials]]<br /> * [[Courses/Essential HTML|Essential HTML]] <br /> * [[Courses/Schijt aan je Site|Schijt aan je Site]]<br /> * [[Courses/all-in-one publishing|All-in-one publishing]]<br /> * [[Courses/Weg met het Web|Weg met het Web]]<br /> * [[Courses/Interactief Visueel Vertellen|Interactief Visueel Vertellen]]<br /> * [[Courses/Pielen met Plotters|Pielen met Plotters]]<br /> * [[Data_Scraping]]<br /> * [[Courses/Browser as Canvas]]<br /> * [[Courses/Web to Print|Web to Print]]<br /> * [[Courses/Hybrid publishing resources|Hybrid publishing resources]]<br /> * [[Courses/Wikis-Publishing Platforms|Wikis as Publishing Platforms]]<br /> * [[Courses/single-page-portfolio|single-page-portfolio]]<br /> * [[Courses/Wordpress-Basics2-self-hosted]]<br /> * [[Courses/Wordpress-Intermediate]]<br /> [[File:animpnky_e0.gif|right]]<br /> ===Proposals for future courses===<br /> * [[Courses/Essential_tools_for_digital_publishing]]<br /> * [[Courses/Hybrid Publishing]]<br /> ''[[Courses]] - all child pages of Courses<br /> ''&lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Research==<br /> &lt;DynamicPageList&gt;<br /> category= Research<br /> &lt;/DynamicPageList&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==On-going Projects==<br /> * &lt;span style=&quot;background:#CCFF66&quot;&gt;'''[http://beyond-social.org/ Beyond Social]'''&lt;/span&gt; is an (online and physical) magazine that offers a platform for challenging and engaging design and art practices. Contributers collective create the content for the magazine via an open * [http://beyond-social.org/wiki/index.php/Main_Page wiki]. The project results from a collaborative effort between '''[http://wdka.nl/ Willem de Kooning Academie's] Social Practices program &amp; the Publication Station'''. <br /> * &lt;span style=&quot;background:-webkit-linear-gradient(#00fbe6, #CCFF66);&quot;&gt;'''[http://publicationstation.wdka.hro.nl/wiki/index.php/FIN:Main_Page FIN Magazine]'''&lt;/span&gt; is a testing page for FIN alumni magazine editors. <br /> &lt;/div&gt;<br /> <br /> <br /> <br /> <br /> [[File:Pope_pubSt.jpg|330px|center]]<br /> <br /> &lt;div style=&quot;background:#00FFCC;width:600px&quot;&gt;<br /> ==Staff stuff==<br /> *[[software|publication station Software]]<br /> *[[Devicelab]]<br /> &lt;/div&gt;</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1445 2015-06-24T14:13:10Z

<p>Lucia Dossin: /* Collaboration */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is developing a workflow in which HTML and CSS is used as the source for a publication. This publication is than available for print, epub and for a responsive website. This approach was chosen because it could potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For larely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously.<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> &lt;span style=&quot;background-color: yellow; font-size: .75em; font-weight: bold;&quot;&gt; -&gt; add screenshot - pdf &amp; annotations (Arjen, my pdf reader doesn't show annotations - I can make one screenshot later on a mac. If not, could you please make one?)&lt;/span&gt;<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similair. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> &lt;span style=&quot;background-color: yellow; font-size: .75em; font-weight: bold;&quot;&gt;place the css merge command here?&lt;/span&gt;<br /> <br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in parallel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future direction is a research into the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render it obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Research/all-in-one_publishing&diff=1444 2015-06-24T14:12:03Z

<p>Lucia Dossin: /* Adding semantic structure and classes */</p> <hr /> <div>== Introduction ==<br /> <br /> The core of our research is developing a workflow in which HTML and CSS is used as the source for a publication. This publication is than available for print, epub and for a responsive website. This approach was chosen because it could potentially improve the publication workflow for the following reasons:<br /> <br /> * Both the design and the content can be updated at any time, fully independently of each other. <br /> * Every update in content or design is automatically exported to every available publication medium.<br /> * HTML and CSS are very widespread transparent file formats that have been used for decades without much change, and will remain this way for years to come. This makes them much more suitable for digital archiving than most proprietary formats.<br /> * For larely the same reasons, the resulting publication is very suitable for (collaborative) reuse and redesign. <br /> <br /> === About the process ===<br /> <br /> For this research, we have chosen to take an existing publication and explore how it could be rebuilt from scratch using our newly developed workflow. The original publication was only designed for print. Our goals was to replicate this design as closely as possible with our new print version, and adapt the design to also fit the other media. <br /> <br /> The global process consisted of the following steps:<br /> <br /> # The original Word documents with the contents of the publication were converted to html files using pandoc conversion software.<br /> # These html files were 'cleaned up', deleting everything design-related and only leaving structural information.<br /> # Additional HTML was added to improve semantic value and facilitate CSS styling. <br /> # CSS stylesheets were created for every output format.<br /> # The outputs were created using Pandoc (for epub), PrinceXML and Weasyprint (for pdf), Chrome (for reposponsive web) and Firefox (for direct browser print) and checked for consistency. PrinceXML is proprietary software, Weasyprint is not.<br /> <br /> Of course the process wasn't as linear as it appears here. The process can be better described as being iterative, looping through the steps continuously.<br /> <br /> == Challenges ==<br /> <br /> Because we are off the beaten tracks for the duration of this research, we encountered many challenges that didn't have readily available solutions. We will discuss the challenges for every step of our process:<br /> <br /> === From Word to HTML ===<br /> At this stage, we encountered very little problems. Pandoc proved easy to install and worked flawlessly.<br /> <br /> === Cleaning up the HTML ===<br /> In word, there are basically two methods to style a document: using styles or by manually changing the font properties for every heading and paragraph. The first method results in html files with a great structure, because the styles can directly translated to HTML tags. The second method creates very messy HTML files that require lots of cleaning because the HTML is littered with unnecessary styling information. The documents that we used as the source were somewhere in between: most styling was done correctly, but a lot of manual cleaning was still needed. Additionally, most figures had to be extracted manually. <br /> <br /> === Adding semantic structure and classes ===<br /> Before we started adding this information to the HTML, we walked through the publication. Together we decided what would be the correct semantic structure and added this as annotations to the file. We could then work in a parallel fashion, individually implementing the structure in the html files. An issue we encountered while defining the structure is that most semantic HTML elements are aimed at the web, so deciding on a suitable semantic structure for both print and web was often a matter of compromise. Because we knew what design we were aiming at, it was easier for us to decide what elements should have classes and which should not. If the design is not ready yet, this may be more of a challenge and will probably change during the course of the project.<br /> <br /> &lt;span style=&quot;background-color: yellow; font-size: .75em; font-weight: bold;&quot;&gt; -&gt; add screenshot - pdf &amp; annotations (Arjen, my pdf reader doesn't show annotations - I can make one screenshot later on a mac. If not, could you please make one?)&lt;/span&gt;<br /> <br /> === Creating the CSS ===<br /> This was by far the most challenging part of this project, so we will discuss the challenges separately for every output format.<br /> <br /> ==== Web CSS ====<br /> For the website, the whole design of the book had to be reimagined. Pages do not exist, information doesn't have to be lineair and many interactive posibilities open up. We decided to keep the website largely lineair because seemed to fit the content well. Some interactivity was added: the index was redesigned to become a navigation menu and the tooltips were made into toolips. Because the font (Metric) was not licensed for online use, we had to find a font that was similair. This proved to be very difficult, so we had to compromise. We tried to avoid using javascript when possible, because this can decrease compatibility and increase the complexity of the code. The only exception we made was for the footnotes, because this was simply not possible in CSS. Numbering of figures, footnotes, pages and tables was also done in CSS. This turned out to work out quite well, although browser support is somewhat limited.<br /> <br /> ==== Responsive web CSS ====<br /> Instead of creating a separate mobile output, we made the regular website responsive to screen size. The challenges we encountered while doing this were not much different from the challenges that come with all responsive websites. Since these challenges are already well-documented, we will not discuss these further.<br /> <br /> ==== Epub CSS ====<br /> Epub stylesheets proved to be very badly documented. Every device has its own interpretation of CSS, and almost all of them are quite limited. Advanced CSS like numbering works on almost none of the available devices. <br /> <br /> We used Pandoc to create the epub, and one limitation was that pandoc can only add one stylesheet. We divided the stylesheet files into a global stylesheet, a print stylesheet and a specific epub stylesheet, all of which should be used for the epub. To solve this, we used a command line utility to merge these stylesheets and save them as one, so that we could use the resulting css for Pandoc.<br /> <br /> &lt;span style=&quot;background-color: yellow; font-size: .75em; font-weight: bold;&quot;&gt;place the css merge command here?&lt;/span&gt;<br /> <br /> ==== Print CSS ====<br /> Because one of our team member had good experiences in the past with Chrome's print functionality, this was the browser we used for testing. This turned out to be a mistake, because lately Chrome's printing functionality has deteriorated (possibly caused by their change of rendering engine). Many hours were wasted on trying to get the design to work on Chrome, after which we decided to focus on firefox. This proved to be much easier, and most CSS worked correctly.<br /> <br /> ==== Prince CSS ====<br /> <br /> None of the team members had used PrinceXML before, so the process was pretty much 'trial and error' in the begining. There were issues with the CSS files being used for the web version. They had to be imported in the CSS file used for Prince (even though they were being requested in the HTML head).<br /> [[File:Prince01.png | 390px]]&lt;br&gt;<br /> The HTML head, where the CSS files are requested).<br /> &lt;br&gt;&lt;br&gt;<br /> [[File:Prince02.png]]&lt;br&gt;<br /> The import command in prince.css (seems redundant but is actually necessary).<br /> &lt;br&gt;&lt;br&gt;<br /> <br /> Prince has some useful features, such as retrieving content from HTML elements and assigning them to variables (useful if you need to use a Chapter's title in the page footer, for example).<br /> <br /> One possible downside is that Prince XML is proprietary software.<br /> <br /> To use Prince, a command like the one below is needed:<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> prince container.html -s css/prince.css book.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation on how to use and install PrinceXML can be found here: http://www.princexml.com/doc/<br /> <br /> ==== Weasyprint CSS ====<br /> <br /> Weasyprint works similarly to PrinceXML. However, it is not proprietary software. It is trickyer to install when compared to Prince and does not have all the features that we found in PrinceXML.<br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> weasyprint container.html -s css/weasyprint.css weasybook_final.pdf<br /> &lt;/source&gt;<br /> <br /> Documentation:<br /> * how to install http://weasyprint.org/docs/install/#by-platform<br /> * command-line API http://weasyprint.org/docs/api/#command-line-api<br /> <br /> === Collaboration ===<br /> We worked in paralel on the different outputs, which worked well but sometimes caused little hickups. The most common problem was caused by the fact that we used multiple css stylesheet for every output. For example, when one person was working on the print stylesheet, this could accidentally break the pdf export.<br /> <br /> == Conclusion ==<br /> Overall, this workflow proved to work well. We needed some time to get used to the process, but it already appears to be a viable alternative to traditional workflows. The biggest challenge is probably that every member of the development team needs a fair bit of technical skill together with an eye for design. If such a team is available, this process can streamline the entire publication process.<br /> <br /> == Future directions ==<br /> Because this process is based on HTML and CSS, it can be combined with several existing technologies and platforms. For example, in the future we plan to use a wiki as the source. Wiki's allow for the collaborative creation of content, which can easily and automatically be converted to HTML. This HTML can then serve as the source file for the publication process that we just described. <br /> <br /> Another possible future direction is a research into the possibility of developing a WYSIWYG editor that strongly enforces a semantically and structurally correct layout. This would vastly simplify the first two steps of our process, and ideally render it obsolete. <br /> <br /> == Output previews == <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ All-in-one Publishing<br /> |-<br /> |WEBSITE<br /> |EPUB<br /> |PRINCE pdf<br /> |WEASYPRINT pdf<br /> |-<br /> |[http://headroom.pzwart.wdka.hro.nl/~ldossin/all-in-one-publishing/ VISIT] <br /> |[[file:all-in-one-publishing-epub.zip]] <br /> |[[file:all-in-one-publishing-pdf.pdf]] <br /> |[[File:Weasybook_final.pdf]]<br /> |}<br /> <br /> [[Category:research]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Wordpress-Intermediate&diff=1443 2015-06-24T13:56:48Z

<p>Lucia Dossin: Created page with &quot;=Overview= You use WordPress and you’d like to change a few details in your Theme. But the Theme does not allow that! In this workshop, you’ll learn how to use an existing...&quot;</p> <hr /> <div>=Overview=<br /> You use WordPress and you’d like to change a few details in your Theme. But the Theme does not allow that! In this workshop, you’ll learn how to use an existing WP Theme as a base for your own, custom Theme.<br /> <br /> =Learning Achievements=<br /> – WordPress template hierarchy and template pages&lt;br&gt;<br /> – how to make changes in an existing Theme, and&lt;br&gt;<br /> – how to avoid that these changes are lost when the Theme is upgraded.<br /> <br /> =Planning=<br /> The course duration is 3 hours.</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Wordpress-Basics2-self-hosted&diff=1442 2015-06-24T13:55:24Z

<p>Lucia Dossin: Created page with &quot;=Overview= WordPress is an open source framework to make websites. By downloading it and installing it on a server, you can do lots of things without even the need of knowing...&quot;</p> <hr /> <div>=Overview=<br /> WordPress is an open source framework to make websites. By downloading it and installing it on a server, you can do lots of things without even the need of knowing how to program.&lt;br&gt;<br /> With the self-hosted version of WP, you can install any Theme and Plugin you wish – not only the ones included in the basic install. That immensely increases your possibilities.<br /> <br /> =Learning Achievements=<br /> An overview of WordPress structure (database and files) and how Themes and Plugins can be installed manually.<br /> <br /> =Planning=<br /> The course duration is 3 hours.</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1441 2015-06-24T13:43:32Z

<p>Lucia Dossin: </p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous knowledge of HTML or CSS.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.&lt;br&gt;<br /> Basic html elements: h1-h6, p&lt;br&gt;<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.&lt;br&gt;<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1440 2015-06-24T13:43:08Z

<p>Lucia Dossin: </p> <hr /> <div>/Courses/Wordpress-Basics2-Self-hosted<br /> <br /> =Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous knowledge of HTML or CSS.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.&lt;br&gt;<br /> Basic html elements: h1-h6, p&lt;br&gt;<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.&lt;br&gt;<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1439 2015-06-24T13:34:09Z

<p>Lucia Dossin: /* Overview */</p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous knowledge of HTML or CSS.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.&lt;br&gt;<br /> Basic html elements: h1-h6, p&lt;br&gt;<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.&lt;br&gt;<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1438 2015-06-24T13:33:36Z

<p>Lucia Dossin: /* DAY 3 */</p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous HTML or CSS knowledge.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.&lt;br&gt;<br /> Basic html elements: h1-h6, p&lt;br&gt;<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.&lt;br&gt;<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1437 2015-06-24T13:33:27Z

<p>Lucia Dossin: /* DAY 2 */</p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous HTML or CSS knowledge.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.&lt;br&gt;<br /> Basic html elements: h1-h6, p&lt;br&gt;<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1436 2015-06-24T13:13:51Z

<p>Lucia Dossin: /* DAY 1 */</p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous HTML or CSS knowledge.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span&lt;br&gt;<br /> Colors: RGB model&lt;br&gt;<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float&lt;br&gt;<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.<br /> Basic html elements: h1-h6, p<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1435 2015-06-24T13:13:17Z

<p>Lucia Dossin: /* Learning Achievements */</p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous HTML or CSS knowledge.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> * basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> * how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span<br /> Colors: RGB model<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.<br /> Basic html elements: h1-h6, p<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1434 2015-06-24T13:13:01Z

<p>Lucia Dossin: </p> <hr /> <div>=Overview=<br /> Making a HTML page that looks more like a poster than a website - and giving students a basic introduction to HTML and CSS. These are the course main goals.<br /> <br /> The course does not require any previous HTML or CSS knowledge.<br /> Note: this course was formerly known as ‘Making Web Posters’<br /> <br /> =Learning Achievements=<br /> – basic HTML/CSS skills, the CSS box model and how different browsers deal with that<br /> – how to accommodate a layout in various screen sizes and how to use typography on the web<br /> <br /> =Planning=<br /> The course is divided into 3 lessons of 3 hours. After the theory is explained, there is time to practice.<br /> <br /> ==DAY 1==<br /> Basic html elements: div, span<br /> Colors: RGB model<br /> Introduction to CSS: positioning, z-index, color, width, height, border, margin, padding, box-shadow, gradient, transform, border-radius, float<br /> Practice<br /> <br /> ==DAY 2==<br /> Web fonts: existing formats and ways to use it.<br /> Basic html elements: h1-h6, p<br /> CSS: font-family, text-align, line-height, letter-spacing, text-shadow<br /> Practice<br /> <br /> ==DAY 3==<br /> Media queries.<br /> Practice<br /> <br /> <br /> <br /> [[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin https://ps.wdka.nl/wiki/index.php?title=Courses/Browser_as_Canvas&diff=1433 2015-06-24T12:50:51Z

<p>Lucia Dossin: Created page with &quot;File:Browser canvas day2 (1).pdf&quot;</p> <hr /> <div>[[File:Browser canvas day2 (1).pdf]]</div>

Lucia Dossin