tag does a perfectly good job. I’ve seen themes that have shortcodes for quotes, citations and headers but no support for the same styling with HTML tags. This is a big no-no. Many users will switch from theme to theme and will already have content on their website when they activate yours. HTML tags will stay the same, but shortcodes vary from theme to theme. Don’t force the user to go back through all of their content just to add your custom shortcodes. Use shortcodes only to execute functions, not to apply styling. There may be a few exceptions, such as to wrap a message in complicated HTML, but if you’re simply adding a class, then adding it to the “Format” menu in the post editor’s kitchen sink makes more sense. A great tutorial was recently published by Luke McDonald that details how to add your own styles to the drop-down menu in the visual editor, giving you one more reason not to use shortcodes to style elements. Plugin Territory Don’t include options for things that should really be added with existing plugins; for example, Google Analytics and favicons. I hear someone in the back asking, “Why not include such things?” Well, person in the back, what if the user decides to switch themes, even to another of yours? They would lose all of that information and have to figure out how to get it back. The option is unnecessary, would make the code overly complicated, and would cause trouble when the user switches themes. Include only options that alter functionality that is unique to your theme; otherwise it’s better suited to a plugin. Further Resources “Theming for the Masses,” Michael Fields Michael’s talk from WordCamp Seattle 2011. “Right To Left Language Support,” WordPress Codex Options Framework Plugin, Devin Price A great framework for quickly putting together an options page for your theme. “An Alternative to the Shortcode Madness, Part 1,” Luke McDonald Learn how to add your own styles to the drop-down menu in the visual editor. “Translating WordPress,” WordPress Codex “WordPress 3.0 Theme Tip: Custom Backgrounds,” Otto on WordPress “Custom Headers,” WordPress Codex (al) © Sawyer Hollenshead for Smashing Magazine, 2011. ]]> Developer's_Toolbox https://pinboard.in/u:pesh2000/b:3fbad8856566/ 2011-10-28T17:36:49+00:00 http://www.noupe.com/wordpress/50-great-free-wordpress-themes-from-2011.html pesh2000 Smashing_Network https://pinboard.in/u:pesh2000/b:1fc9a8640982/ 2011-10-27T06:54:36+00:00 http://speckyboy.com/2011/10/26/sliders-in-web-design-45-creative-examples/ pesh2000 Web_Design Web_Inspiration app Application button design dev development forms Graphic Inspiration magazine minimal Mobile Showcase theme web https://pinboard.in/u:pesh2000/b:f2218cd06cb0/ 2011-10-26T11:16:18+00:00 http://vandelaydesign.com/blog/social-media/facebook-pages/ pesh2000 Smashing_Network https://pinboard.in/u:pesh2000/b:c3d6f742e127/ 2011-10-25T22:31:01+00:00 http://blog.kissmetrics.com/seo-for-ceos/ pesh2000 of your pages is critical. It’s read from left to right in terms of importance, so once you’ve carefully chosen the keyword phrase(s) you’re trying to rank for, a good, simple formula for page titles can look like this: Primary keyword phrase | Secondary keyword phrase (optional) | Company name Meta description. This is the little blurb search engines will show when a page on your site shows up in search results. Make it short and unique, including your top keyword phrase if it fits naturally. Copy. Each page on your site should contain, at the very least, a few sentences with organized headers describing what the page is about. On your homepage, that means spelling out what you do in simple language that both humans and machines can understand. 2. Getting relevant, good quality sites to link to yours Link building is like bridge building. It takes time and sweat. But without strong inbound links, your on-page HTML changes will hardly help you rank. Even one or two powerful links from good sites can funnel “SEO authority” to your site. When negotiating a link, be sure to get specific about the anchor text. 3. Some technical stuff that sounds pretty complicated but isn’t SEO best practices dictate that you submit a sitemap, use proper redirects and descriptive image alt tags, develop a structured system of internal links to indicate the relative importance of your site’s respective pages to the search engines, and execute on a slew of other minutia in order to achieve organic search nirvana. I’m going to recommend focusing on #1 and #2 above as a top priority. Once that’s in motion, you can attack these tasks, but don’t let them overwhelm your team into paralysis. Choose your Cast of Characters to get the Job Done 1. Excel Nerd / Research Ninja. You want a super smart, analytical team player for this role. This person crosses their t’s and dots their i’s. Maybe they once won a spelling bee. 2. Writer Person. You’re not looking for Dostoevsky here, but someone who can write short, punchy marketing copy based on findings curated by your Research Ninja. You also want someone who’s well-liked by your team and great at collaborating with them on different types of projects. 3. Developer. Yup. You’ll need a web developer, too. Mobilize your Cast of Characters Here’s a simple email template you can use to rally your team and spell out the tasks that’ll get your SEO gears a grindin’. From: Mr. CEO guy To: Research Ninja, Writer Person, Developer Subject: Let’s SEO our site in 30 days Hey team, We’ve never had many resources to devote to SEO, but I see big reward for us if we can start to plant the seeds for greater organic search traffic in the future. I’d like to enlist your help with this project, whose objective is to get us to a basic level of SEO proficiency so we have a chance to rank on some desirable search terms. (Research Ninja), I’d like you to: 1. Use the AdWords Keyword Tool to research the types of phrases our prospective customers are using to find sites like ours. The default results will reflect broad match estimates, so be sure to look at exact match, too. 2. Download the search volume and competition data to Excel. This will transform the competition “meter” into a quantitative measure of each keyword phrase’s competitiveness. 3. Strategically whittle down the options to a maximum of 2 or 3 keyword phrases we should try to rank for. Your key criteria are relatively low competition and significant global search volume. 4. Validate your research against search volume and competition estimates shown by other SEO tools like Raventools, SEOmoz, KeywordSpy, etc. You might need to start a free trial or two. See if your recommendation holds water using data from several tools. 5. Whatever you determine our top priority keyword phrase should be, please communicate to the team that this is our preferred anchor text for inbound links. Hand off your final recommendations to Writer Person. (Writer Person), I’d like you to… 1. Take a stab at identifying the 5 or 10 most important pages on our website. 2. Based around Research Ninja’s conclusions, write a page title and meta description for each of the pages you identified. Use the following format for page titles: Primary keyword phrase | Secondary keyword phrase (optional) | Company name Meta description format: One or two very short sentences describing what the page is about, in the context of what our company does. Be sure to use the highest priority keyword phrase Research Ninja identified. Next, write a short paragraph or two describing each page. Don’t stuff keywords into the copy — work them in naturally. Write for humans. Each paragraph should have a header or two, as appropriate, related to the keyword phrase(s) from Research Ninja’s research. You’ll hand these over to Developer, who will wrap them in

and

tags. 3. Coordinate with our other properties, if we have any, to get links pointing to our site. 4. Develop a plan to incentivize customers/partners/vendors/affiliates to link to our site. 5. Work with sales / business development to ensure we start requiring a backlink in every contract we sign, if it’s realistic to ask for one. 6. Identify 5 bloggers and/or companies related to our space and reach out to them to explore guest blogging opportunities. Beyond your obvious outreach tools — LinkedIn, Jigsaw, your colleagues’ contacts. – you can also scope out myblogguest.com for guest blogging opportunities. Once you have some leads lined up, let’s talk about who on our team can help write good content. 7. Are we listed in basic business directories? Please create a standard business profile and submit our site to DMOZ, CrunchBase, LinkedIn, HotFrog, Google Places and Bing. 8. Do we have a blog? Let’s talk about how we can get one going. In all your link building efforts, remember to request the preferred link anchor text recommended by Research Ninja wherever possible. Of course, if you’re building links to pages other than our homepage, it might make sense to tweak this anchor text. As a rule of thumb, you can use the keyword phrase in the title of the page you’re linking to as the anchor text. Developer, can you please work with Writer Person to change our site HTML as follows: Change the 2011-10-25T17:05:56+00:00 http://www.smashingapps.com/2011/10/25/resume-designs-like-infographics-that-can-stand-out-in-a-crowd.html pesh2000 Best_of_the_Web color_Schemes Infographics Inspiration https://pinboard.in/u:pesh2000/b:0ef1f996d110/ 2011-10-25T09:23:10+00:00 http://www.webdesignerdepot.com/2011/10/dos-and-donts-of-call-to-action-pages/ pesh2000 Smashing_Network https://pinboard.in/u:pesh2000/b:c2a7b84f2c58/ 2011-10-25T09:20:02+00:00 http://boagworld.com/mobile-web/mobile-maze/ pesh2000 https://pinboard.in/u:pesh2000/b:45e407d09172/ 2011-10-25T01:57:20+00:00 http://feedproxy.google.com/~r/nettuts/~3/Zn7LKIi_Xa8/ pesh2000

Commands

Employees

If you aren’t familiar with using Twitter Bootstrap, you’ll see it’s no sweat to use. We’ve got a container that is 940px wide. Then, we have two rows. The first has one column, that covers all 16 columns. The other has two columns: one is 4 columns wide, and one is 12 columns wide. One more thing, before we get to some real coding: we’re going to pop up a modal window that allows up to input employees. Under the

, add this modal window HTML. Yes, it seems like a lot code, but it’s mainly Bootstrap stuff:

x

Add an Employee

First Name:

Last Name:

First Name:

Add

All right, we’re ready to go! Let’s code. Step 2: Wiring the Modal Window Open up a script tag at the bottom of index.html (I’m just doing this inline, but feel to put it in a new JS file). start this way: (function () { var employeeModal = $('#add-employee-modal').modal({ backdrop: 'static' }); }()); We’re using the Bootstrap modal plugin here; this just “instantiates” the modal window. Now, we want the window to appear when we click the “Add Employee” button. Of course, we’ll have to add the button first: put this in the

, right under the

.

Add Employee

That data-controls-modal='add-employee-modal' attribute will display the modal with said ID when the button is clicked. So, the user will need to fill in the form, click the “Add” button which has an id of create-employee. So, let’s wire up a click event handler for the button: $('#create-employee').click(function () { var form = $('#employee-form'); employeeModal.modal('hide'); EMPLOYEE.create( form.find('[name=firstName]').val(), form.find('[name=lastName]').val(), form.find('[name=role]').val() ); form.find('input').val(''); }); We get the form, and then hide the modal window. Then, we’re going to call an EMPLOYEE.create method, passing the first name, last name, and role as the three parameters. Finally, we clear the form. amplify.publish But wait, you say, what’s EMPLOYEE.create? Well, it’s a micro-“class” that I’ve put in js/employee.js. Check it out: var EMPLOYEE = { create : function (firstName, lastName, role) { var employee = { firstName: firstName, lastName: lastName, role: role, dateEmployed: new Date() }; amplify.publish('employee-created', employee ); return employee; } }; You’ll want to throw a script tag for it up with the others. Pretty simple, right? We just create an object literal with our parameters, and add a dateEmployed property. But, then—and finally!—we have the first entrance of the AmplifyJS framework. Here, we’re using the pub/sub events component. This is great for doing loose coupling between parts of your app. This method doesn’t have to know if another part of our code wants to do something with each new employee we create; Our “Add” button event handler doesn’t have to worry about it. We’ll just publish it as an “employee-created” event for any part that is interested to take. We pass our new employee object as data for anyone interested. Then, we return the employee object (even though we don’t keep track of it in our event handler). Step 3: Reacting with amplify.subscribe So, is any other part of our app interested in the “employee-created”? Yes, in fact. We want to do two things. First, add this employee to a table on our page. Second, we want to store the employee in localStorage. Here’s the first part of that: amplify.subscribe('employee-created', function (employee) { employeeTable.add([employee.firstName, employee.lastName, employee.role, employee.dateEmployed]); newAlert('success', 'New Employee Added'); }); To subscribe to an event, we call amplify.subscribe. We want subscribe to the “employee-created”; when that events occurs, we want to add it to the employeeTable; notice that instead of just passing it the employee object, we “convert” it to an array; this is because we need to be sure the elements will be in the right order. Then, we want to display an message, letting our user know that the employee was added successfully. What’s up with this employeeTable variable? Well, first, we have to add the to our document. So, underneath our “Employees”

, add this:

First Name	Last Name	Role	Date Employed

Now, we have to capture this table as a variable up in our var statement at the top: employeeTable = TABLE.create($('#employee-table')), And TABLE? That’s the last piece of JS for this puzzle. Put this in js/table.js and don’t forget the script tag: var TABLE = { proto : { init : function (el) { this.element = $(el).find('tbody'); }, add: function (arr) { var row = $('').html(function () { return $.map(arr, function (value) { return '' + value + ''; }).join(''); }); this.element.append(row); }, load: function (rows, order) { for (var i = 0; rows[i]; i++ ) { this.add(rows[i]); } var fields = []; for (var j = 0; order[j]; j++) { fields.push(rows[i][order[j]]); } this.add(fields); }, clear: function () { this.element.empty(); } }, create : function (el) { var table = Object.create(this.proto); table.init(el); return table; } }; It’s a bit complicated, but you should have no problem grokking it. We’ve got a proto property that is the prototype for our table instances. Then, when we call create, we use Object.create to create an object that inherits from this.proto. After that, we call the init method to set any properties. Finally, we return the table instance. This micro-API makes it easy for us to work with our table. You should be able to see how passing an array to the add method will add a row to our table. Notice also that we can pass an array of rows to load and fill the table up; we’ll use this soon. Oh, then there’s the newAlert method we called: function newAlert (type, message) { $('#alert-area').append($('

' + message + '

')); setTimeout(function () { $('.alert-message').fadeOut('slow', function () { this.parentNode.removeChild(this); }); }, 2000); } As you can see, this just simply adds a div inside out

; the new div takes advantage of the Twitter Bootstrap alert styling; after two seconds, we fade the alert out and remove it. amplify.store But that’s not the only think we want to do when the “employee-created” event occurs: employeeStore = amplify.store('employees') || []; At the top, with our two other variables, make the third and final one: employeeStore. If amplify.store('employees') returns something, we’ll use that; otherwise, we’ll use an empty array. amplify.subscribe('employee-created', function (employee) { employeeStore.push(employee); amplify.store('employees', employeeStore); }); Now we’re using the storage component of AmplifyJS. It really couldn’t be simpler: to store a value, pass amplify.store a key and the value. To retrieve the value, hand it the key. Underneath, AmplifyJS is storing that key and value in whatever storage type is available on that browser. So here, we add a new employee to the array and store the array in the “employees” key. I should note that since we’re storing an array, AmplifyJS is using JSON serialization to convert that array to a string. Therefore, if you’re trying to support browsers without native JSON support (IE 5 and down, Firefox 3 and down), you’ll want to include the json2.js library. Step 4: Saving to the Server (with amplify.request) In our little app-example, we’re saying that by default, the data you put into the app is kept only on your computer (in that one browser). However, if the user wants, we’ll allow them to put it up on the server (hypothetically, this is private information they might not want to share; however, if they want to access it from other devices, they could do this.). We’ll start by adding a button for uploading the data.

Push Data to Server

Now, of course, your brilliant minds have already figured out that we’ll be using AmplifyJS’s AJAX component. amplify.request is an incredibly flexible API, and we won’t be looking at everything it can do. However, you’ll get a good feel for how it works here. Doing AJAX with AmplifyJS is a bit different than with other libraries: the idea is that first you define a connection to the server; then, you can use that connection any number of times after that. Let’s begin by defining a connection, called a “resource” by AmplifyJS: amplify.request.define('pushData', 'ajax', { url: 'data.php', type: 'POST' }); The first parameter here is resourceId, which we’re setting as “pushData”; this is how we’ll refer to our connection when we’re using it. The second parameter is the request type; in this case, “ajax.” This is the only request type built into AmplifyJS; you can add your own, but this is suitable for our needs today. Finally, we have an options object. According to the documentation, your settings options are anything you would set in jQuery.ajax, as well as cache (which allows you to set up a custom memory cache) and decoder (for parsing the AJAX response). In our case, only two options are necessary: the url, and the type of request we’re making. Of course, we’ll need some simple PHP on the back end; make sure the data folder is writable. data.php Now, how about using the connection, the resource, we’ve defined? Well, let’s do this in a click handler for that : $('#push-data').click(function () { amplify.request('pushData', { employees: amplify.store('employees') }, function (data) { amplify.publish('data-pushed', data); }); }); When using the resource, the first parameter is the resource ID; it’s the same resource ID we have the resource we defined, so AmplifyJS knows which to use. Second, we pass data hash. In this case, we pass the content in our store, under the key “employees.” The final parameter is a function that’s called when we get a response. Once we get a response, we’ll publish the “data-pushed” event. Then, we’ll just alert the user that it worked: amplify.subscribe('data-pushed', function () { newAlert('success', 'Data successfully sent to server'); }); Taking it a Step Further Well, that’s our little example app. We’ve looked at using all three of AmplifyJS components: amplify.publish / amplify.subscribe, amplify.store, and amplify.request. We’ve covered pretty much all there is to know about the pubsub and store parts (there is a bit more!), but there’s a lot more you can do with the request API. So, go check out the website to learn more! So, what are your thoughts on AmplifyJS? Like it? Find it too redundant? Let’s hear it in the comments! ]]> JavaScript_&_AJAX https://pinboard.in/u:pesh2000/b:d3a13ef639d1/ 2011-10-24T07:01:52+00:00 http://www.webappers.com/2011/10/24/make-your-lists-seachable-sortable-filterable-with-list-js/ pesh2000 MIT_License Tables https://pinboard.in/u:pesh2000/b:d8aa467ecfb1/ 2011-10-23T20:52:18+00:00 http://minimalmac.com/post/11833723471 pesh2000 https://pinboard.in/u:pesh2000/b:06f39da1f768/ 2011-10-21T20:02:22+00:00 http://www.imediaconnection.com/article_full.aspx?id=30267 pesh2000 https://pinboard.in/u:pesh2000/b:7fbda1f1dd1b/ 2011-10-20T19:14:52+00:00 http://feedproxy.google.com/~r/shawnblanc/~3/sXJ2Eb2nLL0/ pesh2000 https://pinboard.in/u:pesh2000/b:3bee8ccaee1c/ 2011-10-20T17:42:59+00:00 http://blog.kissmetrics.com/selling-more/ pesh2000 Conversion https://pinboard.in/u:pesh2000/b:0c171f34c25b/ 2011-10-20T16:05:12+00:00 http://www.somegeekintn.com/blog/2011/10/lies-damned-lies-and-statistics/ pesh2000 https://pinboard.in/u:pesh2000/b:2027e178a82a/ 2011-10-20T14:13:39+00:00 http://www.smashingmagazine.com/2011/10/20/comprehensive-review-of-usability-and-user-experience-testing-tools/ pesh2000 UX_Design testing tools usability https://pinboard.in/u:pesh2000/b:f3b7c61df5d5/ 2011-10-19T21:31:47+00:00 http://d.pr/CK5D pesh2000 Links amazon_item https://pinboard.in/u:pesh2000/b:30837fb1d12d/ 2011-10-19T20:05:48+00:00 http://www.smashingmagazine.com/2011/10/19/optimizing-long-lists-of-yesno-values-with-javascript-2/ pesh2000= 37), which effectively uses all letters in the alphabet, all the way up to z! This way, we can have a compression of up to 6 characters for 32 values, which means saving up to 81.25% compared to the plain string method! And the code is just as simple: parseInt( '1001011000', 2).toString(36); // returns 'go' (instead of '258', which would be the hex version) parseInt('go', 36).toString(2); // returns '1001011000' For some of you, this will be enough. But I can almost hear the more inquisitive minds out there shouting, “But we have capital letters, we have other symbols, we are still not using strings to their full potential!” And you’d be right. There is a reason why every time you open a binary file in a text editor, you get weird symbols mixed with numbers, uppercase letters, lowercase letters and whatnot. Every character in an UTF-16 string is a 2 bytes (16 bits), which means that if we use the right compression algorithm, we should be able to store 16 yes/no values in it (saving 93.75% from the string method). The problem is that JavaScript doesn’t offer a built-in way to do that, so the code becomes a bit more complicated. Packing 8 Values Into One Character You can use String.fromCharCode to get the individual characters. It accepts a numerical value of up to 65,535 and returns a character (and for values greater than that, it returns an empty string). So, we have to split our string into chunks of 16 characters in size. We can do that through .match(/.{1,16}/g). To sum up, the full solution would look like this: function pack(/* string */ values) { var chunks = values.match(/.{1,16}/g), packed = ''; for (var i=0; i < chunks.length; i++) { packed += String.fromCharCode(parseInt(chunks[i], 2)); } return packed; } function unpack(/* string */ packed) { var values = ''; for (var i=0; i < packed.length; i++) { values += packed.charCodeAt(i).toString(2); } return values; } It wasn’t that hard, was it? With these few lines of code, you can pack the aforementioned 512 values into — drum roll, please — 32 characters (64 bytes)! Quite an improvement over our original 2 KB (with the array method), isn’t it? Limitations Numbers in JavaScript have limits. For the methods discussed here that involve an intermediate state of converting to a number, the limit appears to be 1023 yes/no values, because parseInt('1111…1111', 2) returns Infinity when the number of aces is bigger than 1023. This limit does not apply to the last method, because we’re only converting blocks of bits instead of the whole thing. And, of course, it doesn’t apply to the first two methods (array and string) because they don’t involve packing the values into an integer. “I Think You Took It A Bit Too Far” This might be overkill for some cases. But it will definitely come in handy when you want to store a lot of boolean values in any limited space that can only store strings. And no optimization is overkill for things that go through the wire frequently. For example, cookies are sent on every single request, so they should be as tiny as possible. Another use case would be online multiplayer games, for which response times should be lightning-fast, otherwise the games wouldn’t be fun. And even if this kind of optimization isn’t your thing, I hope you’ve found the thought process and the code involved educational. (al) Thanks to Eli Grey and Jonas Wagner for their advice and corrections Image on front page created by Ruiwen Chua. © Lea Verou for Smashing Magazine, 2011. ]]> Coding https://pinboard.in/u:pesh2000/b:64e80c1a2953/ 2011-10-19T15:46:52+00:00 http://codevisually.com/wordpress-widget-boilerplate-an-organized-maintainable-boilerplate-for-building-wp-widgets/ pesh2000 Wordpress IDE README TODO WP https://pinboard.in/u:pesh2000/b:3742e70b89c1/ 2011-10-19T13:15:09+00:00 http://thinkprogress.org/yglesias/2011/10/19/347495/another-9-9-9-distributional-analysis-chart/ pesh2000 General Yglesias Herman_Cain https://pinboard.in/u:pesh2000/b:566f9a72c752/ 2011-10-19T10:32:00+00:00 http://www.smashingmagazine.com/2011/10/19/free-e-commerce-wordpress-theme-balita/ pesh2000 Freebies E-Commerce themes https://pinboard.in/u:pesh2000/b:8b6d37cbe392/ 2011-10-17T03:17:58+00:00 http://designm.ag/designer-showcase/28-fresh-e-mail-newsletter-designs-for-graphic-inspiration/ pesh2000 https://pinboard.in/u:pesh2000/b:71b87a6c125c/ 2011-10-13T09:51:30+00:00 http://www.webdesignerdepot.com/2011/10/no-mobile-site-no-more-excuses/ pesh2000 Smashing_Network https://pinboard.in/u:pesh2000/b:4761cc96a194/ 2011-10-12T11:30:21+00:00 http://www.onextrapixel.com/2011/10/12/build-your-own-qr-code-generator-with-google-chart-api/ pesh2000

QR code generator

Size:

150x150
200x200
250x250
300x300

Encoding:

UTF-8
Shift_JIS
ISO-8859-1

Content:

Error correction:

L M Q H

First part of the code above is an HTML form with available options which will be passed to create the QR code image. Take note the form's target attribute's value is qrcode-frame. This tells the form to submit through an iframe.

Size:

150x150
200x200
250x250
300x300

Encoding:

UTF-8
Shift_JIS
ISO-8859-1

Content:

Error correction:

L M Q H

Second part of the code above is an iframe which will be used to submit the form. The reason we are using iframe here is to let users constantly generate QR code without refreshing the page.

Now view index.php from your browser. It should look like something below. It does not look very good with the current plain CSS style; let us add some CSS style to the page. We will not discuss details of CSS styles here, since this tutorial is more focus on the PHP part.

QR code generator

Size:

150x150
200x200
250x250
300x300

Encoding:

UTF-8
Shift_JIS
ISO-8859-1

Content:

Error correction:

L M Q H

Now view index.php again from your browser, now it should look better as below: File: gen.php Copy and paste following code into gen.php. '; } ?> Do request only if there is a data posted to the page. Capture data using $_REQUEST and store them in different variables. Construct a Goolge Charts API URL, and append captured data above to the URL. Print out a img tag with src equals to the Google Charts API created previously. Generate Your Own QR Code Now! That is all, now your own QR code generator should be fully working. Navigate index.php from your browser and enter some data in content filed, select your desired options and click "generate" button. You should be able to see a QR code being created instantly. 50 Handy CSS Tools And Generators for Developers10 Web Apps For A More Seamless Workflow Online10 Tools To Make The Most Of Twitter25 Handy Freelance Web Designer Tools Written by: Xu Ding for Onextrapixel - Showcasing Web Treats Without A Hitch | 10 comments Post Topic(s): Development ]]> Development javascript tools https://pinboard.in/u:pesh2000/b:eb0383c2ec2b/ 2011-10-11T10:00:00+00:00 http://www.netmagazine.com/features/ethan-marcottes-20-favourite-responsive-sites pesh2000 Smashing_Network https://pinboard.in/u:pesh2000/b:8426ecfe353f/