<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://connectedplaces.online/the-purpose-of-protocols/"/>
	<rdf:li rdf:resource="https://hitchdev.com/strictyaml/why/implicit-typing-removed/"/>
	<rdf:li rdf:resource="https://rednegra.net/blog/20260212-virtual-scroll/"/>
	<rdf:li rdf:resource="https://datatracker.ietf.org/doc/rfc8820/"/>
	<rdf:li rdf:resource="https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md"/>
	<rdf:li rdf:resource="https://velvetyne.fr/fonts/typefesse/"/>
	<rdf:li rdf:resource="https://designsystem.digital.gov/"/>
	<rdf:li rdf:resource="https://hidde.blog/popover-semantics/"/>
	<rdf:li rdf:resource="https://press.uchicago.edu/ucp/books/book/chicago/D/bo213648394.html"/>
	<rdf:li rdf:resource="https://www.c82.net/euclid/en/"/>
	<rdf:li rdf:resource="https://www.w3.org/WAI/ARIA/apg/"/>
	<rdf:li rdf:resource="https://doc.wikimedia.org/codex/latest/"/>
	<rdf:li rdf:resource="https://gitlab.com/edent/paper-prototype-css/"/>
	<rdf:li rdf:resource="https://mattweidner.com/2022/02/10/collaborative-data-design.html"/>
	<rdf:li rdf:resource="https://brianlovin.com/crit"/>
	<rdf:li rdf:resource="https://webflow.com/"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/data-monolith-to-mesh.html"/>
	<rdf:li rdf:resource="https://clig.dev/"/>
	<rdf:li rdf:resource="https://twitter.com/SanDiegoTRUST/status/1325835422350544904"/>
	<rdf:li rdf:resource="https://feathericons.com/"/>
	<rdf:li rdf:resource="http://flux.web.unc.edu/recommended-courses/"/>
	<rdf:li rdf:resource="http://udlguidelines.cast.org/"/>
	<rdf:li rdf:resource="http://fuben-eki.jp/whatsfuben-eki/"/>
	<rdf:li rdf:resource="https://publicdomainreview.org/collections/colour-wheels-charts-and-tables-through-history/"/>
	<rdf:li rdf:resource="https://v2.designsystem.digital.gov/"/>
	<rdf:li rdf:resource="https://subformapp.com/"/>
	<rdf:li rdf:resource="https://twitter.com/i/moments/994601867987619840"/>
	<rdf:li rdf:resource="http://microformats.org/wiki/namespaces-considered-harmful"/>
	<rdf:li rdf:resource="https://mapzen.com/blog/wof-website-redesign/"/>
	<rdf:li rdf:resource="https://www.designernews.co/stories/84443-redditors-design-worst-volume-sliders-possible"/>
	<rdf:li rdf:resource="https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates"/>
	<rdf:li rdf:resource="https://mapzen.com/blog/whosonfirst-api/#a-short-miserable-history-of-pagination"/>
	<rdf:li rdf:resource="https://cloud.google.com/apis/design/"/>
	<rdf:li rdf:resource="http://olasearch.com/articles/what-is-search-experience"/>
	<rdf:li rdf:resource="https://uxdesign.cc/design-better-forms-96fadca0f49c#.qrtbblghm"/>
	<rdf:li rdf:resource="http://www.fastcodesign.com/3053406/how-apple-is-giving-design-a-bad-name"/>
	<rdf:li rdf:resource="http://mrmrs.cc/"/>
	<rdf:li rdf:resource="http://www.economist.com/blogs/babbage/2013/05/evgeny-morozov-technology"/>
	<rdf:li rdf:resource="http://whoo.ps/2015/02/23/futures-of-text"/>
	<rdf:li rdf:resource="http://www.ibm.com/design/language/"/>
	<rdf:li rdf:resource="http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html"/>
	<rdf:li rdf:resource="http://monkey.org/~marius/unix-tools-hints.html"/>
	<rdf:li rdf:resource="http://www.narwhl.com/"/>
	<rdf:li rdf:resource="http://dl.acm.org/citation.cfm?id=2557265"/>
	<rdf:li rdf:resource="http://colorbrewer2.org/"/>
	<rdf:li rdf:resource="http://data.gov.uk/resources/uris"/>
	<rdf:li rdf:resource="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/60975/designing-URI-sets-uk-public-sector.pdf"/>
	<rdf:li rdf:resource="http://msdn.microsoft.com/en-us/library/ms997506.aspx"/>
	<rdf:li rdf:resource="http://msdn.microsoft.com/en-us/library/ms997577.aspx"/>
	<rdf:li rdf:resource="http://msdn.microsoft.com/en-us/library/ms997575.aspx"/>
	<rdf:li rdf:resource="http://queue.acm.org/detail.cfm?id=1805128"/>
	<rdf:li rdf:resource="http://desrist2009.ist.psu.edu/Papers/desrist2009_submission_14.pdf"/>
	<rdf:li rdf:resource="http://echo.iat.sfu.ca/library/snodgrass_design_hermeneutical.pdf"/>
	<rdf:li rdf:resource="http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/"/>
	<rdf:li rdf:resource="http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/"/>
	<rdf:li rdf:resource="http://mashable.com/2010/07/15/wireframing-tools/"/>
	<rdf:li rdf:resource="https://docs.google.com/document/pub?id=1GWTMLjqQsQS45FWwqNG9ztQTdGF48hQYpjQHR_d1WsI"/>
	<rdf:li rdf:resource="http://www.robohornet.org/"/>
	<rdf:li rdf:resource="https://github.com/robohornet/robohornet"/>
	<rdf:li rdf:resource="http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html"/>
	<rdf:li rdf:resource="http://grouplab.cpsc.ucalgary.ca/sketchbook/"/>
	<rdf:li rdf:resource="http://ro.ecu.edu.au/cgi/viewcontent.cgi?article=2611&amp;context=ecuworks"/>
	<rdf:li rdf:resource="http://projects.coe.uga.edu/dbr/"/>
	<rdf:li rdf:resource="http://subtlepatterns.com/"/>
	<rdf:li rdf:resource="http://agora.cs.vu.nl/wp-content/uploads/MScThesisArdjanvanNuland.pdf"/>
	<rdf:li rdf:resource="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/"/>
	<rdf:li rdf:resource="http://research.microsoft.com/apps/pubs/?id=156620"/>
	<rdf:li rdf:resource="http://www.designstaff.org/articles/story-centered-design-2012-03-22.html"/>
	<rdf:li rdf:resource="http://visionmedia.github.com/uikit/"/>
	<rdf:li rdf:resource="http://www.w3.org/WAI/demos/bad/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://connectedplaces.online/the-purpose-of-protocols/">
    <title>The Purpose of Protocols – Connected Places</title>
    <dc:date>2026-03-22T19:33:46+00:00</dc:date>
    <link>https://connectedplaces.online/the-purpose-of-protocols/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Stafford Beer, the management cybernetician, had a phrase for this kind of claim: ‘the purpose of a system is what it does.’ Not what it intends, not what its designers hope for, but what it produces. Applied to four decades of open protocol history, the pattern is consistent: protocol design can constrain how actors operate within a system, but it cannot ensure the conditions that keep the broader ecosystem functioning. The newer protocols engage with governance and power far more directly than their predecessors did, but the distance between architectural intent and operational reality has proven resistant to even the most thoughtful design.
]]></description>
<dc:subject>protocol design philosophy cybernetics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:009f109dbd86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:protocol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cybernetics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hitchdev.com/strictyaml/why/implicit-typing-removed/">
    <title>The Norway Problem - why StrictYAML refuses to do implicit typing and so should you - HitchDev</title>
    <dc:date>2026-02-22T20:43:13+00:00</dc:date>
    <link>https://hitchdev.com/strictyaml/why/implicit-typing-removed/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The most tragic aspect of this bug, however, is that it is intended behavior according to the YAML 1.2 specification. The real fix requires explicitly disregarding the spec - which is why most YAML parsers have it.

StrictYAML sidesteps this problem by ignoring key parts of the spec.]]></description>
<dc:subject>yaml standards parsing design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d26e6255116/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yaml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:parsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://rednegra.net/blog/20260212-virtual-scroll/">
    <title>Virtual Scrolling for Billions of Rows — Techniques from HighTable</title>
    <dc:date>2026-02-17T22:12:17+00:00</dc:date>
    <link>https://rednegra.net/blog/20260212-virtual-scroll/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[No need for a fake scroll bar. No need to render the table in a canvas. We use the Web platform. Thanks to these five techniques that rely on native HTML elements, hightable lets you navigate seamlessly through billions of rows of a remote data file, in the browser.]]></description>
<dc:subject>html css web design architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cf9777ba300f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://datatracker.ietf.org/doc/rfc8820/">
    <title>RFC 8820 - URI Design and Ownership</title>
    <dc:date>2026-02-16T18:39:43+00:00</dc:date>
    <link>https://datatracker.ietf.org/doc/rfc8820/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
   extensible naming system wherein each scheme's specification may
   further restrict the syntax and semantics of identifiers using that
   scheme."  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of substructure in URIs is often
   problematic.

   This document provides guidance on the specification of URI
   substructure in standards.]]></description>
<dc:subject>uri design structure politics economics standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8d636d09ed86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md">
    <title>system-exploration-g/src/system_prompt.md at main · simonw/system-exploration-g</title>
    <dc:date>2025-08-11T15:47:15+00:00</dc:date>
    <link>https://github.com/simonw/system-exploration-g/blob/main/src/system_prompt.md</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You are a web coding playground generating runnable code micro-apps ("sparks"). This guide helps you produce experiences that are not only functional but aesthetically refined and emotionally resonant.]]></description>
<dc:subject>web design manifesto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2eff42c282b6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:manifesto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://velvetyne.fr/fonts/typefesse/">
    <title>Typefesse - Velvetyne</title>
    <dc:date>2024-10-01T19:22:20+00:00</dc:date>
    <link>https://velvetyne.fr/fonts/typefesse/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Typefesse is a playful butt-shaped typeface in which the letters are rendered in such a way that the reading is done through the folds of the body.

The design of Typefesse is motivated by the surprising combination of two vocabularies, that of the body and that of the alphabet. The drawn alphabet reveals contortionist and playful creatures that either hide inside of it or that expose themselves to it. Is it the letter that defines the bodies' shapes, or is it the other way around? These creatures play with the viewer's gaze and fight against the lettershapes by disturbing their readability with their exuberance. The alphabet is laid bare and readers become spectator-voyeurs in spite of themselves. Typefesse is a typeface that generates a confusion between reading, seeing and spying. It's a titling font, although it has a surprising readability at small body sizes. Its three styles have been named in reference to the moon and its mysteries]]></description>
<dc:subject>fonts design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cedf568e2db4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fonts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://designsystem.digital.gov/">
    <title>USWDS: The United States Web Design System | U.S. Web Design System (USWDS)</title>
    <dc:date>2024-07-07T18:38:10+00:00</dc:date>
    <link>https://designsystem.digital.gov/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[USWDS provides principles, guidance, and code to help you design and build accessible, mobile-friendly government websites and digital services.]]></description>
<dc:subject>web design standards government</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:063f2cf6ef70/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:government"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hidde.blog/popover-semantics/">
    <title>Semantics and the popover attribute: which role to use when? | hidde.blog</title>
    <dc:date>2024-05-13T20:35:52+00:00</dc:date>
    <link>https://hidde.blog/popover-semantics/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With the new popover attribute in HTML, we can put elements in the top layer and allow them to disappear with ‘light dismiss’. This attribute adds behaviour, not semantics: you're supposed to add your own role when it makes sense. In this post, we'll look at different roles that could make sense for your popover-behaved elements.]]></description>
<dc:subject>html semantics design accessibility css ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:303efff5f1cd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://press.uchicago.edu/ucp/books/book/chicago/D/bo213648394.html">
    <title>The Design of Books: An Explainer for Authors, Editors, Agents, and Other Curious Readers, Berne</title>
    <dc:date>2024-04-12T22:08:34+00:00</dc:date>
    <link>https://press.uchicago.edu/ucp/books/book/chicago/D/bo213648394.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Seasoned designer Debbie Berne presents an accessible introduction to book design for authors, editors, and other book people.
]]></description>
<dc:subject>book design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:68d6c842f8bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:book"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.c82.net/euclid/en/">
    <title>Byrne’s Euclid</title>
    <dc:date>2023-02-18T00:28:34+00:00</dc:date>
    <link>https://www.c82.net/euclid/en/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A reproduction of Oliver Byrne’s celebrated work from 1847 plus interactive diagrams, cross references, and posters designed by Nicholas Rougeux.]]></description>
<dc:subject>web design geometry diagrams typography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9850a2de49d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geometry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:diagrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:typography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/WAI/ARIA/apg/">
    <title>ARIA Authoring Practices Guide | APG | WAI | W3C</title>
    <dc:date>2023-01-04T21:34:06+00:00</dc:date>
    <link>https://www.w3.org/WAI/ARIA/apg/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Learn to use the accessibility semantics defined by the Accessible Rich Internet Application (ARIA) specification to create accessible web experiences. This guide describes how to apply accessibility semantics to common design patterns and widgets. It provides design patterns and functional examples complemented by in-depth guidance for fundamental practices.

]]></description>
<dc:subject>html accessibility design patterns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b6f65c18a1af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://doc.wikimedia.org/codex/latest/">
    <title>Codex | Codex</title>
    <dc:date>2023-01-04T21:33:00+00:00</dc:date>
    <link>https://doc.wikimedia.org/codex/latest/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Codex is a toolkit for building user interfaces within the Wikimedia Design System.
]]></description>
<dc:subject>wikimedia wikipedia design ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a98a58d50106/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikimedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gitlab.com/edent/paper-prototype-css/">
    <title>Terence Eden / Paper Prototype CSS · GitLab</title>
    <dc:date>2022-06-04T19:08:18+00:00</dc:date>
    <link>https://gitlab.com/edent/paper-prototype-css/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CSS Designed to look a bit like a paper prototype.
]]></description>
<dc:subject>css design prototyping</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:09baf4b91923/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:prototyping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mattweidner.com/2022/02/10/collaborative-data-design.html">
    <title>Designing Data Structures for Collaborative Apps - Matthew Weidner</title>
    <dc:date>2022-05-10T00:45:01+00:00</dc:date>
    <link>https://mattweidner.com/2022/02/10/collaborative-data-design.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This blog post will teach you how to design CRDTs from the ground up. I’ll present a few simple CRDTs that are obviously correct, plus ways to compose them together into complicated whole-app CRDTs that are still obviously correct. I’ll also present principles of CRDT design to help guide you through the process. To cap it off, we’ll design a CRDT for a collaborative spreadsheet.

Ultimately, I hope that you will gain not just an understanding of some existing CRDT designs, but also the confidence to tweak them and create your own!]]></description>
<dc:subject>crdt collaboration distributed decentralization design howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8114caa4539a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:crdt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:decentralization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://brianlovin.com/crit">
    <title>Crit</title>
    <dc:date>2022-02-02T02:36:59+00:00</dc:date>
    <link>https://brianlovin.com/crit</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Crit is a comprehensive product design health report. It's a thorough usability, user interface, interaction, and visual design audit, and includes a redesign of a single page in your product with actionable suggestions for improvement.]]></description>
<dc:subject>design critique</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8a5a94401f2d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:critique"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webflow.com/">
    <title>Webflow: Create a custom website | No-code website builder</title>
    <dc:date>2021-12-09T01:58:04+00:00</dc:date>
    <link>https://webflow.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webflow is used by more than 3,500,000 designers and teams to create, collaborate on, and scale beautiful websites in a completely visual canvas — no coding needed. ]]></description>
<dc:subject>web design tool</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ee7a60cd6728/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tool"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/data-monolith-to-mesh.html">
    <title>How to Move Beyond a Monolithic Data Lake to a Distributed Data Mesh</title>
    <dc:date>2021-01-06T01:39:06+00:00</dc:date>
    <link>https://martinfowler.com/articles/data-monolith-to-mesh.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Many enterprises are investing in their next generation data lake, with the hope of democratizing data at scale to provide business insights and ultimately make automated intelligent decisions. Data platforms based on the data lake architecture have common failure modes that lead to unfulfilled promises at scale. To address these failure modes we need to shift from the centralized paradigm of a lake, or its predecessor data warehouse. We need to shift to a paradigm that draws from modern distributed architecture: considering domains as the first class concern, applying platform thinking to create self-serve data infrastructure, and treating data as a product.]]></description>
<dc:subject>distributed data architecture design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fb0f7990f392/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://clig.dev/">
    <title>Command Line Interface Guidelines</title>
    <dc:date>2020-12-11T22:23:59+00:00</dc:date>
    <link>https://clig.dev/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.]]></description>
<dc:subject>cli unix design standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c6e76abb6eee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cli"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/SanDiegoTRUST/status/1325835422350544904">
    <title>Twitter</title>
    <dc:date>2020-11-10T17:40:13+00:00</dc:date>
    <link>https://twitter.com/SanDiegoTRUST/status/1325835422350544904</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @gleemie: If you're a design or HCI person, esp a student, I want to make the clear that all that stuff you learn about participation, inclusion, etc doesn't mean a thing if there aren't laws that require transparency and accountability. Without it, design becomes risk mitigation. #design ]]></description>
<dc:subject>design</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bfa677c9e9fa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://feathericons.com/">
    <title>Feather – Simply beautiful open source icons</title>
    <dc:date>2020-10-10T18:27:43+00:00</dc:date>
    <link>https://feathericons.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Feather is a collection of simply beautiful open source icons. Each icon is designed on a 24x24 grid with an emphasis on simplicity, consistency, and flexibility.]]></description>
<dc:subject>design icons svg ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:aa06b6ecbf31/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:icons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:svg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://flux.web.unc.edu/recommended-courses/">
    <title>Recommended Courses | Future Leaders of User Experience</title>
    <dc:date>2020-01-28T19:29:37+00:00</dc:date>
    <link>http://flux.web.unc.edu/recommended-courses/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[FLUX believes that user experience design and human-computer interaction are extremely interdisciplinary fields, covering knowledge from fields like computer science, cognitive psychology, linguistics, and visual communication. We have grouped what we believe are relevant courses throughout UNC-CH which touch upon these topics.]]></description>
<dc:subject>userinterface design courses sils</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6879cfac43f2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:userinterface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:courses"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sils"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://udlguidelines.cast.org/">
    <title>UDL: The UDL Guidelines</title>
    <dc:date>2019-10-02T22:05:48+00:00</dc:date>
    <link>http://udlguidelines.cast.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The UDL Guidelines are a tool used in the implementation of Universal Design for Learning, a framework to improve and optimize teaching and learning for all people based on scientific insights into how humans learn. Learn more about the Universal Design for Learning framework from CAST. The UDL Guidelines can be used by educators, curriculum developers, researchers, parents, and anyone else who wants to implement the UDL framework in a learning environment. These guidelines offer a set of concrete suggestions that can be applied to any discipline or domain to ensure that all learners can access and participate in meaningful, challenging learning opportunities.]]></description>
<dc:subject>design reference teaching</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:44edca24dc98/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:teaching"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fuben-eki.jp/whatsfuben-eki/">
    <title>不便益って？｜不便益システム研究所</title>
    <dc:date>2019-08-21T01:00:20+00:00</dc:date>
    <link>http://fuben-eki.jp/whatsfuben-eki/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[不・便益ではありません。不便の益 (benefit of inconvenience) です。
不便で良かったこと、ありませんか？
便利とは，手間がかからず，頭を使わなくても良いことだとします． そうすると，不便で良かった事や，不便じゃなくちゃダメなことが，色々と見えてきます．]]></description>
<dc:subject>inconvenience design research</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:201898b87fe1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inconvenience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://publicdomainreview.org/collections/colour-wheels-charts-and-tables-through-history/">
    <title>Colour Wheels, Charts, and Tables Through History – The Public Domain Review</title>
    <dc:date>2019-07-22T10:46:12+00:00</dc:date>
    <link>https://publicdomainreview.org/collections/colour-wheels-charts-and-tables-through-history/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A chronology of various attempts through the last four centuries to visually organise and make sense of colour. A wide variety of forms and methods are represented: from simple wheels to multi-layered pyramids, from scientific systems to those based on the hues of human emotion. Many of the images are directly, or indirectly, sourced from Sarah Lowengard’s excellent The Creation of Color in Eighteenth-Century Europe – published electronically on Gutenberg-e in 2006 – a highly recommended read if you’re keen to find out more about the fascinating history of colour, and also background on many of the images below. Also check out Philip Ball’s Bright Earth: Art and the Invention of Color (2003) for a great look at how art, chemistry, and technology have interacted through the ages.]]></description>
<dc:subject>color design history inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cf0aab1127aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:color"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://v2.designsystem.digital.gov/">
    <title>USWDS: The United States Web Design System</title>
    <dc:date>2019-04-09T13:37:57+00:00</dc:date>
    <link>https://v2.designsystem.digital.gov/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[USWDS is a library of code, tools, and guidance to help government teams design and build fast, accessible, mobile-friendly government websites backed by user research and modern best practices.]]></description>
<dc:subject>css design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:27634b06024d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://subformapp.com/">
    <title>Subform | Dynamic layout meets direct manipulation</title>
    <dc:date>2018-10-05T01:39:59+00:00</dc:date>
    <link>https://subformapp.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Subform is a visual tool for creating dynamic UI layouts. It replaces drawing a lot of pictures—or the endless tweak-reload-tweak cycle—with direct editing and immediate visual feedback.]]></description>
<dc:subject>ui design tool</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1dbc7d9b3b88/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tool"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/i/moments/994601867987619840">
    <title>🔥 Design Tips</title>
    <dc:date>2018-06-03T17:22:35+00:00</dc:date>
    <link>https://twitter.com/i/moments/994601867987619840</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A collection of design tips]]></description>
<dc:subject>design ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:05aa454f6c2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://microformats.org/wiki/namespaces-considered-harmful">
    <title>namespaces considered harmful · Microformats Wiki</title>
    <dc:date>2018-01-23T20:47:16+00:00</dc:date>
    <link>http://microformats.org/wiki/namespaces-considered-harmful</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In particular namespaces for content are considered harmful (e.g. XML namespaces, QNames in attributes etc.).]]></description>
<dc:subject>xml rdf language design naming decentralization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4d4fc56451b6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:decentralization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mapzen.com/blog/wof-website-redesign/">
    <title>Redesigning and Rebuilding the Who's On First website · Mapzen</title>
    <dc:date>2017-08-22T16:22:35+00:00</dc:date>
    <link>https://mapzen.com/blog/wof-website-redesign/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[My name is Scott and I am an intern on the Mapzen data team this summer. I am also pursuing a graduate degree at the Carnegie Mellon School of Design.

At Mapzen, I am tasked with improving how Who’s On First (WOF) is presented to the world and increasing its accessibility to a wider range of users.

For the majority of my first three weeks at Mapzen, I have focused on the redesign and the rebuilding of the WOF website.]]></description>
<dc:subject>periodo design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2d21ecc9c880/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.designernews.co/stories/84443-redditors-design-worst-volume-sliders-possible">
    <title>Redditors design worst volume sliders possible – Designer News</title>
    <dc:date>2017-06-18T23:47:42+00:00</dc:date>
    <link>https://www.designernews.co/stories/84443-redditors-design-worst-volume-sliders-possible</link>
    <dc:creator>rybesh</dc:creator><dc:subject>design ui</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6865acc6671c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates">
    <title>KohaCon 2010 Open Library presentation - George Oates : George Oates : Free Download &amp; Streaming : Internet Archive</title>
    <dc:date>2017-04-04T18:28:14+00:00</dc:date>
    <link>https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An introduction to Open Library for the awesome open source Koha Open Source Library Software system.]]></description>
<dc:subject>libraries interface design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:629447983cf1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mapzen.com/blog/whosonfirst-api/#a-short-miserable-history-of-pagination">
    <title>A short miserable history of pagination</title>
    <dc:date>2017-04-04T18:21:49+00:00</dc:date>
    <link>https://mapzen.com/blog/whosonfirst-api/#a-short-miserable-history-of-pagination</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Pagination, the practice of chunking a lot of results in to smaller sets, shouldn’t be complicated. But it is. Because databases, after all these years, are still complicated beasts.]]></description>
<dc:subject>hypermedia design inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8d8c4eebb4fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloud.google.com/apis/design/">
    <title>API Design Guide  |  Cloud APIs  |  Google Cloud Platform</title>
    <dc:date>2017-03-05T15:43:26+00:00</dc:date>
    <link>https://cloud.google.com/apis/design/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a general design guide for networked APIs. It has been used inside Google since 2014 and is the guide we follow when designing Cloud APIs and other Google APIs. It is shared here to inform outside developers and to make it easier for us all to work together.

External developers may find it particularly useful when designing gRPC APIs for use with Google Cloud Endpoints, and we strongly recommend such developers use these design principles. However, we don't mandate its use for any non-Google developer and you can use Cloud Endpoints and/or gRPC without following the guide.

This guide applies to both REST APIs and RPC APIs, with specific focus on gRPC APIs. gRPC APIs use Protocol Buffers to define their API surface and API Service Configuration to configure their API services, including HTTP mapping, logging, and monitoring. HTTP mapping features are used by Google APIs and gRPC Cloud Endpoints APIs for JSON/HTTP to Protocol Buffers/RPC transcoding.

This guide is a living document and additions to it will be made over time as new style and design patterns are adopted and approved. In that spirit, it is never going to be complete and there will always be ample room for the art and craft of API design.]]></description>
<dc:subject>api design documentation architecture inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cfdd0c9895bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://olasearch.com/articles/what-is-search-experience">
    <title>What is search experience? - Ola Search</title>
    <dc:date>2017-01-24T14:17:34+00:00</dc:date>
    <link>http://olasearch.com/articles/what-is-search-experience</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An experience is what a person goes through and remembers. A search experience, therefore, is a person's feelings and memories of using search. People embrace pleasant experiences and reject awful ones. Experiences, however, are hard to design. They depend on many factors. The first step is to uncover and unpack them.]]></description>
<dc:subject>search design inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:12c839912d3a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://uxdesign.cc/design-better-forms-96fadca0f49c#.qrtbblghm">
    <title>Design Better Forms</title>
    <dc:date>2016-12-07T23:39:33+00:00</dc:date>
    <link>https://uxdesign.cc/design-better-forms-96fadca0f49c#.qrtbblghm</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Common mistakes designers make and how to fix them]]></description>
<dc:subject>ui design advice</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:296fe7cc83be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:advice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.fastcodesign.com/3053406/how-apple-is-giving-design-a-bad-name">
    <title>How Apple Is Giving Design A Bad Name</title>
    <dc:date>2015-11-17T17:06:25+00:00</dc:date>
    <link>http://www.fastcodesign.com/3053406/how-apple-is-giving-design-a-bad-name</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Apple is destroying design. Worse, it is revitalizing the old belief that design is only about making things look pretty. No, not so! Design is a way of thinking, of determining people’s true, underlying needs, and then delivering products and services that help them. Design combines an understanding of people, technology, society, and business. The production of beautiful objects is only one small component of modern design: Designers today work on such problems as the design of cities, of transportation systems, of health care. Apple is reinforcing the old, discredited idea that the designer’s sole job is to make things beautiful, even at the expense of providing the right functions, aiding understandability, and ensuring ease of use.]]></description>
<dc:subject>design hci</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6eda85451e5d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hci"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mrmrs.cc/">
    <title>mrmrs / designer + developer in hong kong</title>
    <dc:date>2015-10-12T11:45:41+00:00</dc:date>
    <link>http://mrmrs.cc/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Trying to make the web as fast as possible, highly readable, 100% responsive, and easy to navigate.

I like building tools that help make designing in the browser a little easier.]]></description>
<dc:subject>css design tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4303bb8beae1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.economist.com/blogs/babbage/2013/05/evgeny-morozov-technology">
    <title>Evgeny Morozov on technology: The folly of solutionism | The Economist</title>
    <dc:date>2015-04-14T15:04:06+00:00</dc:date>
    <link>http://www.economist.com/blogs/babbage/2013/05/evgeny-morozov-technology</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[EVGENY MOROZOV explains why the world's complex problems will not be solved by technology alone.]]></description>
<dc:subject>technology design critique inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2af7d1066303/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:critique"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://whoo.ps/2015/02/23/futures-of-text">
    <title>Futures of text | Whoops by Jonathan Libov</title>
    <dc:date>2015-03-01T17:05:44+00:00</dc:date>
    <link>http://whoo.ps/2015/02/23/futures-of-text</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Text is an incredibly comfortable medium. Text-based interaction is fast, fun, funny, flexible, intimate, descriptive and even consistent in ways that voice and user interface often are not. Always bet on text:

Text is the most socially useful communication technology. It works well in 1:1, 1:N, and M:N modes. It can be indexed and searched efficiently, even by hand. It can be translated. It can be produced and consumed at variable speeds. It is asynchronous. It can be compared, diffed, clustered, corrected, summarized and filtered algorithmically. It permits multiparty editing. It permits branching conversations, lurking, annotation, quoting, reviewing, summarizing, structured responses, exegesis, even fan fic. The breadth, scale and depth of ways people use text is unmatched by anything.]]></description>
<dc:subject>text ui messaging nlp analysis design mobile AI</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c46daf81681d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:AI"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ibm.com/design/language/">
    <title>IBM Design Language</title>
    <dc:date>2014-12-28T17:09:16+00:00</dc:date>
    <link>http://www.ibm.com/design/language/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The IBM Design Language is a set of living guidelines that communicates a brand promise through our products’ experiences. Our goal is to design for experiences that work together, work the same and work for our users.
We create many different kinds of products, so our language is designed to be more instructive than prescriptive. This effort is relatively new and intentionally crafted to evolve through feedback from product teams and users. We invite you to use our language and join the conversation at IBM Design.]]></description>
<dc:subject>design language framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab72d19eefaf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html">
    <title>Go To Hellman: Stop Making Web Surveillance Bugs by Mistake!</title>
    <dc:date>2014-12-08T02:16:08+00:00</dc:date>
    <link>http://go-to-hellman.blogspot.com/2014/12/stop-making-web-surveillance-bugs-by.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[If you care about user privacy and you have a website, here's what you should do:

Avoid loading images and other assets from 3rd party sites. consider self-hosting these.

When you use 3rd party hosted assets, use HTTPS references only!

Avoid loading static assets from domains that use Google Analytics and set id domain cookies.]]></description>
<dc:subject>privacy http web design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e80e0746f910/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://monkey.org/~marius/unix-tools-hints.html">
    <title>Hints for writing Unix tools</title>
    <dc:date>2014-10-21T16:08:01+00:00</dc:date>
    <link>http://monkey.org/~marius/unix-tools-hints.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A few established customs that you should take care to follow when writing new tools. While making a truly good tool can be an elusive goal, it isn’t difficult to avoid making a truly bad one. Unix demands good citizenry from its tools: it relies on a set of conventions to make things work, and importantly, to compose, well. Here follows a few key customs, often violated. These aren’t absolute requirements, but you should think long and hard before violating them.]]></description>
<dc:subject>unix interface design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bd2bbfefc72f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.narwhl.com/">
    <title>What is the RESTed NARWHL? | The RESTed NARWHL</title>
    <dc:date>2014-09-30T17:32:33+00:00</dc:date>
    <link>http://www.narwhl.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Where REST is an architectural style for APIs, NARWHL is a framework intended to provide a roadmap for those needing to implement an API using current best practices but flexible enough to grow into the future.

This site contains a set of API design recommendations you can implement today with the confidence that your API will be RESTful (level 3 according to the Richardson Maturity Model) and able to adapt to future iterations while still making it easier for developers to use.]]></description>
<dc:subject>rest apis design patterns inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5db109ac70c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dl.acm.org/citation.cfm?id=2557265">
    <title>Designing usable web forms</title>
    <dc:date>2014-07-15T03:34:01+00:00</dc:date>
    <link>http://dl.acm.org/citation.cfm?id=2557265</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This study reports a controlled eye tracking experiment (N = 65) that shows the combined effectiveness of 20 guidelines to improve interactive online forms when applied to forms found on real company websites. Results indicate that improved web forms lead to faster completion times, fewer form submission trials, and fewer eye movements. Data from subjective questionnaires and interviews further show increased user satisfaction. Overall, our findings highlight the importance for web designers to improve their web forms using UX guidelines.]]></description>
<dc:subject>usability design interface</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:af3cdc24df5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://colorbrewer2.org/">
    <title>ColorBrewer: Color Advice for Maps</title>
    <dc:date>2014-05-02T02:03:56+00:00</dc:date>
    <link>http://colorbrewer2.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This map does not depict actual data. Instead, it has been carefully designed to be a diagnostic tool for evaluating the robustness of individual color schemes.]]></description>
<dc:subject>color visualization design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8d8ef7630f69/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:color"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://data.gov.uk/resources/uris">
    <title>Creating URIs | data.gov.uk</title>
    <dc:date>2013-05-19T15:25:51+00:00</dc:date>
    <link>http://data.gov.uk/resources/uris</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document forms part of the data.gov.uk guidance about publishing Linked Data within the UK public sector.]]></description>
<dc:subject>uri design identifiers inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:537396217797/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/60975/designing-URI-sets-uk-public-sector.pdf">
    <title>Designing URI Sets for the UK Public Sector</title>
    <dc:date>2013-05-19T15:24:42+00:00</dc:date>
    <link>https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/60975/designing-URI-sets-uk-public-sector.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document defines the design considerations and guidance by which UK public sector Universal Resource Identifier (URI) sets should be developed and maintained. They are designed both to encourage those that definitively own reference data to make it available for re-use, and to give those that have data that could be linked, the confidence to re-use a URI set that is not under their direct control.]]></description>
<dc:subject>uri design identifiers inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f014e4dd3b43/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://msdn.microsoft.com/en-us/library/ms997506.aspx">
    <title>Microsoft Inductive User Interface Guidelines</title>
    <dc:date>2013-05-03T14:14:58+00:00</dc:date>
    <link>http://msdn.microsoft.com/en-us/library/ms997506.aspx</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This article describes a new user interface model called inductive user interface (IUI). Also called inductive navigation, the IUI model suggests how to make software applications simpler by breaking features into screens or pages that are easy to explain and understand. This IUI model is emerging in various Microsoft projects, most notably Money 2000. This article provides an introduction to IUI, rather than a firm, comprehensive set of guidelines.]]></description>
<dc:subject>interface ui usability design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:43056fe92e24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://msdn.microsoft.com/en-us/library/ms997577.aspx">
    <title>Usability in Software Design</title>
    <dc:date>2013-05-03T14:14:27+00:00</dc:date>
    <link>http://msdn.microsoft.com/en-us/library/ms997577.aspx</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper introduces the concept of usability and why it should be an important part of any software design project.]]></description>
<dc:subject>usability design inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3bfff5fa4bec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://msdn.microsoft.com/en-us/library/ms997575.aspx">
    <title>Usability in the Development Process</title>
    <dc:date>2013-05-03T14:13:23+00:00</dc:date>
    <link>http://msdn.microsoft.com/en-us/library/ms997575.aspx</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper discusses the iterative, cyclical design process, including the four tenets of user-centered design, two types of the product design process, and how usability activities fit into and benefit every phase of product development.]]></description>
<dc:subject>usability design inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0f20729ef99a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://queue.acm.org/detail.cfm?id=1805128">
    <title>A Tour through the Visualization Zoo - ACM Queue</title>
    <dc:date>2013-04-09T01:53:20+00:00</dc:date>
    <link>http://queue.acm.org/detail.cfm?id=1805128</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This article provides a brief tour through the "visualization zoo," showcasing techniques for visualizing and interacting with diverse data sets. In many situations, simple data graphics will not only suffice, they may also be preferable. Here we focus on a few of the more sophisticated and unusual techniques that deal with complex data sets. After all, you don't go to the zoo to see Chihuahuas and raccoons; you go to admire the majestic polar bear, the graceful zebra, and the terrifying Sumatran tiger. Analogously, we cover some of the more exotic (but practically useful!) forms of visual data representation, starting with one of the most common, time-series data; continuing on to statistical data and maps; and then completing the tour with hierarchies and networks. Along the way, bear in mind that all visualizations share a common "DNA"—a set of mappings between data properties and visual attributes such as position, size, shape, and color—and that customized species of visualization might always be constructed by varying these encodings.]]></description>
<dc:subject>visualization reference data design infoviz</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a6c04e31e8e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infoviz"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://desrist2009.ist.psu.edu/Papers/desrist2009_submission_14.pdf">
    <title>Building Theory in the Sciences of the Artificial</title>
    <dc:date>2013-01-18T21:44:19+00:00</dc:date>
    <link>http://desrist2009.ist.psu.edu/Papers/desrist2009_submission_14.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This essay extends Simon’s arguments in the  Sciences of the Artificial  to a critical examination of how theorizing in Information Technology disciplines should occur. The essay is framed around a number of fundamental questions that relate theorizing in the artificial sciences to the traditions of the philosophy of science. Theorizing in the artificial sciences is contrasted with theorizing in other branches of science and the applicability of the scientific method is questioned. The paper argues that theorizing should be considered in a holistic manner that links two modes of theorizing: an  interior mode with the how  of artifact construction studied and an  exterior mode with the what of existing artifacts studied. Unlike some representations in the design science movement the paper argues that the study of artifacts once constructed can not be passed back uncritically to the methods of traditional science. Seven principles for creating knowledge in IT disciplines are derived: (i) artifact system centrality; (ii) artifact purposefulness; (iii) need for design theory; (iv) induction and abduction in theory building; (v) artifact construction as theory building; (vi) interior and  exterior modes for theorizing; and (viii) issues with generality. The implicit claim is that consideration of these principles will improve knowledge creation and theorizing in design disciplines, for  both design science researchers and also for researchers using more traditional methods. Further, attention to these principles should lead to the creation of more useful and relevant knowledge.]]></description>
<dc:subject>design science theory</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:be349954264c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:theory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://echo.iat.sfu.ca/library/snodgrass_design_hermeneutical.pdf">
    <title>Snodgrass &amp; Coyne - 1997 - Is Designing Hermeneutical?</title>
    <dc:date>2013-01-18T15:33:45+00:00</dc:date>
    <link>http://echo.iat.sfu.ca/library/snodgrass_design_hermeneutical.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An atomistic language model is frequently used to codify what is seen as the logical sequence of steps in the design process. Following the critique of Wittgenstein, this language model, derived from Positivist theory, has been generally abandoned  by philosophers of language. It is argued here that despite its apparent successes in the short term, the model embodies a fundamental misunderstanding of the nature of the design process. Drawing on recent studies of language in philosophical hermeneutics, and especially  the  work  of  Hans-Georg  Gadamer,  the  authors  argue  that  design activity proceeds by way of a hermeneutical circle, involving the projection of preunderstandings and a dialogical structure of question and answer. Design does not fall within the domain of natural science with a base in formal logic, but belongs rather to the domain of the human and hermeneutical sciences with a base in the processes of  understanding  and  interpretation.  Atomistic  language  models  of  design  are antipathetic  to  hermeneutical  functioning,  and  impede  rather  than  assist  design understanding and practice.]]></description>
<dc:subject>design hermeneutics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6ef53f0be1d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hermeneutics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/">
    <title>T=Machine » Entity Systems: what makes good Components? good Entities?</title>
    <dc:date>2012-12-12T15:25:13+00:00</dc:date>
    <link>http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What makes a good Component?
How should I split my conceptual model into Entities and Components?
How should I split my algorithms and methods into Systems?]]></description>
<dc:subject>ECS design data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:62e94a6f4e72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ECS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/">
    <title>Chris Granger - Anatomy of a knockout</title>
    <dc:date>2012-12-12T15:10:58+00:00</dc:date>
    <link>http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So what we're doing is exploding all these monolithic objects apart, and turning entities in the game into simple groupings of components.]]></description>
<dc:subject>clojure games design data modeling ECS</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ac196608047b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:clojure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ECS"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mashable.com/2010/07/15/wireframing-tools/">
    <title>10 Free Wireframing Tools for Designers</title>
    <dc:date>2012-10-16T20:50:38+00:00</dc:date>
    <link>http://mashable.com/2010/07/15/wireframing-tools/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This post highlights 10 of the best free wireframing tools available, including standalone applications, web-based tools and browser add-ons.]]></description>
<dc:subject>design tools digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9737c68320dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.google.com/document/pub?id=1GWTMLjqQsQS45FWwqNG9ztQTdGF48hQYpjQHR_d1WsI">
    <title>iPhone 5 website teardown: How Apple compresses video using JPEG, JSON, and &lt;canvas&gt;</title>
    <dc:date>2012-09-26T13:39:32+00:00</dc:date>
    <link>https://docs.google.com/document/pub?id=1GWTMLjqQsQS45FWwqNG9ztQTdGF48hQYpjQHR_d1WsI</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How Apple is encoding video in JPEG.]]></description>
<dc:subject>web design video canvas</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2480a089499c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:canvas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.robohornet.org/">
    <title>RoboHornet</title>
    <dc:date>2012-09-24T23:55:54+00:00</dc:date>
    <link>http://www.robohornet.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RoboHornet is a benchmark designed around peformance pain points real web developers care about. ]]></description>
<dc:subject>testing QA performance web measurement design collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3df0b37aeba0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:QA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/robohornet/robohornet">
    <title>robohornet/robohornet</title>
    <dc:date>2012-09-24T23:55:11+00:00</dc:date>
    <link>https://github.com/robohornet/robohornet</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Every benchmark in the suite is designed to capture a performance pain point in a measurable way, such that an improvement in the benchmark's speed represents a lessening of felt pain. Any performance pain point is fair game—not just the ones that involve JavaScript. The suite uses a novel scoring system to represent the overall score as intuitively as possible. The community proposes performance painpoints to highlight and votes on which ones affect them most. A small group of stewards then distills the community's desires into regular, curated updates to the benchmark suite, allowing it to grow and evolve over time.]]></description>
<dc:subject>performance testing collaboration design measurement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f16d8411e441/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html">
    <title>RoboHornet: The Next Big Thing In Browser Benchmarking : RoboHornet: The Top Five Browsers, Tested And Ranked</title>
    <dc:date>2012-09-24T23:53:08+00:00</dc:date>
    <link>http://www.tomshardware.com/reviews/robohornet-web-browser-performance,3303.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RoboHornet is a framework for a scalable, evolving performance metric. The “benchmark” is actually a modular suite of performance tests. These tests are created and voted on by a community of Web designers and developers, with standards boards and other Web heavyweights acting as stewards. We can confirm that Google, Facebook, Microsoft, and Mozilla are currently listed as stewards. The browser vendors and other Web companies can also get involved as technical advisers to the project. Even regular users can contribute to RoboHornet by raising issues, voting up existing issues, or even writing benchmarks.]]></description>
<dc:subject>design testing performance metrics web collaboration measurement inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5c23b9d14584/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://grouplab.cpsc.ucalgary.ca/sketchbook/">
    <title>iLab Cookbook - Sketching User Experiences: The Workbook</title>
    <dc:date>2012-09-17T03:21:33+00:00</dc:date>
    <link>http://grouplab.cpsc.ucalgary.ca/sketchbook/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this book, you will learn, through step-by-step instructions and exercises, various sketching methods that will let you express your design ideas about user experiences across time. Collectively, these methods will be your sketching repertoire: a toolkit where you can choose the method most appropriate for developing your ideas, which will help you cultivate a culture of experience-based design and critique in your workplace.
Features standalone modules detailing methods and exercises for practitioners who want to learn and develop their sketching skills
Extremely practical, with illustrated examples detailing all steps on how to do a method
Excellent for individual learning, for classrooms, and for a team that wants to develop a culture of design practice
Perfect complement to Buxton's Sketching User Experience or any UX text
]]></description>
<dc:subject>design textbook digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3ea10fd81f6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:textbook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ro.ecu.edu.au/cgi/viewcontent.cgi?article=2611&amp;context=ecuworks">
    <title>Design-based research and doctoral students: Guidelines for preparing a dissertation proposal</title>
    <dc:date>2012-09-13T19:03:25+00:00</dc:date>
    <link>http://ro.ecu.edu.au/cgi/viewcontent.cgi?article=2611&amp;context=ecuworks</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[At first glance, design-based research may appear to be such a long-term and intensive approach to educational inquiry that doctoral students, most of whom expect to complete their Ph.D.  degree in 4-5 years, should not attempt to adopt this approach for their doctoral dissertations. In this paper, we argue that design-based research is feasible for doctoral students, and that candidates should be encouraged to engage in it. More specifically, we describe the components of a dissertation proposal or prospectus that utilizes design-based research methods in the context of educational technology research.
]]></description>
<dc:subject>design research</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:665a96f93d45/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://projects.coe.uga.edu/dbr/">
    <title>Design-based Research</title>
    <dc:date>2012-09-13T19:02:27+00:00</dc:date>
    <link>http://projects.coe.uga.edu/dbr/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Introduction to design research created by instructional technology PhD students at the University of Georgia.]]></description>
<dc:subject>design research</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f7370617fbde/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://subtlepatterns.com/">
    <title>Subtle Patterns | Free textures for your next web project</title>
    <dc:date>2012-08-22T13:33:51+00:00</dc:date>
    <link>http://subtlepatterns.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A high quality resource for anyone in need of tilable textured patterns.]]></description>
<dc:subject>design graphics patterns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:78c27311147f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:graphics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://agora.cs.vu.nl/wp-content/uploads/MScThesisArdjanvanNuland.pdf">
    <title>Towards Cultural Heritage Communities Online</title>
    <dc:date>2012-07-31T16:15:28+00:00</dc:date>
    <link>http://agora.cs.vu.nl/wp-content/uploads/MScThesisArdjanvanNuland.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web technology enables cultural heritage institutions to provide access to their collections to anyone interested.  However, in order to be able to interpret and analyze collection objects online, a contextual representation is necessary. This research explores whether existing communities can be addressed in order to complement this context, and evaluates an event-centered representation of objects. The ﬁrst study comprised of a focus group session with 5 people having roots in the Dutch Indies.  We collected information about their sense of community, and how they shared their memories with others.  In the second study, 22 pairs of high school pupils we asked to answer a historical question using an eventbased collection browser. We analyzed their answers on the question and collected feedback on their experiences. The main results from the focus group indicated that witnesses of historical events have a strong sense of community with their peers. They share their memories by visiting schools, making art, and in books.  They see it as their duty to continue doing this both offine and online. Results of the user study show that event-based representation is successful for ﬁnding the right objects, as a skeleton for answering a historical question. However, additional contextual background information is necessary for pupils to answer the question suﬃciently. To evolve the Agora collection browser into a social platform, the construction of narratives should be emphasized. Enabling users to add, rate and review external sources should provide background information on objects and events. Finally, supporting witnesses and interested lay people to share their own narratives, enriched with text and images, brings more context and information into the platform, giving new insight to all participants.]]></description>
<dc:subject>events narrative history digitalhumanities design research</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:efa19aff2f18/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/">
    <title>Document Design Matters (Erik Wilde and Robert J. Glushko)</title>
    <dc:date>2012-07-01T12:43:09+00:00</dc:date>
    <link>http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The classical approach to the data aspect of system design distinguishes conceptual, logical, and physical models. Models of each type or level are governed by metamodels that specify the kinds of concepts and constraints that can be used by each model; in most cases metamodels are accompanied by languages for describing models. For example, in database design, conceptual models usually conform to the Entity-Relationship (ER) metamodel (or some extension of it), the logical model maps ER models to relational tables and introduces normalization, and the physical model handles implementation issues such as possible denormalizations in the context of a particular database schema language. In this modeling methodology, there is a single hierarchy of models that rests on the assumption that one data model spans all modeling levels and applies to all the applications in some domain. The one true model approach assumes homogeneity, but this does not work very well for the Web. The Web as a constantly growing ecosystem of heterogeneous data and services has challenged a number of practices and theories about the design of IT landscapes. Instead of being governed by one true model used by everyone, the underlying assumption of top-down design, Web data and services evolve in an uncoordinated fashion. As a result, a fundamental challenge with Web data and services is matching and mapping local and often partial models that not only are different models of the same application domain, but also differ, implicitly or explicitly, in their associated metamodels.]]></description>
<dc:subject>models xml webservices inls520 documents design inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ba8fca0a8044/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://research.microsoft.com/apps/pubs/?id=156620">
    <title>The Future of Writing - Microsoft Research</title>
    <dc:date>2012-05-21T00:10:00+00:00</dc:date>
    <link>http://research.microsoft.com/apps/pubs/?id=156620</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Future of Writing was a design project commisioned by Microsoft Research Cambridge and the Microsoft Office team from the Royal College of Art in London. In this project five teams of design alumni from the college took a speculative approach to looking at the way in which authorship may change in the future. The result was five very diverse directions, described using video, text, images and interactive prototypes. This document describes the ideas, research and output of this project in detail.]]></description>
<dc:subject>writing design research</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:57ec6524af61/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.designstaff.org/articles/story-centered-design-2012-03-22.html">
    <title>Design Staff – Story-centered design: Hacking your brain to think like a user</title>
    <dc:date>2012-04-03T02:18:27+00:00</dc:date>
    <link>http://www.designstaff.org/articles/story-centered-design-2012-03-22.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We were thinking of the product as a set of screens. But there’s a problem with working this way: it’s not at all how people experience the product in real life. People use products in little flows that last anywhere from 30 seconds to a few minutes.

A user might first notice your product in a search result, browse around the product for a minute, and then leave. They might come back, sign up, and then leave again. They might open an email from the product, come back, make a purchase, and leave. Each of these little stories is a way that people actually experience your product.]]></description>
<dc:subject>design storyboard narrative</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ea478da384da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storyboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://visionmedia.github.com/uikit/">
    <title>UIKit - Modern UI components for a modern web</title>
    <dc:date>2012-02-04T23:31:13+00:00</dc:date>
    <link>http://visionmedia.github.com/uikit/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[UIKit is a small collection of flexible, decoupled components for the modern web. With an emphasis on structure-only styling making it it simple to apply application specific styling.]]></description>
<dc:subject>javascript ui code css design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e9c9d230a688/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/WAI/demos/bad/">
    <title>Before and After Demonstration: Overview</title>
    <dc:date>2012-02-01T20:10:59+00:00</dc:date>
    <link>http://www.w3.org/WAI/demos/bad/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Before and After Demonstration is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG).]]></description>
<dc:subject>accessibility interface design standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:85a0d73b99d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>