API Documentation
Came across these while researching for API documentation best practices:
Came across these while researching for API documentation best practices:
Windows Internet Explorer 9 introduces pinned sites, a feature with which you can integrate your websites with the Windows 7 desktop. With pinned sites enabled for a website, users can pin that site to the Windows 7 taskbar or add the site to the desktop or Start menu. Pinned sites enable easy access to favorite websites and add shortcut functionality similar to that found in Microsoft Windows applications.
The following code example uses meta elements to customize the pinned site shortcut with a name, tooltip, start URL, initial window size, and navigation button color.
<meta name="application-name" content="Sample Title"><meta name="msapplication-tooltip" content="A description of what this site does."><meta name="msapplication-starturl" content="http://www.example.com/index.html?pinned=true"><meta name="msapplication-navbutton-color" content="#f00"><meta name="msapplication-window" content="width=800;height=600"><meta name="msapplication-task" content="name=Task 1;action-uri=http://host/Page1.html;icon-uri=http://host/icon1.ico">
<meta name=”msapplication-task” content=”name=Task 2;action-uri=http://microsoft.com/Page2.html;icon-uri=http://host/icon2.ico”>
By using this nifty protocol-relative URL trick
web.config configuration best practice rules for making web pages fast and secure
Node.js is a server-side JavaScript environment that uses an asynchronous event-driven model. Node is built on top of Google’s V8 JavaScript engine. Google V8 actually compiles JavaScript into native machine code prior to execution, resulting in extremely fast runtime performance. Node enables you to rapidly build network apps that are lightning fast and highly concurrent.
Node.js and “event-driven” programming is best explained by this post using two analogies
Related Links: