<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.soylentnews.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mrbluze</id>
	<title>SoylentNews - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.soylentnews.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mrbluze"/>
	<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/wiki/Special:Contributions/Mrbluze"/>
	<updated>2026-05-25T16:02:55Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.4</generator>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7202</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7202"/>
		<updated>2014-04-09T04:28:31Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Style is made up of many things.'''''&lt;br /&gt;
== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Explanation of how the site's color / colour should be chosen and some points on colour perception.&lt;br /&gt;
*[[Style:Typography|Typography ]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website and ''other aspects of the project'' look, feel and function. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work closely integrate with those of #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Site Reskin''' - We are now at the phase of designing / planning a reskin of the project's user interface. The implementation phase of this task will become feasible once dependencies are met:&lt;br /&gt;
** The site name needs to be finalized as this could significantly impact the style of the user interface and visual appearance. A name change is potentially a direction change.&lt;br /&gt;
** CSS needs to be easily edited and modified to meet the user interface specifications&lt;br /&gt;
** The site needs to be able to fully and easily function '''without Javascript'''&lt;br /&gt;
** Javascript components must be carefully implemented to facilitate the function of the site with graceful fallback at all times&lt;br /&gt;
** Agreement on the final skin needs to be made with the PTB's of the overall project.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Others - if your name does not appear here, [mailto:style@soylentnews.org Email us!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7201</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7201"/>
		<updated>2014-04-09T04:26:03Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Style is made up of many things.'''''&lt;br /&gt;
== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Explanation of how the site's color / colour should be chosen and some points on colour perception.&lt;br /&gt;
*[[Style:Typography|Typography ]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Site Reskin''' - We are now at the phase of designing / planning a reskin of the project's user interface. The implementation phase of this task will become feasible once dependencies are met:&lt;br /&gt;
** The site name needs to be finalized as this could significantly impact the style of the user interface and visual appearance. A name change is potentially a direction change.&lt;br /&gt;
** CSS needs to be easily edited and modified to meet the user interface specifications&lt;br /&gt;
** The site needs to be able to fully and easily function '''without Javascript'''&lt;br /&gt;
** Javascript components must be carefully implemented to facilitate the function of the site with graceful fallback at all times&lt;br /&gt;
** Agreement on the final skin needs to be made with the PTB's of the overall project.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Others - if your name does not appear here, [mailto:style@soylentnews.org Email us!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7200</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7200"/>
		<updated>2014-04-09T04:22:49Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page was rewritten to reflect the wiki's documentation purpose. The original forum thread on this topic contained mostly subjective opinion on favourite colours, etc. &lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup and, arguably, natural selection.&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content. Colour usage in branding (logos, stripes, etc) should be enough for differentiation but no more than that.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting.&lt;br /&gt;
&lt;br /&gt;
== Colour Quality ==&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7199</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7199"/>
		<updated>2014-04-09T04:21:47Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Colour Quantity */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page was rewritten to reflect the wiki's documentation purpose. The original forum thread on this topic contained mostly subjective opinion on favourite colours, etc. &lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup and, arguably, natural selection.&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content. Colour usage in branding (logos, stripes, etc) should be enough for differentiation but no more than that.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting.&lt;br /&gt;
&lt;br /&gt;
== Colour Quality ===&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7198</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7198"/>
		<updated>2014-04-09T04:20:04Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page was rewritten to reflect the wiki's documentation purpose. The original forum thread on this topic contained mostly subjective opinion on favourite colours, etc. &lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup and, arguably, natural selection.&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting. &lt;br /&gt;
== Colour Quality ===&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7197</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7197"/>
		<updated>2014-04-09T04:19:28Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page was rewritten to reflect the wiki's documentation purpose. The original forum thread on this topic contained mostly subjective opinion on favourite colours, etc. &lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting. &lt;br /&gt;
== Colour Quality ===&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7196</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7196"/>
		<updated>2014-04-08T23:45:55Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Subpages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Explanation of how the site's color / colour should be chosen and some points on colour perception.&lt;br /&gt;
*[[Style:Typography|Typography ]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Site Reskin''' - We are now at the phase of designing / planning a reskin of the project's user interface. The implementation phase of this task will become feasible once dependencies are met:&lt;br /&gt;
** The site name needs to be finalized as this could significantly impact the style of the user interface and visual appearance. A name change is potentially a direction change.&lt;br /&gt;
** CSS needs to be easily edited and modified to meet the user interface specifications&lt;br /&gt;
** The site needs to be able to fully and easily function '''without Javascript'''&lt;br /&gt;
** Javascript components must be carefully implemented to facilitate the function of the site with graceful fallback at all times&lt;br /&gt;
** Agreement on the final skin needs to be made with the PTB's of the overall project.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Others - if your name does not appear here, [mailto:style@soylentnews.org Email us!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7195</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7195"/>
		<updated>2014-04-08T23:41:40Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page was rewritten to reflect the wiki's documentation purpose. The original forum thread on this topic contained mostly subjective opinion on favourite colours, etc. &lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting. &lt;br /&gt;
== Colour Quality ===&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7194</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7194"/>
		<updated>2014-04-08T23:40:03Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(This page is being reformatted to reflect the wiki's documentation purpose.)&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting. &lt;br /&gt;
== Colour Quality ===&lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances. Complementary colour can also help with uncallibrated or low colour gamut displays where the hue of a site can vary wildly.&lt;br /&gt;
* The choice of colour should take into account people with disabilities regarding colour recognition. As such, this issue can be avoided more or less by not having two colours of similar saturation and brightness juxtaposed and having consistent layout of elements that have a certain colour so that if not recognized by other means, their location can be predicted. Traffic lights follow this principle (Red is always at the top, and Green at the bottom).&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7193</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7193"/>
		<updated>2014-04-08T23:33:08Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(This page is being reformatted to reflect the wiki's documentation purpose.)&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
Colour theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. The name of the site may imply colour. For example, in IRC and forums members of the community wished the site to be green because Soylent Green was part of their preconception of what must go with &amp;quot;Soylent&amp;quot;. We have not changed colour at the moment mainly because no major style changes are planned until the site moves beyond alpha (new features are being implemented every few days), the name is finalized and enough human resources are available to implement a reskin.&lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
* Because the main emphasis of this project is text, colour needs to be used sparingly and only to emphasise content.&lt;br /&gt;
* In the current near-original layout of the site, red is the chosen colour for now, but there is a great deal of it, to the point that it is distracting and a bit off-putting. &lt;br /&gt;
* Notice that the high saturation of red changes the perception of the neutral grey of the rest of the page to be a warm grey. In chillax.soylentnews.org, a fully saturated royal blue is in use, which turns the neutral grey perception to be a cool grey. Neither of these versions has optimal colour balance, nor has any consideration been given to complementary colours and how they may offset imbalances.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Comments about the site color from the [http://forums.soylentnews.org/viewtopic.php?f=9&amp;amp;t=53 forums]:&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cloying''': So far there seems to be a lot of red flying about. The logo, the initial slash code site.&lt;br /&gt;
&lt;br /&gt;
I would much prefer green, a Slashdot similar green. Please say it will be green!&lt;br /&gt;
&lt;br /&gt;
Green is more peaceful, the color of science in quizzes (well often), obviously soylent green, but perhaps more importantly the colour of Slashdot. I think familiarity will really help everyone feel at home. Or is there a problem using green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Category''': Green is the obvious choice IMO, from the name alone.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Blackmoore''': I like green myself. is everything currently in red; in an attempt to avoid conflict with dice? or just because were mad as hell?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Twike''': I also like green, and I think it's red because that's the slashcode default(I think I saw that mentioned earlier on one of the other threads, but I'm not going to look it up now, I'm still getting caught back up).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''carguy''': I'm cool with any defaults for now, red is certainly usable. Seems like there are bigger fish to fry.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': That's all we have for now. There was going to be a bit of a test earlier, but moderation was broken. They are regrouping and fixin that, and will let us know what's up as soon as they can.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. Another color could be better.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': Oh, but ''this'' is SoylentVerde. Totally unrelated.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': &amp;lt;blockquote&amp;gt;Cactus wrote: &amp;lt;br /&amp;gt;Oh, but this is SoylentVerde. Totally unrelated.&amp;lt;/blockquote&amp;gt;Oh, well that is completely different. Carry on, then.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Istaera''': I think it has to be a different colour to slashdot in order to avoid copying them, copyright, etc.&lt;br /&gt;
&lt;br /&gt;
That said, green is the obvious choice for something with Soylent in the name, so perhaps a different green would work well, perhaps a greener green (lighter? yellower?).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Gaaark''': &amp;lt;blockquote&amp;gt;mattie_p wrote: &amp;lt;br /&amp;gt;Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. &amp;lt;/blockquote&amp;gt;Another color could be better.But soylent red/any/other/colour isn't people. Wonder if there is an off-green? :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Blue maybe. :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': I'm partial to the blue going on over at pipedot.org&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Apparently the blue at pipedot is now considerably more green than when I first noticed it.&lt;br /&gt;
&lt;br /&gt;
At least on my monitor.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''bryan''': &amp;lt;blockquote&amp;gt;Apparently the blue at pipedot is now considerably more green than when I first noticed it.&amp;lt;/blockquote&amp;gt;I've been using the same blue (#506890) [http://beicker.org/ on] [http://beicker.com/ most] [https://update.dynatouch.com/ of] [http://zwin.org/ my] [https://zenbi.net/ webpages] for over 15 years.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Well, everything else around here is breaking down, I suppose my monitor might as well be one of them.&lt;br /&gt;
&lt;br /&gt;
Can you describe how that blue looks to you?&lt;br /&gt;
&lt;br /&gt;
Does it have a whole lot more green in it than the blue here on the phpBB version of Soylent?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''it doesn't come easy''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you&amp;lt;/blockquote&amp;gt;Whoa, our first philosophical question. I've often wondered how colors look to other people. Someday, maybe we'll be able to see the world from another's point of view...then maybe we'll be able to answer that question (as well as others).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;To me, on my screen, its blue, leaning towards purple.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;No green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
No green?&amp;lt;/blockquote&amp;gt;We are talking about http://pipedot.org/ right.? there is no green in the site theme what-so-ever. &amp;lt;br /&amp;gt;&lt;br /&gt;
None, zip, nil, nada :)&lt;br /&gt;
&lt;br /&gt;
You need a new monitor/glasses/eyes&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': If not all of the above.&lt;br /&gt;
&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;Mostly,&lt;br /&gt;
The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
Still no green tho :)&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
        Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
    Mostly,&lt;br /&gt;
    The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
    I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
    Still no green tho :)&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
That's exactly how this page looks for me in Chrome on XP, but in the tab right next to it pipedot's blue has so much green it might be more accurate to call it green-blue than blue-green.&lt;br /&gt;
&lt;br /&gt;
But a few days ago it was semi-light blue with no green and the faintest whisper of red.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Are you partially colour-blind? &amp;lt;br /&amp;gt; Can you try with a different monitor?&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;br /&gt;
[[Category:Archived forum threads]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7192</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7192"/>
		<updated>2014-04-08T23:06:47Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(This page is being reformatted to reflect the wiki's documentation purpose.)&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
Color theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. &lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Comments about the site color from the [http://forums.soylentnews.org/viewtopic.php?f=9&amp;amp;t=53 forums]:&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cloying''': So far there seems to be a lot of red flying about. The logo, the initial slash code site.&lt;br /&gt;
&lt;br /&gt;
I would much prefer green, a Slashdot similar green. Please say it will be green!&lt;br /&gt;
&lt;br /&gt;
Green is more peaceful, the color of science in quizzes (well often), obviously soylent green, but perhaps more importantly the colour of Slashdot. I think familiarity will really help everyone feel at home. Or is there a problem using green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Category''': Green is the obvious choice IMO, from the name alone.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Blackmoore''': I like green myself. is everything currently in red; in an attempt to avoid conflict with dice? or just because were mad as hell?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Twike''': I also like green, and I think it's red because that's the slashcode default(I think I saw that mentioned earlier on one of the other threads, but I'm not going to look it up now, I'm still getting caught back up).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''carguy''': I'm cool with any defaults for now, red is certainly usable. Seems like there are bigger fish to fry.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': That's all we have for now. There was going to be a bit of a test earlier, but moderation was broken. They are regrouping and fixin that, and will let us know what's up as soon as they can.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. Another color could be better.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': Oh, but ''this'' is SoylentVerde. Totally unrelated.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': &amp;lt;blockquote&amp;gt;Cactus wrote: &amp;lt;br /&amp;gt;Oh, but this is SoylentVerde. Totally unrelated.&amp;lt;/blockquote&amp;gt;Oh, well that is completely different. Carry on, then.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Istaera''': I think it has to be a different colour to slashdot in order to avoid copying them, copyright, etc.&lt;br /&gt;
&lt;br /&gt;
That said, green is the obvious choice for something with Soylent in the name, so perhaps a different green would work well, perhaps a greener green (lighter? yellower?).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Gaaark''': &amp;lt;blockquote&amp;gt;mattie_p wrote: &amp;lt;br /&amp;gt;Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. &amp;lt;/blockquote&amp;gt;Another color could be better.But soylent red/any/other/colour isn't people. Wonder if there is an off-green? :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Blue maybe. :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': I'm partial to the blue going on over at pipedot.org&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Apparently the blue at pipedot is now considerably more green than when I first noticed it.&lt;br /&gt;
&lt;br /&gt;
At least on my monitor.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''bryan''': &amp;lt;blockquote&amp;gt;Apparently the blue at pipedot is now considerably more green than when I first noticed it.&amp;lt;/blockquote&amp;gt;I've been using the same blue (#506890) [http://beicker.org/ on] [http://beicker.com/ most] [https://update.dynatouch.com/ of] [http://zwin.org/ my] [https://zenbi.net/ webpages] for over 15 years.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Well, everything else around here is breaking down, I suppose my monitor might as well be one of them.&lt;br /&gt;
&lt;br /&gt;
Can you describe how that blue looks to you?&lt;br /&gt;
&lt;br /&gt;
Does it have a whole lot more green in it than the blue here on the phpBB version of Soylent?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''it doesn't come easy''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you&amp;lt;/blockquote&amp;gt;Whoa, our first philosophical question. I've often wondered how colors look to other people. Someday, maybe we'll be able to see the world from another's point of view...then maybe we'll be able to answer that question (as well as others).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;To me, on my screen, its blue, leaning towards purple.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;No green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
No green?&amp;lt;/blockquote&amp;gt;We are talking about http://pipedot.org/ right.? there is no green in the site theme what-so-ever. &amp;lt;br /&amp;gt;&lt;br /&gt;
None, zip, nil, nada :)&lt;br /&gt;
&lt;br /&gt;
You need a new monitor/glasses/eyes&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': If not all of the above.&lt;br /&gt;
&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;Mostly,&lt;br /&gt;
The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
Still no green tho :)&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
        Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
    Mostly,&lt;br /&gt;
    The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
    I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
    Still no green tho :)&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
That's exactly how this page looks for me in Chrome on XP, but in the tab right next to it pipedot's blue has so much green it might be more accurate to call it green-blue than blue-green.&lt;br /&gt;
&lt;br /&gt;
But a few days ago it was semi-light blue with no green and the faintest whisper of red.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Are you partially colour-blind? &amp;lt;br /&amp;gt; Can you try with a different monitor?&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;br /&gt;
[[Category:Archived forum threads]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7191</id>
		<title>Style:Color</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Color&amp;diff=7191"/>
		<updated>2014-04-08T22:35:05Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(This page has recently been reformatted to reflect the wiki's documentation purpose.)&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''''De gustibus non dispudandum est.'''''&lt;br /&gt;
Color theory is a complex and advanced topic, but some things can quickly be understood about it:&lt;br /&gt;
* The perception of color depends on the medium it is presented and the context in which it is presented.&lt;br /&gt;
* Perception itself is highly 'subjective', however recent neuroscientific discoveries have given explanations on why color, contrast and shadow are perceived the way they are&lt;br /&gt;
* People's tastes for colour are influenced by many subconscious factors:&lt;br /&gt;
** Genetic makeup&lt;br /&gt;
** Previous exposure and association with colour&lt;br /&gt;
** Contextual presentation of colour with either positive or negative subconscious signals and juxtaposition with other visual features&lt;br /&gt;
** Fashion&lt;br /&gt;
** We could take ANY colour at all, even omg-ponies-pink, and make it awesome, due to the above factors.&lt;br /&gt;
* People don't like anything new, and they don't like anything old. But they eventually will like anything if it contains some familiar aspects but is different enough to be recognizable.&lt;br /&gt;
* Colour is branding. &lt;br /&gt;
&lt;br /&gt;
== Colour Quantity ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Comments about the site color from the [http://forums.soylentnews.org/viewtopic.php?f=9&amp;amp;t=53 forums]:&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cloying''': So far there seems to be a lot of red flying about. The logo, the initial slash code site.&lt;br /&gt;
&lt;br /&gt;
I would much prefer green, a Slashdot similar green. Please say it will be green!&lt;br /&gt;
&lt;br /&gt;
Green is more peaceful, the color of science in quizzes (well often), obviously soylent green, but perhaps more importantly the colour of Slashdot. I think familiarity will really help everyone feel at home. Or is there a problem using green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Category''': Green is the obvious choice IMO, from the name alone.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Blackmoore''': I like green myself. is everything currently in red; in an attempt to avoid conflict with dice? or just because were mad as hell?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Twike''': I also like green, and I think it's red because that's the slashcode default(I think I saw that mentioned earlier on one of the other threads, but I'm not going to look it up now, I'm still getting caught back up).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''carguy''': I'm cool with any defaults for now, red is certainly usable. Seems like there are bigger fish to fry.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': That's all we have for now. There was going to be a bit of a test earlier, but moderation was broken. They are regrouping and fixin that, and will let us know what's up as soon as they can.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. Another color could be better.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Cactus''': Oh, but ''this'' is SoylentVerde. Totally unrelated.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''mattie_p''': &amp;lt;blockquote&amp;gt;Cactus wrote: &amp;lt;br /&amp;gt;Oh, but this is SoylentVerde. Totally unrelated.&amp;lt;/blockquote&amp;gt;Oh, well that is completely different. Carry on, then.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Istaera''': I think it has to be a different colour to slashdot in order to avoid copying them, copyright, etc.&lt;br /&gt;
&lt;br /&gt;
That said, green is the obvious choice for something with Soylent in the name, so perhaps a different green would work well, perhaps a greener green (lighter? yellower?).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''Gaaark''': &amp;lt;blockquote&amp;gt;mattie_p wrote: &amp;lt;br /&amp;gt;Seems to me that the most recognized soylent is green, and might be trademarked or copyrighted. &amp;lt;/blockquote&amp;gt;Another color could be better.But soylent red/any/other/colour isn't people. Wonder if there is an off-green? :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Blue maybe. :D&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': I'm partial to the blue going on over at pipedot.org&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Apparently the blue at pipedot is now considerably more green than when I first noticed it.&lt;br /&gt;
&lt;br /&gt;
At least on my monitor.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''bryan''': &amp;lt;blockquote&amp;gt;Apparently the blue at pipedot is now considerably more green than when I first noticed it.&amp;lt;/blockquote&amp;gt;I've been using the same blue (#506890) [http://beicker.org/ on] [http://beicker.com/ most] [https://update.dynatouch.com/ of] [http://zwin.org/ my] [https://zenbi.net/ webpages] for over 15 years.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': Well, everything else around here is breaking down, I suppose my monitor might as well be one of them.&lt;br /&gt;
&lt;br /&gt;
Can you describe how that blue looks to you?&lt;br /&gt;
&lt;br /&gt;
Does it have a whole lot more green in it than the blue here on the phpBB version of Soylent?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''it doesn't come easy''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you&amp;lt;/blockquote&amp;gt;Whoa, our first philosophical question. I've often wondered how colors look to other people. Someday, maybe we'll be able to see the world from another's point of view...then maybe we'll be able to answer that question (as well as others).&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;To me, on my screen, its blue, leaning towards purple.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;No green?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;Can you describe how that blue looks to you?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    To me, on my screen, its blue, leaning towards purple.&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
No green?&amp;lt;/blockquote&amp;gt;We are talking about http://pipedot.org/ right.? there is no green in the site theme what-so-ever. &amp;lt;br /&amp;gt;&lt;br /&gt;
None, zip, nil, nada :)&lt;br /&gt;
&lt;br /&gt;
You need a new monitor/glasses/eyes&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': If not all of the above.&lt;br /&gt;
&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;Mostly,&lt;br /&gt;
The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
Still no green tho :)&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''unitron''': &amp;lt;blockquote&amp;gt;WizardFusion wrote:&lt;br /&gt;
        &amp;lt;blockquote&amp;gt;unitron wrote:&amp;lt;br /&amp;gt;If not all of the above.&lt;br /&gt;
        Does this page (forums.soylentnews.org phpBB) look blue overall?&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
    Mostly,&lt;br /&gt;
    The large header is blue, the &amp;quot;section&amp;quot; panels are blueish.&lt;br /&gt;
    I would describe them as dark light-blue, or dirty light-blue&lt;br /&gt;
&lt;br /&gt;
    Still no green tho :)&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
That's exactly how this page looks for me in Chrome on XP, but in the tab right next to it pipedot's blue has so much green it might be more accurate to call it green-blue than blue-green.&lt;br /&gt;
&lt;br /&gt;
But a few days ago it was semi-light blue with no green and the faintest whisper of red.&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
'''WizardFusion''': Are you partially colour-blind? &amp;lt;br /&amp;gt; Can you try with a different monitor?&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;br /&gt;
[[Category:Archived forum threads]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7190</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=7190"/>
		<updated>2014-04-08T22:05:00Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Discussion about what color the site in general should be (mostly archived from forums currently).&lt;br /&gt;
*[[Style:Typography|Typography ]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Site Reskin''' - We are now at the phase of designing / planning a reskin of the project's user interface. The implementation phase of this task will become feasible once dependencies are met:&lt;br /&gt;
** The site name needs to be finalized as this could significantly impact the style of the user interface and visual appearance. A name change is potentially a direction change.&lt;br /&gt;
** CSS needs to be easily edited and modified to meet the user interface specifications&lt;br /&gt;
** The site needs to be able to fully and easily function '''without Javascript'''&lt;br /&gt;
** Javascript components must be carefully implemented to facilitate the function of the site with graceful fallback at all times&lt;br /&gt;
** Agreement on the final skin needs to be made with the PTB's of the overall project.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Others - if your name does not appear here, [mailto:style@soylentnews.org Email us!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6921</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6921"/>
		<updated>2014-03-29T06:18:34Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Golden Ratio of Proportionality */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
==== Why do Golden Ratios work for visual appearance? ====&lt;br /&gt;
* The brain is geared for nature, in which natural logarithms and other well known patterns such as the Golden Ratio, are ubiquitous.&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
==== Taste ====&lt;br /&gt;
* The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
* Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
==== Practicality ====&lt;br /&gt;
* Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
* New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
** Smartphones exceed 300 pixels per inch&lt;br /&gt;
** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
* Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
==== Evidence Basis ====&lt;br /&gt;
* Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
*** 80 characters per line is faster to read than 40&lt;br /&gt;
*** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
*** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
* Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
* Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
*** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
*** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
*** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
*** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
*** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
*** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read. &lt;br /&gt;
*** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
*** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
==== Lessons ====&lt;br /&gt;
* Minimal lines, shades and distracting images should be used, to aid focus on the content (text) of the site.&lt;br /&gt;
* Font choice should be a compromise between aesthetics and readability. It is for this reason that, as displays became more photo-realistic, Microsoft chose Calibri, as it borders on being a serif font in many respects, but is recognized as sans serif. Microsoft's research in font readability has, at least until recently, been ahead of the others.&lt;br /&gt;
* We should consider returning to the use of a minimal serif, or borerline sans-serif font, rather than Verdana which is a classic sans-serif font and arguably a bit dated.&lt;br /&gt;
* As fonts are very inexpensive (less than $100) we could consider buying a font that suits our needs.&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6920</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6920"/>
		<updated>2014-03-29T05:47:19Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Lessons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
==== Taste ====&lt;br /&gt;
* The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
* Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
==== Practicality ====&lt;br /&gt;
* Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
* New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
** Smartphones exceed 300 pixels per inch&lt;br /&gt;
** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
* Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
==== Evidence Basis ====&lt;br /&gt;
* Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
*** 80 characters per line is faster to read than 40&lt;br /&gt;
*** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
*** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
* Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
* Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
*** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
*** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
*** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
*** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
*** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
*** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read. &lt;br /&gt;
*** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
*** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
==== Lessons ====&lt;br /&gt;
* Minimal lines, shades and distracting images should be used, to aid focus on the content (text) of the site.&lt;br /&gt;
* Font choice should be a compromise between aesthetics and readability. It is for this reason that, as displays became more photo-realistic, Microsoft chose Calibri, as it borders on being a serif font in many respects, but is recognized as sans serif. Microsoft's research in font readability has, at least until recently, been ahead of the others.&lt;br /&gt;
* We should consider returning to the use of a minimal serif, or borerline sans-serif font, rather than Verdana which is a classic sans-serif font and arguably a bit dated.&lt;br /&gt;
* As fonts are very inexpensive (less than $100) we could consider buying a font that suits our needs.&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6919</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6919"/>
		<updated>2014-03-29T05:36:59Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
==== Taste ====&lt;br /&gt;
* The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
* Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
==== Practicality ====&lt;br /&gt;
* Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
* New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
** Smartphones exceed 300 pixels per inch&lt;br /&gt;
** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
* Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
==== Evidence Basis ====&lt;br /&gt;
* Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
*** 80 characters per line is faster to read than 40&lt;br /&gt;
*** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
*** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
* Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
* Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
*** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
*** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
*** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
*** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
*** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
*** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read. &lt;br /&gt;
*** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
*** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
==== Lessons ====&lt;br /&gt;
* Minimal lines, shades and distracting images should be used, to aid focus on the content (text) of the site.&lt;br /&gt;
* Font choice should be a compromise between asthetics and readability. It is for this reason that Microsoft chose Calibri, as it borders on being a serif font in many respects, but is recognized as sans serif.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6918</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6918"/>
		<updated>2014-03-29T05:30:48Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
** Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
*** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
**** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
**** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
*** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
*** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
*** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
**** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
**** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
**** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
**** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
*** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read. &lt;br /&gt;
**** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
**** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
*** The lessons are therefore:&lt;br /&gt;
**** Minimal lines, shades and distracting images should be used, to aid focus on the content (text) of the site.&lt;br /&gt;
**** Font choice should be a compromise between asthetics and readability. It is for this reason that Microsoft chose Calibri, as it borders on being a serif font in many respects, but is recognized as sans serif.&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6917</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6917"/>
		<updated>2014-03-29T05:28:43Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
** Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
*** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
**** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
**** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
*** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
*** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
*** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
**** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
**** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
**** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
**** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
*** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read. &lt;br /&gt;
**** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
**** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
*** The lessons are therefore:&lt;br /&gt;
**** &lt;br /&gt;
**** Minimal lines, shades and&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6916</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6916"/>
		<updated>2014-03-29T05:26:35Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
** Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
*** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
**** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
**** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.&lt;br /&gt;
*** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
*** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
*** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
**** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
**** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
**** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
**** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
*** The accessory visual cortex interprets shapes. &lt;br /&gt;
**** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word. &lt;br /&gt;
**** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.&lt;br /&gt;
*** The lessons are therefore:&lt;br /&gt;
**** &lt;br /&gt;
**** Minimal lines, shades and&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6915</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6915"/>
		<updated>2014-03-29T05:21:11Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
** Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
*** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
**** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex process the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort. &lt;br /&gt;
*** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
*** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
*** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
**** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
**** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
**** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
**** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
*** The accessory visual cortex interprets shapes&lt;br /&gt;
*** The lessons are therefore:&lt;br /&gt;
**** &lt;br /&gt;
**** Minimal lines, shades and&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6914</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6914"/>
		<updated>2014-03-29T05:14:44Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
** Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others&lt;br /&gt;
*** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched. &lt;br /&gt;
*** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision. &lt;br /&gt;
*** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.&lt;br /&gt;
*** The eye enhances what you see by center-surround antagonism:&lt;br /&gt;
**** Bright and dark shade is sent to the visual cortex, which processes the signal&lt;br /&gt;
**** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection&lt;br /&gt;
**** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.&lt;br /&gt;
**** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions&lt;br /&gt;
*** The accessory visual cortex interprets shapes&lt;br /&gt;
*** The lessons are therefore:&lt;br /&gt;
**** &lt;br /&gt;
**** Minimal lines, shades and&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6913</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6913"/>
		<updated>2014-03-29T04:59:22Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
** Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts&lt;br /&gt;
*** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6912</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6912"/>
		<updated>2014-03-29T04:50:48Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
** Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays&lt;br /&gt;
*** This is bad because no two web browsers are using the same methods for this fudge factor&lt;br /&gt;
*** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6911</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6911"/>
		<updated>2014-03-29T04:48:17Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
** Old screen displays come in at around 96 pixels per inch&lt;br /&gt;
** New screen displays come in at 200+ pixels per inch:&lt;br /&gt;
*** Smartphones exceed 300 pixels per inch&lt;br /&gt;
*** Retina and similar high resolution displays are 250+ pixels per inch&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6910</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6910"/>
		<updated>2014-03-29T04:40:38Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* General Guidelines for Font Choice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
* Taste:&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
* Practicality:&lt;br /&gt;
* Evidence Basis:&lt;br /&gt;
** Older studies for screen fonts relied on lower resolution displays than those currently being manufactured.&lt;br /&gt;
*** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch): &lt;br /&gt;
**** 80 characters per line is faster to read than 40&lt;br /&gt;
**** Times New Roman is ''much more'' readable than Verdana at equal pixel size&lt;br /&gt;
**** Arial is ''somewhat more'' readable than Verdana&lt;br /&gt;
&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6909</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6909"/>
		<updated>2014-03-29T04:30:25Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Block Quote */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.&lt;br /&gt;
&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6908</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6908"/>
		<updated>2014-03-29T04:28:11Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Colour */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;br /&gt;
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6907</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6907"/>
		<updated>2014-03-29T04:26:00Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;br /&gt;
==== Colour ====&lt;br /&gt;
* Colour should be used very sparingly&lt;br /&gt;
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site&lt;br /&gt;
* Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6906</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6906"/>
		<updated>2014-03-29T04:23:59Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin&lt;br /&gt;
** Text should be approximatley 0.5cm justified from the vertical rule&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6905</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6905"/>
		<updated>2014-03-29T04:22:30Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6904</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6904"/>
		<updated>2014-03-29T04:21:18Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;br /&gt;
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)&lt;br /&gt;
==== Code ====&lt;br /&gt;
* Code should be monospace&lt;br /&gt;
* Code boxes should have a standard size and generally have automatic vertical and horizontal scroll-bars&lt;br /&gt;
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade). &lt;br /&gt;
* Text should have equal padding around it, about half the size that of block quote&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6903</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6903"/>
		<updated>2014-03-29T04:17:47Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
==== Drop Caps ====&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
==== Block Quote ====&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6902</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6902"/>
		<updated>2014-03-29T04:16:56Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6901</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6901"/>
		<updated>2014-03-29T04:15:22Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
** Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6900</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6900"/>
		<updated>2014-03-29T04:09:46Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;br /&gt;
=== General Guidelines for Font Choice ===&lt;br /&gt;
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''&lt;br /&gt;
** The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif&lt;br /&gt;
=== General Guidelines for Styles ===&lt;br /&gt;
* Drop-caps will not be used, as we are not aiming for magazine style.&lt;br /&gt;
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text.&lt;br /&gt;
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) that is about 0.5cm&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6899</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6899"/>
		<updated>2014-03-29T03:56:04Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Golden Ratio of Proportionality */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
* The same website provides a calculator:&lt;br /&gt;
See [http://www.pearsonified.com/typography/ Typography Calculator]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6898</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6898"/>
		<updated>2014-03-29T03:49:21Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* The Golden Ratio is approximately = 1.618&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;br /&gt;
*&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6897</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6897"/>
		<updated>2014-03-29T03:46:04Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png|thumbnail|Source: pearsonified.com]]&lt;br /&gt;
=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6896</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6896"/>
		<updated>2014-03-29T03:45:29Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png|thumbnail|Source: www.pearsonified.com]]&lt;br /&gt;
=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6895</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6895"/>
		<updated>2014-03-29T03:45:00Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Golden Ratio of Proportionality */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png|framed|Source: www.pearsonified.com]]&lt;br /&gt;
=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6894</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6894"/>
		<updated>2014-03-29T03:44:20Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':&lt;br /&gt;
* Line height increases with increasing font size, and increasing line length.&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;br /&gt;
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=6893</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=6893"/>
		<updated>2014-03-29T03:42:05Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Subpages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Discussion about what color the site in general should be (mostly archived from forums currently).&lt;br /&gt;
*[[Style:Typography|Typography ]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Phase 1''' [http://wiki.soylentnews.org/wiki/index.php?title=Style#Phase_1_Repair_List we repair the existing site]&lt;br /&gt;
*'''Phase 2''' we design a new and improved interface, (not a buck feta), which retains the same functionality but is slick, quick and works well on contemporary devices, not just large landscape monitors.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=6892</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=6892"/>
		<updated>2014-03-29T03:41:47Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Subpages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subpages ==&lt;br /&gt;
*[[Style:WishList|Wish List and Identified Problems]] - Look here for something to work on.&lt;br /&gt;
*[[Style:Resources|Resources]] - References and reading list.&lt;br /&gt;
*[[Style:Art|Art]] - Artwork links and discussion&lt;br /&gt;
*[[Style:UI_Design|User Interface Design]] - Discussion and definitions for UI design&lt;br /&gt;
*[[Style:Color|Site overall color]] - Discussion about what color the site in general should be (mostly archived from forums currently).&lt;br /&gt;
*[[Style:Typography]] - Font choice, spacing and markup.&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Phase 1''' [http://wiki.soylentnews.org/wiki/index.php?title=Style#Phase_1_Repair_List we repair the existing site]&lt;br /&gt;
*'''Phase 2''' we design a new and improved interface, (not a buck feta), which retains the same functionality but is slick, quick and works well on contemporary devices, not just large landscape monitors.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;br /&gt;
&lt;br /&gt;
[[Category:User experience]]&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6891</id>
		<title>Style:Typography</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Typography&amp;diff=6891"/>
		<updated>2014-03-29T03:14:21Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: Created page with &amp;quot;=== Golden Ratio of Proportionality === [http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here: * Long line length...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Golden Ratio of Proportionality ===&lt;br /&gt;
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here:&lt;br /&gt;
* Long line lengths require wider line widths&lt;br /&gt;
** Landscape view has long line lengths&lt;br /&gt;
** Portrait view has short line lengths&lt;br /&gt;
* The screen orientation should be sensed to determine optimal line width: use media queries.&lt;br /&gt;
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=5885</id>
		<title>WhosWho</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=WhosWho&amp;diff=5885"/>
		<updated>2014-03-09T10:32:31Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Style */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In the interest of getting questions to the right people on IRC and general organization, this is a summary of who is involved in SoylentNews. '''Please add yourself''' (or others) if you are actively working on the project. Also you can skip to the [[#Overlords|Overlord Contacts]].&lt;br /&gt;
&lt;br /&gt;
See also: [[Staff list]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==The Man Behind The Curtain==&lt;br /&gt;
&lt;br /&gt;
* NCommander - Site-wide responsibility&lt;br /&gt;
&lt;br /&gt;
==Administration==&lt;br /&gt;
&lt;br /&gt;
* mattie_p - Overlord/General Manager&lt;br /&gt;
* mrcoolbp&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
* NCommander&lt;br /&gt;
* robinld&lt;br /&gt;
* zford&lt;br /&gt;
* mechanicjay&lt;br /&gt;
&lt;br /&gt;
==Style==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;shogun - HTML&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;moo_kuh - Testing&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;PrestonL - CSS / Bug Testing&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;mtrycz - User Interface&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;CynicGalahad - Website Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
Correspondence: [mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
&lt;br /&gt;
==Frontend: CSS\HTML issues that pertain to look and feel==&lt;br /&gt;
&lt;br /&gt;
* paulej72 - (working on mods to comments.css)&lt;br /&gt;
* AudioGuy - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made&lt;br /&gt;
* martyb&lt;br /&gt;
&lt;br /&gt;
==Content==&lt;br /&gt;
* Dopefish - Overlord&lt;br /&gt;
&lt;br /&gt;
Editors include:&lt;br /&gt;
&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* mattie_p&lt;br /&gt;
* janrinok&lt;br /&gt;
* girlwhowaspluggedout&lt;br /&gt;
&lt;br /&gt;
Misc:&lt;br /&gt;
&lt;br /&gt;
* Cactus&lt;br /&gt;
&lt;br /&gt;
==Forums==&lt;br /&gt;
* applesmasher - Overlord&lt;br /&gt;
* Dopefish&lt;br /&gt;
* LaminatorX&lt;br /&gt;
* mattie_p - I'm just an active user and in the Editor Group.  I'm nobody official on the forums, though.&lt;br /&gt;
&lt;br /&gt;
==Wiki==&lt;br /&gt;
* FunPika - Overlord&lt;br /&gt;
* Cactus&lt;br /&gt;
* sfm&lt;br /&gt;
* cosurgi&lt;br /&gt;
* [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 13:16, 26 February 2014 (MST) - working on re-organization and clean up&lt;br /&gt;
&lt;br /&gt;
==IRC==&lt;br /&gt;
* Landon - Overlord&lt;br /&gt;
* Xlefay - Technical lead&lt;br /&gt;
* MrBluze&lt;br /&gt;
&lt;br /&gt;
==Bugs==&lt;br /&gt;
* paulej72 - currently scraping SoylentNews comments for bug reports and posting them to the bug tracker&lt;br /&gt;
* martyb - QA and testing&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overlords==&lt;br /&gt;
&lt;br /&gt;
We're have overlords that manage various features. An overlord is responsible for granting access - it's '''intended''' to be a ''no work'' position, so that it can be held for long periods without requiring much time.&lt;br /&gt;
 &lt;br /&gt;
So for example, Applesmasher is the overlord of forums. He grants access to people and recovers access when people leave, but he doesn't ''have'' to do any work himself (although he can if he wants). He ensures that the people with access are reliable.&lt;br /&gt;
 	&lt;br /&gt;
If you need a forum for your group, ask the overlord of forums. If you want a set of wiki pages, ask the overlord of the wiki, and so on.	&lt;br /&gt;
	&lt;br /&gt;
The current overlords originally agreed to hold the position until Mar 1, that date has already passed. Going forward we can choose overlords via some formal process. (And the current overlords might ask to continue.)&lt;br /&gt;
 	&lt;br /&gt;
The current overlords can be contacted here:&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
art@SoylentNews.org&lt;br /&gt;
 	&lt;br /&gt;
editors@SoylentNews.org	&lt;br /&gt;
	&lt;br /&gt;
forums@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
wiki@SoylentNews.org	&lt;br /&gt;
 &lt;br /&gt;
chat@SoylentNews.org&lt;br /&gt;
 &lt;br /&gt;
style@soylentnews.org&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
There will be more to come. This is temporary to get us going - the community can change the structure later, but for now things seem to naturally separate into these areas of interest.&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style:Art&amp;diff=5550</id>
		<title>Style:Art</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style:Art&amp;diff=5550"/>
		<updated>2014-03-06T05:35:21Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Description==&lt;br /&gt;
Links to artwork samples and artwork discussion.&lt;br /&gt;
===Icons To Do===&lt;br /&gt;
*Answers&lt;br /&gt;
*Business&lt;br /&gt;
*Career &amp;amp; Education&lt;br /&gt;
*Code&lt;br /&gt;
*Digital Liberties&lt;br /&gt;
*Editorial&lt;br /&gt;
*Hardware&lt;br /&gt;
*Leisure&lt;br /&gt;
*OS&lt;br /&gt;
*Science&lt;br /&gt;
*Software&lt;br /&gt;
*SoylentNews&lt;br /&gt;
*Techonomics&lt;br /&gt;
*Today's News&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5547</id>
		<title>MobileDesign</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5547"/>
		<updated>2014-03-06T02:49:47Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Single Column Format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Single Column Format==&lt;br /&gt;
*This format is ideal for hand-held devices (all sizes) which are typically held in the portrait orientation.&lt;br /&gt;
*Principles are: &lt;br /&gt;
**No functional elements should appear along the bottom of the screen &lt;br /&gt;
**Most users are right handed therefore orientate buttons to the right of the screen where possible&lt;br /&gt;
**At all times a minimal of touches/clicks should lead to the most common tasks&lt;br /&gt;
**All tasks must be obviously categorized&lt;br /&gt;
**Single column view is meant to be minimalistic and geared largely towards content consumption and not so much creation, although this should be made simple (guidelines to come).&lt;br /&gt;
*See [http://i.imgur.com/WVDZiAy.png This Sketch] and refer to the below for details.&lt;br /&gt;
**A - Username / Login option should be a tap/pull down with the usual log in/log out and viewing preferences. In small devices this can be iconified, but the menu may occupy the entire screen if required.&lt;br /&gt;
**B - Topic Bar - should be the topic group currently being viewed eg: &amp;quot;Technology&amp;quot; or &amp;quot;All Stories&amp;quot;. Tapping this should bring down a pull down list of topics for selection.&lt;br /&gt;
**D - Website Logo - tapping this should return to home page, it can also pull down a list of links to other major areas.&lt;br /&gt;
**E - Read More and other buttons - positioned to the right. They need to be at least 1cm tall and 1cm wide so that a finger can touch the button easily.&lt;br /&gt;
**F - Article Body - text needs to be 11 point equivalent minimum. Use em to be device independent if need be, but it's possible that experimentation will be required. Typographic and text layout guidelines are described elsewhere.&lt;br /&gt;
**G - Bottom of page needs to indicate that there is &amp;quot;more&amp;quot; below .. one way is to fade window contents to background color, or to black, to indicate that there is more to be found below.&lt;br /&gt;
**H - Story Icons - Clicking these should do something, possibly changing the story view category?&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=Style&amp;diff=5546</id>
		<title>Style</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=Style&amp;diff=5546"/>
		<updated>2014-03-06T02:47:20Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Subpages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subpages ==&lt;br /&gt;
*[http://wiki.soylentnews.org/wiki/index.php/Style:WishList Wish List and Identified Problems] - Look here for something to work on.&lt;br /&gt;
*[http://wiki.soylentnews.org/wiki/index.php/Style:Resources Resources] - References and reading list.&lt;br /&gt;
*[http://wiki.soylentnews.org/wiki/index.php/Style:Art Art] - Artwork links and discussion&lt;br /&gt;
*[http://wiki.soylentnews.org/wiki/index.php/Style:UI_Design User Interface Design] - Discussion and definitions for UI design&lt;br /&gt;
*Typography&lt;br /&gt;
*Testing&lt;br /&gt;
&lt;br /&gt;
== The Project ==&lt;br /&gt;
===Description===&lt;br /&gt;
&amp;quot;Style&amp;quot; is a  project concerned with how the website looks, feels and functions. Our aim is to produce the slickest, best looking, easy to use user experience whilst preserving all the functionality that the community puts into place. Our areas of work overlap with #Dev:&lt;br /&gt;
*Graphic Design&lt;br /&gt;
*UI Design&lt;br /&gt;
*Artwork&lt;br /&gt;
*Heuristics and Usability&lt;br /&gt;
*CSS / HTML&lt;br /&gt;
&lt;br /&gt;
===Scope===&lt;br /&gt;
&lt;br /&gt;
To guide the development of the site with respect to:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Heuristics:''' the workflow of the site needs to be intuitive and efficient. The user should need to perform a minimum of actions to achieve each task, and the steps should be intuitive. Our task is to define these workflows, assess the performance of them on the site and direct changes accordingly.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''Appearance:''' the site should reach the best possible standards of visual appeal, subject to its main purpose of article presentation and peer review. Our task is to develop a set of user interface guidelines to guide developers, including placement of elements, font selection graphical styles.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;'''User Experience:''' the final arbiter of the success of our work is the community. Our task is to assess the quality of our work by monitoring the usage of website elements, studying user workflow patterns and giving the community the opportunity to give feedback on style related matters.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Basic Plan===&lt;br /&gt;
*'''Phase 1''' [http://wiki.soylentnews.org/wiki/index.php?title=Style#Phase_1_Repair_List we repair the existing site]&lt;br /&gt;
*'''Phase 2''' we design a new and improved interface, (not a buck feta), which retains the same functionality but is slick, quick and works well on contemporary devices, not just large landscape monitors.&lt;br /&gt;
&lt;br /&gt;
===Members and Roles===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;MrBluze - Graphics Design / Art / UI Design / Heuristics&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;FrogBlast - Art / Graphics Design&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Recruiting===&lt;br /&gt;
We are interested in people wanting to help who have skills in:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Graphic design&amp;lt;/b&amp;gt; - for critical appraisal, or assistance in the art department.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;User interface design&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;Mobile app development&amp;lt;/b&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Contact===&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
[mailto:style@soylentnews.org style@soylentnews.org]&lt;br /&gt;
or&lt;br /&gt;
'#style' on irc.soylentnews.org&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Work in Progress==&lt;br /&gt;
===Handheld Devices===&lt;br /&gt;
*Hand-held devices (eg: up to 7 inch screen device) are usually held in portrait mode for reading.&lt;br /&gt;
*Efficient use of space requires a single column view&lt;br /&gt;
*These devices, when held in the portrait orientation, are not generally suitable for extensive content creation and the UI should not be geared towards content creation&lt;br /&gt;
*Functionality can be curtailed for these devices to a MINIMUM NECESSARY to perform normal tasks&lt;br /&gt;
====User interface principles:====&lt;br /&gt;
*Consider [http://i.imgur.com/ayOGVps.png how a device is held] in a right handed person. The edges of the screen are the places where fingers can accurately pick off small items, the right side of the screen is where fingers can do common tasks without impeding visibility. At the top of the screen there is usually just enough room for a utilities bar, this should be a drag down which essentially should reveal a site-map for the mobile device.&lt;br /&gt;
*Do not put any buttons or functions at the bottom of the page, at most a short copyright / authorship notice or a courtesy shadow to indicate bottom of document, but nothing that can be accidentally touched to cause a navigation event.&lt;br /&gt;
&lt;br /&gt;
===IRC Web Interface===&lt;br /&gt;
*Owned by: xlefay&lt;br /&gt;
*Information needs to be provided as to specs required and who is going to write the css/html.&lt;br /&gt;
*'''General Ideas''' (MrBluze)&lt;br /&gt;
** The web interface needs generous screen space and it may well be best to use the proposed single column user interface, ie: no left and right columns, limited functionality in a header '''and''' footer containing eg: Login/Logout option, User Prefs link, Home link. This minimalistic interface is originally intended for mobile devices where screen real estate is a premium and content must have pride of place.&lt;br /&gt;
** The theme should be exactly the same as of the rest of the site. The web interface itself looks fine and should be simply embedded in the standard red-banner window as currently exists, so that re-theming is trivial.&lt;br /&gt;
** This will require a separate perl file eg: irc.pl. It should be fairly easy to strip down the features of another similar file and include html that provides a frame which loads the web interface.&lt;br /&gt;
** There should be checking for javascript and a polite apology that this is required, with links to one or two suggested real IRC clients.&lt;br /&gt;
** Ideally the log in and username should be automated to be that of the logged in user, but the wherewithal of this is outside the scope of #style (although this is the 'feel' of look and feel).&lt;br /&gt;
&lt;br /&gt;
===Developing new Theme===&lt;br /&gt;
===Typography===&lt;br /&gt;
Paragraph element:&lt;br /&gt;
This needs to be narrower in all cases: &lt;br /&gt;
&amp;lt;code&amp;gt;.intro p, .full p { margin: 0 0 0.4em; }&amp;lt;/code&amp;gt; ```Resolved.&lt;br /&gt;
&lt;br /&gt;
===Lynx mode===&lt;br /&gt;
I (Shogun) decided to create non-CSS, non-JS theme for site.&lt;br /&gt;
It would be advantageous for some users because:&lt;br /&gt;
&lt;br /&gt;
* Not all browsers support CSS at all(Lynx, w3m)&lt;br /&gt;
* Not all browsers support CSS correctly according to W3M standards (IE6 for example)&lt;br /&gt;
* Not all browsers have full implementation of &amp;quot;newest&amp;quot; version of CSS (currently it's CSS4)&lt;br /&gt;
* Not everyone wants to use CSS because of performance issues on slower machines (CSS is very flexible and provides a lot of complexity like CSS sided animations, alpha-transparency and other resource heavy(for old machines) effects&lt;br /&gt;
* Not everyone wants to use CSS beasue of potential security issues:&lt;br /&gt;
It is proven that [http://stackoverflow.com/questions/2497146/is-css-turing-complete CSS is Turing complete], therefor there is theoretical possibility that someone could put some rogue code(shell-code) withing CSS and inject it into memory of computer using nothing else but CSS. This AFIK have not been done yet - but I believe that in incoming years someone smart enough will be able to generate such hostile CSS.&lt;br /&gt;
&lt;br /&gt;
* JavaScript implementation is usually very slow in old browsers (up to 50x slower then modern 2013 browsers).  Because of that majority of scripts are simply unusable for users - being well too slow.&lt;br /&gt;
&lt;br /&gt;
* Owners of old computers can't or don't want to upgrade their browsers - because of lack of RAM needed to run them. It's nearly impossible to work on computer with 256MB ram with newest[2014] versions of Firefox,Chrome or Opera - because of excessive memory usage. Funny fact is that those new browsers have superior execution speed of JavaScript - but this is ALL LOST because of overall excessive memory usage of browser.&lt;br /&gt;
&lt;br /&gt;
* JavaScript libraries tends to be &amp;quot;big&amp;quot;. It '''does matter''' when you are using modem or 3G capped connection(speeds in range of 64kbit/s - 128kbit/s). Process of loading some of the libraries can be as long as one minute on such connections, and often JS code taking as much as 75% of overall content on the side. Early slash-dot beta was great example of that.&lt;br /&gt;
&lt;br /&gt;
* In good old days, web pages were static. You download it, and after download you plug-off your Internet cable, read the article, fill-up form, write comment, and connect back to continue minutes later without any problems. With JS - most websites force user to be permanently connected to Internet. &lt;br /&gt;
This is especially painful in high latency links. some scripts are tracking each click on form and transport them to server and back with new orders - this is problematic because if script requires 20 operations with server, and each operation takes 500ms - it would increase end-user lag to humongous 5s... And that is all AFTER all scripts have been downloaded. Unfortunately most modern Internet sites suffer from this - because developers does not test sites under low quality Internet links.&lt;br /&gt;
&lt;br /&gt;
* Because JS on websites tend to run in unlimited loops - they consume cpu cycles ALL-THE-TIME, unlike good old plain html where after download and parsing cpu usage went to ZERO.&lt;br /&gt;
&lt;br /&gt;
* Javascript is Turing Complete, therefor it is possible to write malware with it. For example in August 2013 FBI [http://security.stackexchange.com/questions/40072/could-someone-explain-parts-of-the-fbis-firefox-0-day injected JavaScript based exploit  into various TOR servicies.]&lt;br /&gt;
&lt;br /&gt;
'''Comment by MrBluze:'''&lt;br /&gt;
Possible task list:&lt;br /&gt;
*There is already a minimalistic mode, simplified view etc. Have a look at it.&lt;br /&gt;
*There are UI problems with this mode, it contains JS!&lt;br /&gt;
*Need to strip the JS and replace with single page settings .. not trivial&lt;br /&gt;
*Need to simplify the path from setting and UNSETTING the simplified mode&lt;br /&gt;
*Need a way of triggering simplified mode by a URL argument&lt;br /&gt;
*Need to bring look/feel as close as possible to original site so there is no culture shock from switching&lt;br /&gt;
*Need basic navigation items to duplicate at top and bottom of pages&lt;br /&gt;
*Need user preferences to be complete on a single page&lt;br /&gt;
&lt;br /&gt;
==Related Areas==&lt;br /&gt;
[[CssWork|CSS Work]] - CSS Working group for soylentnews.org&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5544</id>
		<title>MobileDesign</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5544"/>
		<updated>2014-03-06T02:40:50Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: /* Single Column Format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Single Column Format==&lt;br /&gt;
*This format is ideal for hand-held devices (all sizes) which are typically held in the portrait orientation.&lt;br /&gt;
*Principles are: &lt;br /&gt;
**No functional elements should appear along the bottom of the screen &lt;br /&gt;
**Most users are right handed therefore orientate buttons to the right of the screen where possible&lt;br /&gt;
**&lt;br /&gt;
*See [http://i.imgur.com/WVDZiAy.png This Sketch] and refer to the below for details.&lt;br /&gt;
**A - Username / Login option should be a tap/pull down with the usual log in/log out and viewing preferences. In small devices this can be iconified, but the menu may occupy the entire screen if required.&lt;br /&gt;
**B - Topic Bar - should be the topic group currently being viewed eg: &amp;quot;Technology&amp;quot; or &amp;quot;All Stories&amp;quot;. Tapping this should bring down a pull down list of topics for selection.&lt;br /&gt;
**D - Website Logo - tapping this should return to home page, it can also pull down a list of links to other major areas.&lt;br /&gt;
**E - Read More and other buttons - positioned to the right. They need to be at least 1cm tall and 1cm wide so that a finger can touch the button easily.&lt;br /&gt;
**F - Article Body - text needs to be 11 point equivalent minimum. Use em to be device independent if need be, but it's possible that experimentation will be required. Typographic and text layout guidelines are described elsewhere.&lt;br /&gt;
**G - Bottom of page needs to indicate that there is &amp;quot;more&amp;quot; below .. one way is to fade window contents to background color, or to black, to indicate that there is more to be found below.&lt;br /&gt;
**H - Story Icons - Clicking these should do something, possibly changing the story view category?&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
	<entry>
		<id>https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5543</id>
		<title>MobileDesign</title>
		<link rel="alternate" type="text/html" href="https://wiki.soylentnews.org/index.php?title=MobileDesign&amp;diff=5543"/>
		<updated>2014-03-06T02:35:37Z</updated>

		<summary type="html">&lt;p&gt;Mrbluze: Created page with &amp;quot;==Single Column Format== *This format is ideal for hand-held devices (all sizes) which are typically held in the portrait orientation. *Principles are:  **No functional elemen...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Single Column Format==&lt;br /&gt;
*This format is ideal for hand-held devices (all sizes) which are typically held in the portrait orientation.&lt;br /&gt;
*Principles are: &lt;br /&gt;
**No functional elements should appear along the bottom of the screen &lt;br /&gt;
**Most users are right handed therefore orientate buttons to the right of the screen where possible&lt;br /&gt;
**&lt;br /&gt;
*See [http://i.imgur.com/WVDZiAy.png This Sketch] and refer to the below for details.&lt;br /&gt;
**A - Username / Login option should be a tap/pull down with the usual log in/log out preferences. In small devices this can be iconified, but the menu may occupy the entire screen if required.&lt;br /&gt;
**B - Topic Bar - should consist of&lt;/div&gt;</summary>
		<author><name>Mrbluze</name></author>
	</entry>
</feed>