This is a unique way of using custom tags that makes the pages easier to read. When we have tag libraries, we prefix the tag with the library name and a colon, rather than the traditional cf_ prefix. While creating tag libraries, you need to know the path of the files in your library. They should be in one directory. You must create a library call on every page that uses the library form of call. Here is sample code for creating a library. We should always try to put it at the top of the page:
<cfimport prefix="skin" taglib="/share/tags/skin"> <skin:page > Page content </skin:page>
This would run similarly to our <cf_page> tag call, but it is declared in the code that we are using the skin library. Normally, any of these libraries are stored together. So, a common practice is to use the tag library approach. This does not require the use of the application settings. The only challenge is that any code using this will require the custom tags to...