DW Template Limitations on Editable Regions
Ok, I’m self-taught in addition to still learning, but Love it if more enjoy the beauty of having a basic page template for my website. This gives me the capacity to change the planning of my website, add a food selection option, or other universal changes but not have to painstakingly perform this for VERY web page.
This is where I’m working with a small issue, which relates to important SEO features for each of my web sites. It is the understanding that among several other elements that may help raise my ranks is my web site are my webpage title tags. One articles makes this particular statement: " TITLE tag has become the most important point of On-Page Optimisation. "
In having a DW template, Concerning locked the concept tag and cannot make changes to ANY in the other webpage games. Having different title tags for every webpage, which depend on the content at that page, would probably aid in this SEO efforts. Ideally I want my " subject matter rich" website to make use of the article content’s bill (headline) as the TITLE tag for the page, but I cannot let that happen without " detaching the actual template" from everyone of my current webpages, then inputing the specified TITLE tag for each page.
The template fraction of my website pages is through it can be " working phase" along with I don’t prepare for any changes, but I still like getting the ability to help make quick and simple universal changes to some single file (DWT) and get the Dreamweaver application update Every one of the webpages fast and easy.
There has to be any way to produce that " TITLE" tag area of my template a strong " editable region" I initially tried to undertake that, but it only inserted a standard " text editable spot, " rather than a code editable district.
Am I merely SOL
Without digging much into it, Absolutely , you can enter code view and place the editable region where you choose.
<! — InstanceBeginEditable name=" doctitle" –>
< title> Aero Web site Design Services- Detroit, Opening Huron area< /title>
<! — InstanceEndEditable –>
This is the snippet from our site. You should be able to use this code instead of what you have with your template. Let me recognize if that works available for you. If not, show me what you’ve got and I’ll consider it further. While always, save a copy of one’s current template in case something goes incorrect when your messing around with editable zones.
Thanks aeroweb99 (Steve)… in which worked fine.
Sorry it got me awhile to acquire back out below (the forum) in order to read your response And to properly thank you. I just started a fresh job about every thirty days ago, which includes a pretty huge learning curve to it. It’s a brand new sales job providing digital voice, data, and video tools and services. I got NOT totally ignorant in the technology (got a good AA degree around Elect/Comp Tech), but I have learned a lot about some amazing new technologies and services which can be currently available and many more that is " forthcoming soon. " Fiber optics is a driver for these types of things and I learned that recent tests by NTT throughout Japan successfully sent 14 trillion rolls per second by having a single strand of fiber Understanding that data rate will be tripling every ninety days and expected to perform so for the following 20 years!
NEVERTHELESS… thanks again for ones help, it worked great! I had to make some modifications towards the naming scheme for that other " Editable Regions" in my template website marketing the new region for the " title" tag to figure properly or so that it seemed. My EditRegions had to be renamed, because it will help within tracking and identifying those regions to come, especially if MY PARTNER AND I add more of which. I had formerly let DW name them towards default names connected with " EditableRegion1, ER2… for example. ).
I guess I should have studied up much more on DW Themes, because I had previously considered DW Template Editable Zones as primarily or solely being used to place and still provide sections of the actual page content (text, layouts, objects… etc. ). Ever since I know I will have an " Editable Region" for Html page, then I’ll have the ability to work through different rather frustrating issues I’d previously encounted once i often attempted my own " learning" experiments using direct Html page entry in that Code View involving DW. When wanting to use some different codes and/or diverse coding combinations (my " trial and error" approach to self-education), I would often get yourself a template error including code locked through the template. While you simply can’t make any changes into the template code within a web page, I believe I was putting and/or using code that is tied to, referencing, or affecting locked code in the template (or similar to that).
Ever since I know I WILL unlock code inside template by doing that code an " Editable Spot, " then I will be able to resolve my preceding errors and fix them going forward. Don’t ask my family the specifics in my " HTML PAGE coding experiments, " because the way to awhile since I’ve done some of my " trial and error learing methods" IN ADDITION TO I’m often making use of commands or strings this I’ve " captured" from other webpages and pages. I’m really not PIRATING anyone’s Html code, but just wanting to learn – " How Did They actually That"
MANY THANKS AGAIN, Steve….. AMAZING!