Sign up for the newsletter today.
At yesterday’s Create the Web event, Adobe announced a number of new products that are already available for you to use. I have covered a full summary of the keynote on my personal blog if you’re interested. Of course, if you are excited about the announcements, you may want to know a little bit more about the products and how to use them. The good news is that we’ve posted a some new (and one updated) tutorials on the ADC covering several of the key products announced.
Edge Inspect, formerly called Shadow, helps solve the difficulty of testing and debugging mobile web sites across the ever growing list of devices and screens. It has features like remote debugging using Weinre and collecting screenshots on all devices at once. Edge Inspect is now available via subscription, including a free version. You can learn more about how to use Edge Inspect in my article on the Adobe Developer Connection, “Browser testing across devices with Adobe Edge Inspect.”
The official release of PhoneGap Build was announced yesterday. PhoneGap Build is a service that creates the multiple distributions for a wide array of device operating systems in the cloud. If you want to learn more about PhoneGap Build and the new features, including Hydration, which automatically updates you app when a new build is posted, check out Ray Camden’s article on the Adobe Developer Connection, “PhoneGap Build Levels Up.”
While Greg’s presentation was great, I really felt that it was important enough to deserve a wider audience than just those able to attend PhoneGap Day. Thankfully, Greg agreed to turn his presentation into an article for the Adobe Developer Connection. Yesterday, we published Greg’s article “Creating apps with PhoneGap: Lessons learned” and if you are already doing PhoneGap development or are interested in it, I’d call it a “must read.” As always, feel free to share your feedback.
If you are a web designer or front-end developer using HTML and CSS, it’s likely you have heard of Louis Lazaris. Even if you don’t recognize the name, you have probably at some point referenced one of the many posts on his blog, Impressive Webs, or other well-known publications. So, I am very happy that the ADC has published a contribution by Louis covering the topic of CSS3 transitions titled “Using CSS3 transitions: A comprehensive guide.” As the title indicates, this is a great tutorial and reference for creating and triggering animations using various CSS transitions. Louis covers the syntax for building transitions via your stylesheets, then discusses various ways for triggering transitions, offers some useful tips and techniques and discusses the current state of browser support. If you are new to using transitions, this is a great “how to” and if you have already used transitions, I think it still makes a perfect reference.
So, please, check out Louis’ article and, as always, feel free to share your feedback.
CORS stands for cross-origin resource sharing and it is an HTML5 feature that allows you to connect to 3rd party API’s without hitting browser security warnings. In the past, you’d usually have to write server-side API wrappers or use JSONP, which only works for reading and isn’t supported by many API’s. Now, with CORS, you can forgo the wrapper and even do things like post, put and delete. I have been walking through HTML5 features, going from left to right on HTML5 Readiness, on my blog and as part of this journey I investigated CORS. In my latest article for the ADC, I take a look at the feature in some detail and discuss browser support in current browser versions. I show some examples of how you can connect to the GitHub API, which is one of a growing number of API’s that support CORS. So please read “Understanding Cross-Origin Resource Sharing (CORS)” and please feel free to share your thoughts on the article.
For anyone who hasn’t yet heard of Adobe Brackets, it is an open-source code editor created by Adobe and hosted on GitHub. While you can download early experimental builds on Brackets, it is early and not everyone may find it yet has all the features they want for every day use. Nonetheless, the team, with the help of an array of contributors from the community, is progressing quickly with new builds and new features.
Semantic HTML is one of those things that, despite it’s value, doesn’t demo well. There’s no flashy animated effects or interaction. For example, I could demo how I replaced a <div> with a <nav> but the resulting page would look and behave exactly the same. The same if I replace something like <div id=”rt4894_sm”> with <div id=”rightpanel”>. In addition, the full value of semantic HTML is often hard to explain. Because of this, you may even still be unfamiliar with what semantic markup is and how to use it. The truth is though, there are a wide variety of ways your web site/application can benefit from semantic markup – this is why a number of new semantic tags were added to HTML5.
Terry Ryan has been an advocate of semantic HTML, even creating a site, along with Raymond Camden, called WhichElement that tries to help you decide when and where to use certain semantic tags. In his latest ADC article, Terry lays out a strong case for why you should care about semantic HTML and the variety of potential benefits of caring about semantics when developing. Terry gives an honest look at the topic, even acknowledging some skepticism about semantic markup. However, to me, that is what makes his argument most compelling – it takes a realistic and pragmatic look at the topic. So, give Terry’s article, “Using Semantic HTML” a read and please feel free to share your thoughts on the topic.