Web Professional Trends for 2013 – “Web Project Management” Interview with Tonya Price
In this sixteen minute interview with Tonya Price, Web consultant and Web project Management instructor we learn from her perspective on the topic of Web Professional Trends for 2013 as it relates to Web Project Management.
• How companies are postponing hiring of the Web project “leaders” due to the pressures of a tight economy
• How the net result of this is the shift of the project management job function to Web Designers and Web Developers
• About the “Web Project Management Essentials” Course offering on the Weprofessionals.org website
• How Web project management is becoming of particular interest to the Web Designer and Web Developer
• How Web Designers and Developers have an increased interest in accessing Web project management training gain access to the training
• How Web projects are changing too fast for the “typical project manager”
• How Web project management is different than that of typical project management
• How traditional project managers want to manage Web teams but they don’t understand the terminology or technology
• How traditional project managers need Web design and Web development training
• About the “Web Project Management Essentials” Course offering on the Weprofessionals.org website
More about Tonya Price
Tonya Price advises holds an MBA in Marketing and Finance from Cornell University’s Johnson School of Management and teaches the Website Project Management Essentials course WebProfessionals.org. She has over 20 years’ experience managing high tech and Internet company Technical Support and Web Development teams ranging in size from five to over one hundred and fifty staff members. She runs a Web Project Management blog at www.tonyaprice.com/blog and posts the Web Project Management Tip of the Day on twitter www.twitter.com/tdprice.
She started her career as a programmer and founded the web firm, StrategicIdeas in 1996, which was acquired by the Internet Service Provider, UltraNet Communications (later acquired by RCN.) She has consulted with a variety of companies across numerous industries and served as Director of Web Services and Web Operations for start-ups to Fortune 500 companies. As Director of Marketing and Web Operations at Worcester Polytechnic Institute, she oversaw the successful Project Management of a 40,000 page redesign of the university Web site and Red Dot CMS integration
In this six minute interview Larry Ullman is a writer, Web and software developer, trainer, instructor, speaker, and consultant we learn from his perspective on the topic of Web Professional Trends for 2013 as it relates to Mobile UX Micro-Frameworks.
Web Professional Trends for 2013 – “Mobile UX Micro-Frameworks” Interview with Larry UllmanPlay Now | Play in Popup | Download
Specifically we learn:
•The need to repeat the demand for mobile ( Mobile first Desktop Second)
•UX for Mobile
•Authentication security concerns for mobile
•Advice for teachers
•Advice for job seekers
•Micro-Frameworks
•About Larry’s favorite books
• More about Larry Ullman
Ten Tips for Designing Mobile UX
According to RedAnt.com, as the mobile channel matures and technologies develop, so too does the field of Mobile User Experience. Good UX is what separates successful apps from unsuccessful ones, and lets small upstarts take on big brands by creating more compelling apps. The article shares ten quick tips that will help you on the way to great mobile design. Even if you’re not involved in the actual design process, knowing these concepts will still help you come up with better concepts and give better feedback to those who do the work. (Note: I refer to apps below, but you can generally interchange with mobile websites freely).
1) Go back to the drawing board ( bottom up)
2) Identify your users (hunters or gatherers)
3) Remember the 80/20 rule ( what functionality is most used)
4) Use task-based design
5) Keep it simple (fast info vs. and instruction manual)
6) Don’t ignore platform UX
7) Capture more than just touch input
8) Design for interruption
9) Remember your design isn’t perfect
10) Above all, follow best practice and your own experience
According to a Micro-Frameworks article written by Addy Somaini, ( http://addyosmani.com/blog/prosconsmicroframeworks/) the concept of the JavaScript micro-framework has always existed, tackling tasks ranging from client-side templating through compact solutions for MVC-architecture and beyond. With an increased recent interest in combining such focused solutions into a custom modularized framework for your production needs (as opposed to say, using a larger library that tackles broader concerns), I thought it would be interesting to take a look at micro-frameworks to find out what the true pros and cons of using them might be.
Why consider micro-frameworks?
Addy Somaini makes the case by saying that, “It’s no secret that with each subsequent release, well-established libraries, frameworks and toolkits increase in size and this has some developers questioning whether the entire stack of functionality provided is required for the average site or project. We live in an age where performance and page-load time are constantly under scrutiny and thus, a developer couldn’t be blamed for attempting to cut down unused code from their site’s overall load.”
The reality is that you may only wish to use a subset of features offered in a library like jQuery (eg. selection, animation) but may not require support for ajax, DOM-associated data storage, deferreds and others. The library may also not provide everything your project needs (it’s naive to think it ever would), however we can appreciate a developer asking whether that 30KB+ download of the library could be replaced with something significantly more modular that does cover more of their own needs.
This is an area where using micro-frameworks can potentially offer the greatest benefit to a project (especially where mobile is specifically targeted). For the full article visit http://addyosmani.com/blog/prosconsmicroframeworks/
Thomas Fuchs has been attempting to make developers more aware of micro-frameworks through efforts such as microjs.com (which you should check out) and there certainly appears to be enough interest in modularized frameworks for a broader discussion on micro-frameworks to keep going.
More about Larry Ullman
Larry Ullman is a writer, Web and software developer, trainer, instructor, speaker, and consultant. He has written 23 books and numerous articles. His books have sold over 350,000 copies world wide in more than 20 languages. As his readers, students, and co-workers can attest, Larry’s strength is in Translating Geek into English: converting the technical and arcane into something comprehensible and useful. For additional information visit http://larryullman.com
WebProfessionals.org is proud to announce their “2013 Web Design and Web Development Trends” podcast series
The “2013 Web Design and Web Development Trends” podcast series will be moderated by Bill Cullifer, Executive Director WebProfessionals.org and will explore trends and cutting-edge enabling technologies potentially affecting Web professionals’ upcoming projects and next-generation technology.
The series will include topics ranging from Web Accessibility, Responsive Design, Typograpghy, HTML5, JavaScript, CSS, Linked Data, Programming, JQuery, Search, Web Standards, Web Marketing and Branding, Project Management, Web Security, Legal issues, Web Server Admin including hardware, security, network) Mobile Application Development and Social Media to name a few.
Invited Guest:
* “Enterprise SEO and Social” Interview with Jeff MacGurn, Covario
* “Social Media for Small Business” Interview with Brent Norris, Green Collar Tech
* “Responsive Design and Web Typography” Interview with Jason Cranford Teague, Rosenfeld Media
* “Responsive Design and Download” Interview with Chris Converse, Codify Design Studio
* “HTML5 and CSS3″ Interview with Charles Wyke-Smith, Bublish
* “Web Development” Interview with Chris Wilson, Google
* “Responsive Design” Interview with Tim Kadlec, Breaking Development
* “Content Marketing” Interview with Rebecca Lieb, Altimeter Group
* “Search” Interview” with Bruce Clay, Bruce Clay Inc.
* “Web Standards and CSS” Interview with Eric Meyer, Web Consultant
* “SAAS and Compass” Interview with Dirk Ginader, Senior UX Prototyper at Yahoo!
Web Professional Trends for 2013 – “Enterprise SEO and Social” Interview with Jeff MacGurn
In this six minute interview Jeff MacGurn, Vice President of Global Earned Media Services Covario we learn from his perspective on the topic of Web Professional Trends for 2013 as it relates to Enterprise SEO and Social.
Web Professional Trends for 2013 – “Enterprise SEO and Social” Interview with Jeff MacGurnPlay Now | Play in Popup | Download
Specifically we learn:
•What Content Marketing means to the Enterprise
•The rise of Content Marketing
•The meeting and melding of SEO and Social
•Content received a promotion
•Best practices for enterprise level SEO and Social
•Top of funnel needs of consumers
•Leverage Yelp, YouTube and LinkedIn
•Case studies from Marriott, American Express and Virgin Mobile
•Flat image files rule for 2013
5 Big Brands Confirm That Content Marketing Is the Key To the Consumer
According to Forbes online, brands have begun to embrace Content Marketing and as a discipline as a vital part of their overall strategy. What was once a conversation on “why content marketing” has turned into a conversation on “how to.” Check out how five leading brands are developing content their consumers want by following the link below.
In this twelve minute interview Brent Norris, Web Consultant at Green Collar Technology we learn about his perspective on the topic of Web Professional Trends for 2013 as it relates Social Media and Small Business.
Web Professional Trends for 2013 – “Social Media for Small Business” Interview with Brent NorrisPlay Now | Play in Popup | Download
Specifically we learn:
•What Social Media means for Small Business
•Social Media goals for Small Business
•Social Media challenges Small Business
•Social Media ROI for Small Business
•Social Media challenges within the Web profession
•Brent’s perspective on meeting Social Media client needs for Small Business
•Social Media Opportunities for Small Business Web professionals
•A Social Media Comparison of Facebook, LinkedIn and Google plus
•Social Media Tips and Advice for Web professionals targeting Small Business
More about Brent Norris
Brent Norris grew up in Ormond Beach, Florida, mostly surfing with little awareness of the outside world. A designer at birth, Brent attended design school in the eighties before embarking on a digital design career in Boston, Massachusetts.
Working for small design boutiques and large corporations in the Greater Boston area during the dot-com boom, Brent gained experience consulting and training Fortune 500 companies like, Macromedia, Adobe, Apple and Nike. Brent expanded his personal reach giving emerging technology presentations at National and International conferences for organizations like the World Organization of Webmasters and the World Wide Web Consortium.
Brent lives off-the-grid in a remote area of Hawaii Island in a self-built treehouse where he re-imagines sustainable living practices in a native Ohia lehua forest. Brent lives lightly on the land, embraces local culture and constantly learns to apply ancient and modern technologies in everyday life. Thirty years of surfing and five years of living and working from his treehouse studio has married Brent to his environment.
Presently engaged in helping to strengthen Hawaii’s digital economies Brent seeks to transform Hawaii Island into a mecca for like-minded digital designers and developers interested in living off the grid and cultivating a new culture based on past traditions and singularity principles. Brent mentors students, serves on the Hawaii Island Junior Achievement Board of Directors. Brent earned the Webmaster of the Year award in 2009 and as Co-Founder and ED of Green Collar Technologies earned the Small Business Administration’s “Home Based Business Champion of the Year
In this twelve minute interview Jason Cranford Teague, Trainer & Consultant at Rosenfeld Media we learn about his perspective on the topic of Web Professional Trends for 2013 as it relates to Responsive Design and Web Typography.
Web Professional Trends for 2013 – “Responsive Design and Web Typography” Interview with Jason Cranford TeaguePlay Now | Play in Popup | Download
Specifically we learn:
• The rational for Responsive Design
• About Responsive Web Typography and making it work across multiple devices
• About the multitude of Web Typography offerings today
• How to choose Web Typography
• How to choose Type Faces
• That we need to be ready for change
• Iconography
• How Icons will be replaced by Fonts
• How fonts can stand out in interactive design
• How customers don’t always understand or appreciate the complexity of Web design process
• His thoughts on creating Web design credibility
• How Web Design really matters
• Jason’s thoughts and tips on education for the client
• A discussion with Jason and Bill Cullifer about
• Some of the downsides of CMS or off the shelf web solutions
• A discussion with Jason and Bill Cullifer about Web professional titles and skill offerings
• About Jason’s resources and links
More about Web Typography
According to Wikipedia, Web typography refers to the use of fonts on the World Wide Web. When HTML was first created, font faces and styles were controlled exclusively by the settings of each Web browser. There was no mechanism for individual Web pages to control font display until Netscape introduced the font tag in 1995, which was then standardized in the HTML 2 specification. However, the font specified by the tag had to be installed on the user’s computer or a fallback font, such as a browser’s default sans-serif or monospace font, would be used. The first Cascading Style Sheets specification was published in 1996 and provided the same capabilities.
The CSS2 specification was released in 1998 and attempted to improve the font selection process by adding font matching, synthesis and download. These techniques did not gain much use, and were removed in the CSS2.1 specification. However, Internet Explorer added support for the font downloading feature in version 4.0, released in 1997.Font downloading was later included in the CSS3 fonts module, and has since been implemented in Safari 3.1, Opera 10 and Mozilla Firefox 3.5. This has subsequently increased interest in Web typography, as well as the usage of font downloading.
More about Iconography
Iconography is the branch of art history which studies the identification, description, and the interpretation of the content of images: the subjects depicted, the particular compositions and details used to do so, and other elements that are distinct from artistic style. The word iconography comes from the Greek ????? (“image”) and ??????? (“to write”). A secondary meaning (based on a non-standard translation of the Greek and Russian equivalent terms) is the production of religious images, called icons, in the Byzantine and Orthodox Christian tradition; that is covered at Icon. In art history, “an iconography” may also mean a particular depiction of a subject in terms of the content of the image, such as the number of figures used, their placing and gestures. The term is also used in many academic fields other than art history, for example semiotics and media studies, and in general usage, for the content of images, the typical depiction in images of a subject, and related senses. Sometimes distinctions have been made between Iconology and Iconography, although the definitions, and so the distinction made, varies. When referring to movies, genres are immediately recognizable through their iconography, motifs that become associated with a specific genre through repetition.
More about Jason Cranford Teague
Jason has been at the forefront of web culture for over 18 years as a designer, writer and teacher. He is the director of user experience at Forum One, an interactive agency with clients that include the Environmental Protection Agency, The Aspen Ideas Festival, and The Half the Sky Foundation.
As well as being a core contributor to Wired’s GeekDad blog, Jason has written over a dozen books and hundreds of articles, dealing with a wide range of digital media topics. His recent books include CSS3 Visual Quickstart, Fluid Web Typography, and Speaking in Styles: The Fundamentals of CSS for Web Designers. Over the last 10 years, Jason has spoken to audiences at some of the leading events in digital media, including SXSW, Voices That Matter, Macworld, WebVisions, WebDirections, NEXT, and HOW Live.
Web Professional Trends for 2013 – Chris Converse, Codify Design Studio
In this twelve minute interview Chris Converse, partner, designer and developer at Codify Design Studio we learn about his perspective on the topic of Web Professional Trends for 2013 as it relates to Responsive Design, Responsive Downloads and Responsive Imagery.
Web Professional Trends for 2013 – “Responsive Design and Download” Interview with Chris ConversePlay Now | Play in Popup | Download
Specifically we learn:
• About Chris and his Codifydesign.com Company
• More about Chris’s education and advocacy efforts to bridge the relationship between the Web Designer and Web developer
• About how he is building on the Responsive Design trends with Responsive Download discoveries
• About Responsive Imagery
• About Responsive Downloads with Media Quires, CSS3 and HTML5 Elements
• About faster downloads with less intensive bandwidth requirements
• Advice for those that teach
• Pros and the Cons of Responsive Imagery
• Efforts at the W3C that will enable browsers to communicate to the server and your device with specific download speed capabilities that could deliver high res images to your Mobile device
• Examples of Server Side Responsive Imagery to detect things with PHP and .NE, picking out those images and dynamically assembling them
• Trends to make images more compelling for tablets that are more animated and compelling that will utilize Containers and JavaScript that to achieve responsive download techniques
• How much we’ve progressed as an industry in the last decade
• An open discussion between Bill Cullifer, WebProfessionals.org Exec and Chris Converse regarding the current status of the industry
• About some of the debate in the Web Design community about best practices
• More about the great work at the w3c to support the Web professional community
• Some wireless industry history and honorable mention of wireless pioneer Craig McCaw from Bill Cullifer
• Links to more information about Chris and his resources
More about Responsive Download and Imagery
According to an article written by Chris for Lynda.com, when considering a responsive design for a website, many web designers and developers only consider the layout. While it is key to ensure the layout and composition make use of the user’s screen size, the download time should also be considered as part of the user experience.
To really understand the concept of designing for responsive download, we first need to take into account that CSS can be used to add imagery to HTML elements of webpages. From there it becomes more apparent that CSS3 media queries can be used to alter imagery, as well as layout, based on a user’s screen size.
With this in mind, the is one HTML5 element to focus on when planning a web layout. Typically the header area of a website is used for corporate branding, navigation, and imagery that sets the tone of the design. When creating a responsive web design, three or more sets of CSS rules will need to be specified based on the user’s screen size. These CSS rules will then in turn make adjustments to the sizing- and layout-based properties of the header elements based on available screen real estate. If we use CSS to specify imagery to be used in the header area, we can also drive more of the design tone with CSS.
Now, with CSS driving the imagery for the header element, combining CSS3 media queries with image assignments allows the imagery to adjust based on screen size. This allows designers to use larger, less compressed images for larger screens, while smaller screens reference smaller, more compressed images.
The ability to call on CSS referenced images that have varying dimensions and compression settings results in reduced download sizes and times for devices with smaller screens. This means the same HTML and CSS files will call on files for small- and large-screen devices, but the files called on for small-screen devices will be up to one-fifth the size of those called on for large-screen devices.
More about Chris Converse
Chris Converse has 20 years of experience in graphic design and interactive media, with a unique focus on both design and development. Chris possesses development skills across such languages as PHP, ActionScript, HTML5, CSS3, JavaScript and jQuery, making his design execution optimal across various media.
Chris is graduate of Rochester Institute of Technology with a degree in graphic design. He began his career in print, designing and preparing digital files for commercial offset printing. Chris has spent the last 15 years studying and applying design and interface principles to technology. His work spans various distribution media (CD-ROMs, web sites, and interactive DVDs) and applies many authoring media and techniques (HTML, CSS, JavaScript, AJAX, image optimization, motion graphics, Flash, Director, Shockwave, sound engineering, digital video compression, PHP, and ASP). Chris has a passion for and a commitment to conceiving, creating, and delivering the best possible user experience, regardless of the medium.
If you’re interested in learning more about responsive web design in the lynda.com library, consider checking out Creating a Responsive Web Design from Chris Converse at the links below:
Web Professional Trends for 2013 – “HTML5 and CSS3” Interview with Charles Wyke-Smith, CEO at Bublish
In this ten minute interview Charles Wyke-Smith, CEO at Bublish and author of Stylin’ with CSS” and various others from Charleston, South Carolina, we learn about Charles’s perspective on the topic of Web Professional Trends for 2013 as it relates to HTML5, CSS3 and monetization for Web professionals.
Web Professional Trends for 2013 – “HTML5 and CSS3” Interview with Charles Wyke-SmithPlay Now | Play in Popup | Download
Specifically we learn:
• Advances in HTML5 and CSS3
• How the web is becoming more application like
• How the Browsers are becoming more capable
• About how API’s in HTML5 like Geo location, local storage, audio and vide are improving and eliminating the need for downloadable applications
• How HTML5 will provide additional revenue opportunities for application designers and developers by providing direct access to the market
• Benefits of learning on “the front end” that will allow Web professionals to focus on the User Experience
•That it’s an exciting time to be a Web professional
•How the Web is maturing to become the “Web 3.0” according to Charles, is Web 2.0 plus revenue
•Availability of all of the APIs
•How to build a core value by focusing your business
•About the Web Hypertext Application Technology Working Group (WHATWG)
•More about Charles Wyke-Smith, his new books and all of his great resources
More about HTML5
HTML5 is a markup language for structuring and presenting content for the World Wide Web and a core technology of the Internet. It is the fifth revision of the HTML standard (created in 1990 and standardized as HTML4 as of 1997) and, as of December 2012, is still under development. Its core aims have been to improve the language with support for the latest multimedia while keeping it easily readable by humans and consistently understood by computers and devices (web browsers, parsers, etc.). HTML5 is intended to subsume not only HTML 4, but XHTML 1 and DOM Level 2 HTML as well.
Following its immediate predecessors HTML 4.01 and XHTML 1.1, HTML5 is a response to the observation that the HTML and XHTML in common use on the World Wide Web are a mixture of features introduced by various specifications, along with those introduced by software products such as web browsers, those established by common practice, and the many syntax errors in existing web documents. It is also an attempt to define a single markup language that can be written in either HTML or XHTML syntax. It includes detailed processing models to encourage more interoperable implementations; it extends, improves and rationalises the markup available for documents, and introduces markup and application programming interfaces (APIs) for complex web applications. For the same reasons, HTML5 is also a potential candidate for cross-platform mobile applications. Many features of HTML5 have been built with the consideration of being able to run on low-powered devices such as smartphones and tablets. In December 2011 research firm Strategy Analytics forecast sales of HTML5 compatible phones will top 1 billion in 2013.
In particular, HTML5 adds many new syntactic features. These include the new video, audio and canvas elements, as well as the integration of scalable vector graphics (SVG) content (that replaces the uses of generic object tags) and MathML for mathematical formulas. These features are designed to make it easy to include and handle multimedia and graphical content on the web without having to resort to proprietary plugins and APIs. Other new elements, such as section, article, header and nav, are designed to enrich the semantic content of documents. New attributes have been introduced for the same purpose, while some elements and attributes have been removed. Some elements, such as a, cite and menu have been changed, redefined or standardized. The APIs and document object model (DOM) are no longer afterthoughts, but are fundamental parts of the HTML5 specification. HTML5 also defines in some detail the required processing for invalid documents so that syntax errors will be treated uniformly by all conforming browsers and other user agents.
History
The Web Hypertext Application Technology Working Group (WHATWG) began work on the new standard in 2004. At that time, HTML 4.01 had not been updated since 2000, and the World Wide Web Consortium (W3C) was focusing future developments on XHTML 2.0. In 2009, the W3C allowed the XHTML 2.0 Working Group’s charter to expire and decided not to renew it. W3C and WHATWG are currently working together on the development of HTML5.
While HTML5 is often compared to Flash, the two technologies are very different. Both include features for playing audio and video within web pages, and for using Scalable Vector Graphics. HTML5 on its own cannot be used for animation and interactivity – it must be supplemented with CSS3 or Javascript. There are many Flash capabilities that have no direct counterpart in HTML5. See Comparison of HTML5 and Flash.
Although HTML5 has been well known among web developers for years, it became the topic of mainstream media around April 2010 after Apple Inc’s then-CEO Steve Jobs issued a public letter titled “Thoughts on Flash” where he concludes that “[Adobe] Flash is no longer necessary to watch video or consume any kind of web content” and that “new open standards created in the mobile era, such as HTML5, will win”. This sparked a debate in web development circles where some suggested that while HTML5 provides enhanced functionality, developers must consider the varying browser support of the different parts of the standard as well as other functionality differences between HTML5 and Flash. In early November 2011 Adobe announced that it will discontinue development of Flash for mobile devices and reorient its efforts in developing tools utilizing HTML 5.
More about CSS3
According to CSS3.info, CSS3 is the new kid in the stylesheet family. It offers exciting new possibilities to create an impact with your designs, allows you to use more diverse style sheets for a variety of occasions and lots more.
According to Wikipedia, Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation semantics (the look and formatting) of a document written in a markup language. Its most common application is to style web pages written in HTML and XHTML, but the language can also be applied to any kind of XML document, including plain XML, SVG and XUL.
CSS is designed primarily to enable the separation of document content (written in HTML or a similar markup language) from document presentation, including elements such as the layout, colors, and fonts. This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple pages to share formatting, and reduce complexity and repetition in the structural content (such as by allowing for tableless web design). CSS can also allow the same markup page to be presented in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow the web page to display differently depending on the screen size or device on which it is being viewed. While the author of a document typically links that document to a CSS style sheet, readers can use a different style sheet, perhaps one on their own computer, to override the one the author has specified.
CSS specifies a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities or weights are calculated and assigned to rules, so that the results are predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998), and they also operate a free CSS validation service.
CSS has a simple syntax and uses a number of English keywords to specify the names of various style properties.
A style sheet consists of a list of rules. Each rule or rule-set consists of one or more selectors, and a declaration block. A declaration-block consists of a list of declarations in braces. Each declaration itself consists of a property, a colon (:), and a value. If there are multiple declarations in a block, a semi-colon (;) must be inserted to separate each declaration.
In CSS, selectors are used to declare which part of the markup a style applies to, a kind of match expression. Selectors may apply to all elements of a specific type, to elements specified by attribute, or to elements depending on how they are placed relative to, or nested within, others in the document tree.
Pseudo-classes are used in CSS selectors to permit formatting based on information that is outside the document tree. An often-used example of a pseudo-class is :hover, which identifies content only when the user ‘points to’ the visible element, usually by holding the mouse cursor over it. It is appended to a selector as in a:hover or #elementid:hover. A pseudo-class classifies document elements, such as :link or :visited, whereas a pseudo-element makes a selection that may consist of partial elements, such as :first-line or :first-letter.
Selectors may be combined in many ways, especially in CSS 2.1, to achieve great specificity and flexibility.
Unlike CSS 2, which is a large single specification defining various features, CSS 3 is divided into several separate documents called “modules”. Each module adds new capabilities or extends features defined in CSS 2, over preserving backward compatibility. Work on CSS level 3 started around the time of publication of the original CSS 2 recommendation. The earliest CSS 3 drafts were published in June 1999. Due to the modularization, different modules have different stability and statuses. As of June 2012, there are over fifty CSS modules published from the CSS Working Group., and four of these have been published as formal recommendations.
More about Charles Wyke-Smith
According to his Linkedin page, Charles Wyke-Smith is a creative media professional focused on developing enterprise online SaaS applications and web sites that provide excellent user experience and quantifiable ROI.
Charles has consulted and developed online applications, web sites and multimedia for Palm, Wells Fargo, ESPN Videogames UCSF, and Benefitfocus, and have held VP and other senior positions for online companies.
The third edition of “Stylin’ with CSS” will be published in Summer 2012. The first two editions have sold over 30,000 copies. “Scriptin’ with JavaScript and Ajax” was published 2009. and “Codin’ for the Web” in 2006, all on the New Riders imprint of Peachpit Books. The second edition of Stylin’ was published in December of 2007.
He’s a regular conference presenter on the topics of web design and user experience at events such as SXSW (South by South West) and my publisher’s twice-yearly Voices That Matter web design conference.
I take great pride in combining business skill, design flair, marketing acumen, and programming abilities to deliver powerful online business solutions says Charles.
Next move: Solving the problem of book discovery in a disrupted marketplace.
Specialties
Leadership in online application and corporate web development, with deep knowledge of business management, venture funding, user experience, interface design, information architecture, and content management systems. Can define and manage online application development processes to design new and innovative products, and can lead design and tech teams in to develop projects in Java, ASP.NET and open source languages. Can program PHP, HTML5, CSS3, JavaScript, jQuery and more.
A special shout out to Charles Wyke-Smith, a super nice and gracious guy for taking the time to talk with us!
Web Professional Trends for 2013 – “Web Development” Interview with Chris Wilson, Developer Advocate at Google
In this twelve minute interview Chris Wilson, Developer Advocate at Google, we learn about Chris’s perspective on the topic of Web Professional Trends for 2013 as it relates to Web Development trends, Web standards and the Open Web.
•About the benefits and current trends of Encapsulation and Reuse
•The component model for the Web (also known as Web Components)
•Chris’s thoughts on a focus for developing for the user and how tools have made life much easier the for the Web developer
•Now is a great time to be a Web Professional
•Access to real world to the Web platform (audio and video inputs)
•Advice for aspiring Web developers and those that teach
•About Chris’s personal interest in audio and the Web audio API and his exciting efforts to support open standards for the WebRTC, (Web Real-Time Communication) an API definition that is being supported by Chris and others the World Wide Web Consortium (W3C) to enable browser to browser applications for voice calling, video chat and P2P file sharing without plugins.
More about Encapsulation
According to Wikipedia, in programming language, encapsulation is used to refer to one of two related but distinct notions, and sometimes to the combination thereof:
A language mechanism for restricting access to some of the object’s components.
A language construct that facilitates the bundling of data with the methods (or other functions) operating on that data.
Some programming language researchers and academics use the first meaning alone or in combination with the second as a distinguishing feature of object oriented programming, while other programming languages which provide lexical closures view encapsulation as a feature of the language orthogonal to object orientation.
The second definition is motivated by the fact that in many OOP languages hiding of components is not automatic or can be overridden; thus, information hiding is defined as a separate notion by those who prefer the second definition.
As information hiding mechanism
Under this definition, encapsulation means that the internal representation of an object is generally hidden from view outside of the object’s definition. Typically, only the object’s own methods can directly inspect or manipulate its fields. Some languages like Smalltalk and Ruby only allow access via object methods, but most others (e.g. C++, C# or Java) offer the programmer a degree of control over what is hidden, typically via keywords like public and private.[4] It should be noted that the ISO C++ standard refers to private and public as “access specifiers” and that they do not “hide any information”. Information hiding is accomplished by furnishing a compiled version of the source code that is interfaced via a header file.
Hiding the internals of the object protects its integrity by preventing users from setting the internal data of the component into an invalid or inconsistent state. A benefit of encapsulation is that it can reduce system complexity, and thus increases robustness, by allowing the developer to limit the interdependencies between software components.
More about Web Components
According to the W3c, the component model for the Web (also known as Web Components) consists of four pieces designed to be used together to let web application authors define widgets with a level of visual richness not possible with CSS alone, and ease of composition and reuse not possible with script libraries today.
These pieces are:
templates, which define chunks of markup that are inert but can be activated for use later;
decorators, which apply templates to let CSS affect rich visual and behavioral changes to documents;
custom elements, which let authors define their own elements, including new presentation and API, that can be used in HTML documents; and
shadow DOM which defines how presentation and behavior of decorators and custom elements fit together in the DOM tree.
Both decorators and custom elements are called components. For additional information visit http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html
More about WebRTC
According to WebRTC.org, the WebRTC (Web Real-Time Communication) is an API definition being drafted by the World Wide Web Consortium (W3C) to enable browser to browser applications for voice calling, video chat and P2P file sharing without plugins.
History
According to Wikipedia, a project known as WebRTC, for browser based realtime communication, was open sourced by Google . This has been followed by on going work to standardise the relevant protocols in the IETF and browser APIs in the W3C
The Web Real-Time Communications Working Group expects this specification to evolve significantly based on:
The outcomes of ongoing exchanges in the companion RTCWEB group at IETF to define the set of protocols that, together with this document, will enable real-time communications in Web browsers.
Privacy issues that arise when exposing local capabilities and local streams.
Technical discussions within the group, on implementing data channels in particular.
Experience gained through early experimentations.
Feedback received from other groups and individuals.
Design
As of March 2012 the IETF WebRTC Codec and Media Processing Requirements draft[9] requires implementations to provide PCMA/PCMU (RFC 3551), Telephone Event as DTMF (RFC 4733), and Opus (RFC 6716), along with a number of video codec minimum capabilities. The Peerconnection, Data channels and a media capture browser APIs are detailed in the W3C.
Web Audio API
According to the w3c, Web Audio API specification describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.
The introductory section covers the motivation behind this specification.
This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (using the responseType and response attributes). For games and interactive applications, it is anticipated to be used with the canvas 2D and WebGL 3D graphics APIs.
For additional information visit https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html
More about Chris Wilson
Chris Wilson, is a Developer Advocate at Google, Chris is a Web browser guy since 1993. Chris grew up in the Chicago, Il area.
Chris spent 15 years at Microsoft Co-wrote NCSA Mosaic for Windows, wrote IE’s original CSS implementation, worked on lots of standards. Chris Wilson was the group program manager for Internet Explorer Platform and Security at Microsoft. He began working on web browsers in 1993 when he co-authored the first Windows versions of NCSA Mosaic, the first mass-market WWW browser. This was also when he inflicted overlapping tags on the world. After leaving NCSA in 1994 and spending a year working on the web browser for SPRY, Inc., he joined Microsoft’s Internet Explorer team as a developer in 1995.
In the course of five years on the IE team, Chris has participated in many standards working groups, in particular helping develop standards for Cascading Style Sheets, HTML, the Document Object Model and XSL through the W3C working groups. He also developed the first implementations of CSS in Internet Explorer. Beginning in 2001, he spent a few years working on the Avalon project, but rejoined the IE team a year and a half ago to lead the IE Platform and Security team.
Chris resides in Seattle. In his free time, he enjoys photography and hiking with his wife and daughter, and scuba diving in the chilly waters of Puget Sound as a PADI Divemaster. With any free money, he replaces the cameras he’s destroyed by taking them underwater for dive photography.
Lastly, according to Chris, he builds cool stuff, and even more importantly, help other people build cool stuff and help Chrome build the right platform for people to build cool stuff on.
A special shout out to Chris, a super nice and gracious guy for taking the time to talk with us!
What’s in store for 2013 for Web Professionals – Interview with Bruce Clay, Search and Web marketing specialist
In this ten minute interview Bruce Clay, president of Bruce Clay Inc. a California based Internet marketing optimization organization providing search engine optimization (SEO) services, and pay-per-click (PPC) advertising management we learn about his perspective on the topic of Web Professional Trends for 2013 as it relates to Search.
* How Google changes everything every day
* That Google is in the business of making money (a concept often misunderstood)
* That over 90% of Google “clicks” on Search queries are on the first page
* How Google is limited and even restricted to advertising in the organic search location of “public trust” as outlined by the U.S. Federal Trade Commission
* YouTube videos yet to be monetized but probably will be soon
* How “paid” videos may be in the future
* How Google local could produce add in the areas of Google local
* That the organic ads need to be relevant and high quality to keep the loyalty
* Search for “hammer” on Google and see what you get
* How Google will use your search history to add relevancy to your search
* How this could effect and change the relevancy of search for Google
* How Yahoo/Bing has run ads that claim to be better than Google Yahoo –Bing market share has increased 9%
* Marissa Ann Mayer, formerly of Google fame and now the Yahoo new CEO will improve Yahoo significantly
* How Google + plus has a lot of growing pains and yet to be relevant and is the butt of many jokes
* Facebook is massive and has a ton of influence
* How “social media” search changes the dynamics of search
* How Social Media search still has limitations
* Mobile Search will change the game
* Responsive design is changing how we search and will be the de facto standard for “one content” strategy
* Google recommends only one copy providing more relevance to Responsive design
More about Responsive Design
According to Wikipedia, Responsive web design (often abbreviated to RWD) is an approach to web design in which a site is crafted to provide an optimal viewing experience—easy reading and navigation with a minimum of resizing, panning, and scrolling—across a wide range of devices (from desktop computer monitors to mobile phones).
Elements of responsive web design (RWD)
A site designed with RWD uses CSS3 media queries, an extension of the @media rule, to adapt the layout to the viewing environment—along with fluid proportion-based grids[8] and flexible images:
* Media queries allow the page to use different CSS style rules based on characteristics of the device the site is being displayed on, most commonly the width of the browser.
* The fluid grid concept calls for page element sizing to be in relative units like percentages or EMs, rather than absolute units like pixels or points.
* Flexible images are also sized in relative units (up to 100%), so as to prevent them from displaying outside their containing element.
More about Bruce
Bruce Clay, Inc. (BCI) is an Internet marketing optimization company providing search engine optimization (SEO) services, pay-per-click (PPC) advertising management, SEO-friendly Web design and information architecture, and social media and conversion rate optimization services. BCI is also the creator of the award-winning SEOToolSet® and its acclaimed SEO training course.
Bruce Clay has been a top search engine optimization company since 1996 through contributions such as author of the 746 page Wylie book Search Engine Optimization All-In-One for Dummies, SEO Code of Ethics, Search Engine Relationship Chart®, and SEO training and certification programs that promote ethical SEO practices. Headquartered in California, Bruce Clay, Inc. has global locations in Australia, Switzerland, India, Japan and Brazil.
