<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Clarify.io - Behind the Scenes</title><link href="../." rel="alternate"></link><link href=".././feeds/all.atom.xml" rel="self"></link><id>../.</id><updated>2012-03-28T18:10:00Z</updated><entry><title>A Look At The Embedding Feature</title><link href=".././a-look-at-the-embedding-feature.html" rel="alternate"></link><updated>2012-03-28T18:10:00Z</updated><author><name>Clarify.io - Behind the Scenes</name></author><id>.././a-look-at-the-embedding-feature.html</id><summary type="html">&lt;p&gt;A nice feature of Clarify is embedding. It's still in the very beginning, you're already able to embed the comments layer. Think of embedding in your wiki, issue tracker or in presentations. No more drawing of dots in Photoshop &amp;amp; Co, struggling with aligning and stuff like that.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Clarify Embedding Feature" src="http://dl.dropbox.com/u/5923660/clarify/embed-feature.png"&gt;&lt;/p&gt;
&lt;p&gt;The dots are rendered as markup into the image. This allows us to add more behaviour to the comment dots in the future. Think about linking to detail pages, etc.&lt;/p&gt;
&lt;h2&gt;Example&lt;/h2&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://beta.clarify.io/embed/UbjkDsu1/800&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;script type="text/javascript" src="http://beta.clarify.io/embed/UbjkDsu1/800"&gt;&lt;/script&gt;

&lt;h2&gt;Small Width Example&lt;/h2&gt;
&lt;p&gt;You can also choose a smaller size by changing the width parameter. The comment numbers will be adjusted in size to the new width. Take a look at the following example, with 400 pixels width:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://beta.clarify.io/embed/UbjkDsu1/400&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;script type="text/javascript" src="http://beta.clarify.io/embed/UbjkDsu1/400"&gt;&lt;/script&gt;

&lt;p&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Have you already signed up for the Beta? Not?&lt;/strong&gt; Hurry on to get your invite as an early adopter on &lt;a href="http://clarify.io"&gt;Clarify.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For updates, follow &lt;a href="http://www.twitter.com/clarify_io"&gt;@clarify_io&lt;/a&gt; or &lt;a href="http://www.twitter.com/rogerdudler"&gt;@rogerdudler&lt;/a&gt; on Twitter and read this blog.&lt;/p&gt;
&lt;h2&gt;Further reading:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/a-look-at-the-project-sidebar.html"&gt;A Look At The Project Sidebar&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/its-all-about-color.html"&gt;It's All About: Color&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/say-hello-to-clarify.html"&gt;Say Hello To Clarify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://twitter.com/share" class="twitter-share-button" data-via="rogerdudler"&gt;Tweet&lt;/a&gt;
&lt;script&gt;!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");&lt;/script&gt;&lt;/p&gt;</summary><category term="embedding"></category><category term="feature"></category></entry><entry><title>A Look At The Project Sidebar</title><link href=".././a-look-at-the-project-sidebar.html" rel="alternate"></link><updated>2012-03-23T21:10:00Z</updated><author><name>Clarify.io - Behind the Scenes</name></author><id>.././a-look-at-the-project-sidebar.html</id><summary type="html">&lt;p&gt;Clarify allows you to manage multiple projects within your workspace. You can see the screen count on every project, delete it or change settings like e.g. colors for the comment dots or later resolutions or browser support. Here is a screen of the recently pushed design of the project sidebar.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Project Sidebar" src="http://dl.dropbox.com/u/5923660/clarify/project-sidebar.png"&gt;&lt;/p&gt;
&lt;p&gt;I've planned to add a notification indicator on top of the screen count (red dot) with the number of new notifications on this project. This is not implemented yet, but shows where it goes when thinking about team collaboration.&lt;/p&gt;
&lt;p&gt;I try to make every interaction as simple and comfortable as possible. Without too much noise. For example the creation of projects.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Project Sidebar: Add Project" src="http://dl.dropbox.com/u/5923660/clarify/project-sidebar-add-project.png"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Have you already signed up for the Beta? Not?&lt;/strong&gt; Hurry on to get your invite as an early adopter on &lt;a href="http://clarify.io"&gt;Clarify.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For updates, follow &lt;a href="http://www.twitter.com/clarify_io"&gt;@clarify_io&lt;/a&gt; or &lt;a href="http://www.twitter.com/rogerdudler"&gt;@rogerdudler&lt;/a&gt; on Twitter and read this blog.&lt;/p&gt;
&lt;p&gt;Further reading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/its-all-about-color.html"&gt;It's All About: Color&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/say-hello-to-clarify.html"&gt;Say Hello To Clarify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://twitter.com/share" class="twitter-share-button" data-via="rogerdudler"&gt;Tweet&lt;/a&gt;
&lt;script&gt;!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");&lt;/script&gt;&lt;/p&gt;</summary><category term="sidebar"></category><category term="feature"></category></entry><entry><title>It's All About: Color</title><link href=".././its-all-about-color.html" rel="alternate"></link><updated>2012-03-22T21:20:00Z</updated><author><name>Clarify.io - Behind the Scenes</name></author><id>.././its-all-about-color.html</id><summary type="html">&lt;p&gt;In the process of bringing a design to life, you need to decide how you describe colors and their usage. You probably want to add &lt;strong&gt;color names&lt;/strong&gt; (it's easier to talk about them), you want to know all the values, especially the &lt;strong&gt;HEX&lt;/strong&gt; code and &lt;strong&gt;RGB(A)&lt;/strong&gt; values. There are &lt;strong&gt;gradients&lt;/strong&gt; (with two or more colors). You need to know &lt;strong&gt;where these colors are used&lt;/strong&gt; in your screens and you probably want to provide a nice &lt;strong&gt;documentation&lt;/strong&gt; for your client. This is what I thought it should be.&lt;/p&gt;
&lt;h1&gt;Color Picker&lt;/h1&gt;
&lt;p&gt;An important operation in the workflow is picking colors. Therefore, I've developed a color picker for Clarify, which allows you to pick colors directly in your browser. One challenge was, that it had to be very accurate. For this reason, there is a zoom tool, which allows pixelperfect color picking.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Color Picker" src="http://dl.dropbox.com/u/5923660/clarify/colorpicker.png"&gt;&lt;/p&gt;
&lt;p&gt;Normally, a picked color will be added to a CSS file and everyone will forget about it. Sometimes, there is also a styleguide for the client, for further use. In Clarify, every color you pick is stored in a database. If you pick a color twice, it will just create a reference to a library color (per project).&lt;/p&gt;
&lt;h1&gt;Color Library&lt;/h1&gt;
&lt;p&gt;Every color you pick is registered in your project and a reference to that color is created on the screen. You're able to keep your projects color library clean, reuse colors from the library in other screens or create a LESS template from your library.&lt;/p&gt;
&lt;h1&gt;Color Names&lt;/h1&gt;
&lt;p&gt;I thought it would be nice to get a name proposal for a color you pick. My plan is to implement an algorithm, which proposes a nearly accurate name &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" rel="footnote"&gt;1&lt;/a&gt;&lt;/sup&gt; for the picked color for better reference.&lt;/p&gt;
&lt;h1&gt;Styleguide&lt;/h1&gt;
&lt;p&gt;As a future reference, it's useful to create a color styleguide. I personally really like the color styleguide from &lt;a href="http://www.colorschemer.com"&gt;ColorSchemer&lt;/a&gt;. I'll probably take this one as a base template. This styleguide will be just a listing of the project or screens color library. Because the data is in a database, no problem.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Color Library from ColorSchemer" src="http://dl.dropbox.com/u/5923660/clarify/colors.png"&gt;&lt;/p&gt;
&lt;h1&gt;LESS&lt;/h1&gt;
&lt;p&gt;Out of the library, you can now generate a LESS template. Let's have a look at the following example.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;@baby-yellow: #ecc649;
@peace-and-quiet: #edae3c;
@neuron-deflated: #ba602b;
@deep-coral: #a24236;
@auberginee: #5f0126;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Now you're able to use these color variables in your project. That's nice!&lt;/p&gt;
&lt;h1&gt;Roadmap&lt;/h1&gt;
&lt;p&gt;Some of the needed functionality is already implemented in Clarify, but a lot of them are just planned yet. But, the architecture of Clarify allows an easy access to every definition you make during your workflow and allows to easy create additional outputs as styleguides or LESS templates. These features will be added soon.&lt;/p&gt;
&lt;p&gt;Think of a nice looking styleguide, which you can deliver to your clients, just out of the box. You'll never miss that again.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Wanna test those tasty features?&lt;/strong&gt; Register now as a beta tester on &lt;a href="http://clarify.io"&gt;Clarify.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Further reading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/an-api-preview.html"&gt;An API Preview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/say-hello-to-clarify.html"&gt;Say Hello To Clarify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://twitter.com/share" class="twitter-share-button" data-via="rogerdudler"&gt;Tweet&lt;/a&gt;
&lt;script&gt;!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");&lt;/script&gt;&lt;/p&gt;
&lt;div class="footnote"&gt;
&lt;hr&gt;
&lt;ol&gt;
&lt;li id="fn:1"&gt;
&lt;p&gt;One example of a color name reference is the &lt;a href="http://en.wikipedia.org/wiki/List_of_colors"&gt;List of Colors&lt;/a&gt; on Wikipedia&amp;#160;&lt;a href="#fnref:1" rev="footnote" title="Jump back to footnote 1 in the text"&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;</summary><category term="color"></category><category term="feature"></category></entry><entry><title>An API Preview</title><link href=".././an-api-preview.html" rel="alternate"></link><updated>2012-03-22T20:20:00Z</updated><author><name>Clarify.io - Behind the Scenes</name></author><id>.././an-api-preview.html</id><summary type="html">&lt;p&gt;To make it easy for innovative developers out there to connect their tools with Clarify, I've added an API from the beginning. The whole application is built on super-simple web services from the ground up. I'll add the documentation for the calls after releasing the first version. But for a first impression, check the services below.&lt;/p&gt;
&lt;h1&gt;Comment API&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;/api/comment/get/&lt;strong&gt;{screen}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/comment/add/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/comment/move/&lt;strong&gt;{id}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/comment/resize/&lt;strong&gt;{id}&lt;/strong&gt;/&lt;strong&gt;{width}&lt;/strong&gt;/&lt;strong&gt;{height}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/comment/update/&lt;strong&gt;{id}&lt;/strong&gt;
&lt;em&gt;Parameter:&lt;/em&gt; content=your comment&lt;/li&gt;
&lt;li&gt;/api/comment/delete/&lt;strong&gt;{id}&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Color API&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;/api/color/add/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;/&lt;strong&gt;{hex}&lt;/strong&gt;/&lt;strong&gt;{alpha}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/color/add/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;/&lt;strong&gt;{color}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/color/get/&lt;strong&gt;{screen}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/color/delete/&lt;strong&gt;{id}&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Measure API&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;/api/measure/add/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;/&lt;strong&gt;{width}&lt;/strong&gt;/&lt;strong&gt;{height}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/measure/get/&lt;strong&gt;{screen}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/measure/move/&lt;strong&gt;{id}&lt;/strong&gt;/&lt;strong&gt;{x}&lt;/strong&gt;/&lt;strong&gt;{y}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/measure/resize/&lt;strong&gt;{id}&lt;/strong&gt;/&lt;strong&gt;{width}&lt;/strong&gt;/&lt;strong&gt;{height}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/measure/delete/&lt;strong&gt;{id}&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Screen API&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;/api/screen/add/&lt;strong&gt;{project}&lt;/strong&gt;
&lt;em&gt;Parameter:&lt;/em&gt; file=…&lt;/li&gt;
&lt;li&gt;/api/screen/delete/&lt;strong&gt;{screen}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/screen/image/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{width}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/screen/thumbnail/&lt;strong&gt;{screen}&lt;/strong&gt;/&lt;strong&gt;{width}&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;/api/screen/embed/&lt;strong&gt;{screen}&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Project API&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;/api/project/add/
&lt;em&gt;Parameter:&lt;/em&gt; name=…&lt;/li&gt;
&lt;li&gt;/api/project/delete/&lt;strong&gt;{id}&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This API is heavily in development and is subject to change. But I want you to know in which direction it's going. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Wanna be the first to write a Clarify App using the API?&lt;/strong&gt; Register now as a beta tester on &lt;a href="http://clarify.io"&gt;Clarify.io&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://twitter.com/share" class="twitter-share-button" data-via="rogerdudler"&gt;Tweet&lt;/a&gt;
&lt;script&gt;!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");&lt;/script&gt;&lt;/p&gt;</summary><category term="api"></category></entry><entry><title>Say Hello To Clarify!</title><link href=".././say-hello-to-clarify.html" rel="alternate"></link><updated>2012-03-22T19:23:30Z</updated><author><name>Clarify.io - Behind the Scenes</name></author><id>.././say-hello-to-clarify.html</id><summary type="html">&lt;p&gt;As a software developer, who does a lot of frontend work &lt;a href="http://www.twitter.com/namics"&gt;@Namics&lt;/a&gt; and sometimes creates his own &lt;a href="http://forrst.com/people/pixeldude/posts"&gt;designs&lt;/a&gt;, my goal is always to improve my workflow for projects. I asked myself, why I need to open up Photoshop for picking colors or adding missing measurements by panning &amp;amp; zooming around? When I add them, why do I need to write them down into a documentation as well? Too much work for a lazy developer :) In addition, I thought it would be nice, to put some reproducable structure into styleguides I receive for projects. I thought about the possibilities of having those information stored in a database. Think of outputs like Styleguides, &lt;a href="http://lesscss.org"&gt;LESS&lt;/a&gt; Templates, &lt;a href="http://www.terrifically.org"&gt;Terrific&lt;/a&gt; Modules. Impressive, isn't it?&lt;/p&gt;
&lt;p&gt;&lt;img alt="Clarify Landing Page" src="http://dl.dropbox.com/u/5923660/clarify/clarify-landing.png"&gt;&lt;/p&gt;
&lt;p&gt;I decided to start a project based on this initial thoughts. I created a screen management interface with things like annotations à la &lt;a href="http://notableapp.com"&gt;Notable&lt;/a&gt;, a color picker or measuring tools, all usable directly in your browser. The feedback from my work friends was really positive, therefore I worked hard to improve it. I added support for embedding, added an API and Twitter authentication.&lt;/p&gt;
&lt;p&gt;I'm currently working on the first private beta release, which will be available in the next few weeks to a small group of early adopters.&lt;/p&gt;
&lt;h1&gt;Looking for testers&lt;/h1&gt;
&lt;p&gt;This week, I've published a landing page, where interested developers &amp;amp; designers can sign up as beta users. My plan is to invite about 50 people in the first round. I'll try to choose them wisely, because they are really important for the success of the product. So, I invite you to join the program as well on &lt;a href="http://clarify.io"&gt;Clarify.io&lt;/a&gt;. Thanks!&lt;/p&gt;
&lt;p&gt;Stay updated by following &lt;a href="http://www.twitter.com/rogerdudler"&gt;@rogerdudler&lt;/a&gt; on Twitter or by subscribing to the &lt;a href="http://blog.clarify.io/feeds/all.atom.xml"&gt;blog feed&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Further reading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/its-all-about-color.html"&gt;It's All About: Color&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.clarify.io/an-api-preview.html"&gt;An API Preview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vimeo.com/38098903"&gt;Watch the Preview Video&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://blog.namics.com/2012/03/clarify-ein-toolkit-fur-den-frontend-workflow.html"&gt;Clarify - A Frontend Development Toolkit (German)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://twitter.com/share" class="twitter-share-button" data-via="rogerdudler"&gt;Tweet&lt;/a&gt;
&lt;script&gt;!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");&lt;/script&gt;&lt;/p&gt;</summary><category term="idea"></category><category term="progress"></category><category term="beta"></category></entry></feed>