dreamweaver .net sql server graphics compass max miscellaneous cart | sign out

template and menu hot sauce - the NEW BETA version See the completely new features of the BETA product Which is better for website design? Include Files: server-side includes (ssi) Templates I already use templates. What can nested templates do for me? I have an E-commerce site that uses a SINGLE product page that changes via the query string. Can your product integrate with a single page? Auto Collapsing Tree Menus versus the Traditional Non-Auto Collapsing Tree Menus Enough of this. Take me to your demos.     Yes you can take your existing Dreamweaver templates and convert them over to nested templates. This is all discussed in the Nested Templates and Menus Instruction Manual, Chapter VIII - Upgrading your Existing Templates x Furthermore, you can also see the Upgrade Support Page on Upgrading your FrontPage, Adobe GoLIve, frames, or any other html website Therefore, you are not starting from scratch when you make a nested template system. In fact, you can upgrade all your templates and web sites.   Maintenance. Those sites do it with either really complex server side, JavaScript and/or CSS programming or simply do each and every web page by hand with lots and lots of search and replace. They also have the man-power to do it. Thus, it would be a huge maintenance task just to add or modify a single sub-menu item/web page to the navigation bar. (Notice that each web page has it's corresponding Main Menu and the Sub-menu item highlighted.) Performance. All the pages are pre-generated and produce pure HTML No hitting against a database. Or using overly complex JavaScript and CSS programming. WYSIWYG - What You See, Is What You Get design view editing in Dreamweaver MX or MX 2004. With these other complex server-side JavaScript and CSS technologies, you can't see the actually menu items in design view. With our product you can and you can even understand the code as it's simple HTML. See the Features Page for a complete list.     Nested Templates are about as friendly are you can get for search engines. Each page can be static or dynamic and the URL can also be easy to remember. Furthermore, as for search engine ranking, templates are great because each individual page can have it's own <title> tag as well description, keywords, meta tags, JavaScript and CSS files, etc. With templates, you can have the best of both worlds, pages that are easily undateable with a common look and feel, AND pages that each have their own individuality and content and meta content and server side code. See our support page regarding "Designing for Search engines"     You still can. However, if you want to be really productive and produce user friendly, websites, you want to do the follow three (3) things. First, you have a double context sensitive menu. That is, the sub-navigation menu changes for each section of the site. Second, you want to maintain the same "look-n-feel" through the entire site. Third, each sub-menu is highlighted depending upon the current page. That is, the entire menu has "bread crumbs" built right into the menu as opposed to a separate text link. (bread crumbs show the user where there are in your site just like the "You are Here" words on a Shopping mall map.)     Basically, if you wanted a navigational menu system like that found at www.apple.com web site, you could NOT do it with just regular Dreamweaver 3 or 4 Templates. That is, it would be a huge amount of maintenance just to add or modify a single sub-menu item/web page to the navigation bar. (Notice that each web page has it's corresponding Main Menu and the Sub-menu item highlighted.) However, using the Nested Templates Combo Starter and Upgrade Kit you can make this same type of menu system but get the same speed and maintenance as regular templates in adding or changing menu items.     First, regular templates allow you to make changes across the entire web site (which is great in itself). However, with Nested templates you get the same benefits as with regular templates, BUT with the added ability to make changes across "sections" of a web site. (e.g. departments, product categories, etc.) This allows you to have a far more intuitive menu bar where the user does NOT have to search in the popular hidden drop down lists. (probably the best example of an intuitive menu bar is the Apple web site, which uses NO drop down menus. If you were to do this site with just regular templates, you could spend an incredible amount of time updating links as each section has it's own set as you still need to maintain the overall look and feel) So, for example, a corporate web site can have a single unified look and feel while still being able to give each one of its departments its own unique look and feel and sub-menu navigation system. Just as regular templates can save web designers and developers time, Nested Templates can save even more time for large and complex web site.   Each individual section of the website can also have some of it's own look and feel to signify, for example, it's own department Colors. Yet, the entire web site can be completely updated from the original template while not affecting other parts of the website or department sections Uses the latest Dreamweaver MX technology to easily add individual menu items as well as completely change entire sub-navigation menus for an entire section. Menu Items can be completely PURE HTML in the end thus giving the web site max scalability and performance. Menu Items can also implement JavaScript rollovers if need be. And it can use both images and/or text as links. Tree Menus can also be done.     Able to customize template while still being able to offer Context Sensitive Sub Navigation Menus. Great for sites that are large and complex. Or for sites that are growing Users will find using Context Sensitive menus very easy to use and great time saver navigating a web site.     Because this uses Dreamweaver MX technology, all files can be simple HTML. Thus, even Mozilla, NeoPlanet, Opera, Apple's Safari, Netscape 4.x, you name it. If your browser is can read simple HTML, it will work. If you want to avoid using JavaScript or CSS so that it can read by screen readers for the visually impaired, that's completely OK with this product as it can even use <FONT> tags. Check out Extreme Cross-Browser Compatibility page for wanting to be Section 508 Accessible.     Nested Templates does NOT use complex JavaScript code. However, if for example you wanted JavaScript roll-overs, you could easily add this to your navigation menu. HOWEVER, check out the Demo Patterns for a JavaScript Nested Templates example. Works great with or without JavaScript. This is all Dreamweaver MX templates and library technology. NO JavaScript, CSs, ASP, ASP.NET, ColdFusion, PHP, J2EE, required     No problems whatsoever. This is all Dreamweaver MX templates and library technology and generates pure HTML before hand.     You want to have a navigation bar that can do this and this while still being able to use templates that can make massive changes across the entire site and with the added feature of making changes across sections of a site. You have read all the books and searched all the newsgroups on Dreamweaver Templates but they haven't showed you how to actually use them to build this type of web site. You don't want to spend days or even weeks, finding a solution to making a context sub-navigation menu work in the real world. Drop Down Menus   = 2 click Context Sensitive Menus   = 1 click     Savings   = 1 click = 100% return = TWICE AS FAST!     You finally realize that javascript drop down menus make the user do twice the work to find something as opposed to context sensitive sub-navigation menus (2 clicks versus 1 click, especially when doing a lot of navigation daily) REGULAR TEMPLATES can ONLY GO SO FAR You realize that using the regular templates of Dreamweaver can only go so far and that to produce a navigation bar like this will have you running through hoops and about 10 times more work just to update a simple link or add another page to a web site. LESS MAINTENANCE....A LOT LESS You already have a context sub-navigation system that requires a huge amount maintenance time just to update links, add pages or delete pages. This is probably the biggest advantage of nested templates as it's the biggest time saver. APPLE.COM "like" menus system If you notice, the www.apple.com web site has been around for at least 3 to 4 years and it's the most easy to use web site out there. Yet most web sites have not copied Apple's navigation menus because it requires a huge amount of work to manage all the links and so far Dreamweaver regular templates are NOT able do it. (NOTE: decloak, Inc is NOT affiliated whatsoever with apple.com, nor do they endorse us either. Would we like for them to recommend us? of course! But it's probably not going to happen as we make stuff for both WIndows and the Mac, not just the Mac.) Don't want a Complex JavaScript Solution You don't want to be tied to a complex JavaScript or CSS solution. You also don't want to be tied to an Extension for making updates. And you want to have more freedom in making the buttons and look and feel like normal templates. You want to fully utilize the base feature of Dreamweaver MX template programming language with minimal learning time. You want the same flexibility and power as regular templates, yet you want to make a context sub-navigation menu. MAX PERFORMANCE, MAX BROWSER COMPATIBILITY You want max performance on your web site as this does NOT need any server-side scripts. Just Pure HTML and Dreamweaver MX. Thus, browsers like, Netscape 4.x, Apple's Safari, IE, Opera, Mozilla, and NeoPlanet work. E-COMMERCE, CRM, PRODUCT CATALOGS, PORTALS You have a e-commerce or corporate site with many pages that needs to be organized. Use Templates before Library Items As an experienced Dreamweaver user, you realize that you need to get as many parts of a web page into the template as possible before resorting to a library item. Since the sub-navigation bars are inside the nested templates, you don't have to worry about the wrong library item being in the wrong page. You eliminate the maintenance hassle and you can switch library items without fear of orphaned web pages. Regular Templates provide consistent a look and feel. Nested Templates provide for a consistent look and feel as well as organization in large web site.     Trying to setup and show someone how to use Nested Templates is not simple. That's why there is a Fully Illustrated Color Instruction Manual. By being simple, VANILLA like, Dreamweaver MX Designers can take a look at the template code language and see how all of the template and library items are setup without any extra markup that can confuse a new user. If there were JavaScript rollovers and all that other flashy stuff, web designers and developers could easily get lost trying to understand all that extra code. It's far more important to understand how Nested Templates work. After which, you can take your existing templates (or buy the look and feel you want) and then update the demo web sites.     Please see the page, What's Included in the box for complete details LINKS to TEMPLATE TUTORIALS Question: If you needed to make the same change to 10 or more pages at once, How do you do it? Would you open up all 10 pages and change each one, one-at-a-time? Answer: http://www.dwfaq.com/Tutorials/Basics/dwtemplates1.asp http://depts.washington.edu/trio/comp/howto/page/dreamweaver/mxtemp/index.shtml http://www.dw-fw-beginners.com/tutorials/drmwvr/templ_1.htm http://www.image.ufl.edu/help/dreamweaver/templates.shtml http://www.epinions.com/content_141237390980 Templates - The ability to design a template allows me to quickly create new pages using a standard layout. I create the basic page templates, then I can go back and edit the template and let the changes apply on all pages built on that template. The is great for people who constantly like to tinker with a site (that's me). It allows allows me to build new pages a lot faster. http://www.webmasterworld.com/forum46/592.htm   WHAT USERS WANT Users find Context Sensitive Sub Navigation menus a big time saver as there are no hidden drop down menus to open up and thus it's much easier to find what they are looking for. (e.g. www.apple.com web site) Users can see the sub categories without having to search or click with the mouse. It's also easier for Customer Support to show users where to click. PROBLEMS TRYING to do WHAT the USER WANTS Creating a web site with Context Sensitive Sub Navigation menus is very hard, and time consuming. Adding or Making changes to links is also time consuming as well as confusing. Basically, if you wanted something like the APPLE.COM web site navigation, you could NOT do it with just regular Dreamweaver Templates. That is, it would a huge amount of maintenance just to add or modify one page. Dynamically generated code using JavaScript, PHP, C#, VB.NET, Perl or J2EE that are currently used to make Context Sensitive Sub Navigation Menus are commonly hard to work with and are quite difficult to understand and install. A strong understanding of the underlying code is needed to implement, as well as maintain the web site, especially for debugging purposes. Web Designers have a hard time working with the current solutions as complex code is needed and can be somewhat limited in variety of the look and feel wanted.

terms of use | privacy policy copyright © 2003 - decloak, inc. all rights reserved