When creating a technical article on a web page, you may need to embed equations in the page.

A way to do this easily, is to use the LaTeX Equation function from http://www.codecogs.com
This tool uses a base URL of  "http://www.codecogs.com/eq.latex?" with the LaTeX code for the equation to render placed after the question mark.

As an example, I will use the following LaTeX notation to describe the equation.

To get this equation into the page as an image, just place the following HTML into the page source code.

Below is the rendered equation as an image in a little table for layout.

Equation 1.1

To be extra informative you could place the LaTeX for the image in the 'title' tag. So the final HTML would look like.

Idea for this inspired by a knol at: http://knol.google.com/k/michael-chelen/embed-equation-online/gxxp1ckx8nad/2#

Currently I work at the National Institute of Standards and Technology (NIST) in Gaithersburg, MD which is under the US Department of Commerce. Here is my Staff Profile page on the BFRL website.

I have recently moved to the Fire Fighting Technology Group (FFT) with a focus on efforts within the Advanced Fire Service Technologies Program, in the Fire Research Division [Link 2] of the Building and Fire Research Laboratory (BFRL).
Prior to joining the FFT group, I was a member of the Fire Modeling Group. My primary work with the Fire Modeling Group was to assist in the development and support of the Fire Dynamics Simulator (FDS) and promoting its use across the United States and Internationally. One of my first tasks at NIST was to modernize the development methodology, support and distribution of the FDS software.  By utilizing freely available web services provided by Google (Google Code, Google Groups), this set of tasks was quickly accomplished within my first 6 months at NIST.  Then time was taken to introduce standard software development best practices to the development team, such as; code revision management, standardized version scheme, publicly available bug reporting and issue tracking system, and integrating change logs into the documentation.  By bringing a host of new services and support features online we have also been able to tap into the global user community as a development resource, and provide immediate feedback from reported bugs and questions regarding the software.

These efforts have brought more consistency and stability to the FDS project and allows the development group the freedom to rapidly integrate new changes to the software and documentation in parallel, eliminating the serial development bottleneck of the past.  Before I started at NIST, changes to FDS were funneled through the lead developer, each change from the development team had to be woven into the evolving source code by him and then tested and recompiled.  Now each developer has direct access to the latest version of the source code through Subversion and can test their changes locally before committing it into the repository.  By enforcing the standard practice of 'update, modify, update, test, update, commit, repeat...' into the work flow, the development team is always working with the most recent version of source and reduces conflicts resulting from parallel modifications to the source.
I look forward to continued success in many of the opportunities that I am presented with now and into the future at NIST.