Content Management: Building a sitemap for your dynamic Texty content

If you followed along with my last series of posts, I’ve showed you how to build a customized content management system into your Web site using AjaxIncludes, Zoho Creator’s JSON feeds, and the powerful Texty SCMS (Simple Content Management System). In this last post of this series, I want to show you how you can expand the same principal to not only deliver the content to your site, but to build a simple sitemap to help your users find content within your site.

As with the other content management systems I’ve discussed, the actual text delivered to your Web site will not be indexed by search engines such as Google. Most major search engines ignore any text delivered to your page via javascript or other scripting methods that take place in the browser, rather than on the server. If you happen to have a Web site that allows you to run javascript codes on the server side, you can avoid problems with indexing your site content by adding a code within your <script> tag to tell the server to run the code before delivering the page to your user. Simply change <script> to <script runat=server>. However, if you are using Microsoft Office Live Basics, you can not run any scripts at the server level, so you have to find some other way to deliver your content. I will spend a little time discussing the problems this presents to individuals and small businesses trying to establish a Web presence in the next series of posts.

Essentially, you will use the same procedure I outlined in my last post to build your sitemap as you do to build your general page. In fact, you can use the code below on a single page and, if a specific article is requested in the URL (articles.aspx?271), the article will be displayed. If no article is requested  (articles.aspx) or a nonexistent article is requested, the user will be shown a Table of Contents. This is nice because your single page serves a dual purpose. As before, you want to load your Zoho Creator JSON code into your page and then go through the records one by one. This time, however, instead of only writing out a single story, you will want to write out all of your stories…

Below is a sample code based on the following assumptions:

  1. You have already generated a Zoho Creator database to hold your Texty codes. This database has the following fields: TextyID (a code you assign to this texty when you put it in the database. Depending on your needs, this could be a number, the default Zoho ID, a short word-description, or a combination of values), Title (A short title to display), TextyCode (The <script> code generated by Texty, which you want to include in the page.
  2. You are using a single value to identify each texty (Instead of “texty.asp?page=27” or “texty.asp?article=TGIF”, you are using only a single value like “texty.asp?47” or “texty.asp?MOLB”).
  3. Your Zoho Creator database is already sorted by the appropriate field.
  4. You are using Microsoft Office Live Basics (or a similar Web page that allows only HTML codes, not server-side scripting languages such as ASP.NET or PHP).
   <!–Load your Zoho Creator Data–>

    <script type=”text/javascript” src=”{Username}/json/{View Number}/”></script>


    //Parse out the attributes from the URL

    var winloc=””+top.window.location;

    var winsplit=winloc.split(“?”);

    var marker=””;

      if (winsplit.length>1){ //If an attribute is found in the URL

      for (var i=0; i<zoho{Username}view{View number}.Texty.length; i++){

        var NewArray=zoho{Username}view{View number}.Texty[i];

        var val=NewArray.TextyID;

        val = val.toLowerCase();

        var thisparam=winsplit[1].toLowerCase();

        if (thisparam==val){


           marker=”content”; //Content has been found…display content instead of Table of Contents

          document.writeln(‘<scr’+’ipt type=”text/javascript” language=”javascript” src=’+TextySource+’></scr’+’ipt>’);

  //Write the content on your page

          if (NewArray.Title>””){

            document.title=NewArray.Title; //Make the page title match the Texty title





    else { //No parameter found in the URL

    //Write out a link to each page you have entered in your database to create a Table of Contents

      for (var i=0; i<zoho{Username}view{View number}.Texty.length; i++){

        var NewArray = zoho{Username}view{View number}.Texty[i];

        var Title = NewArray.Title;

        var val = NewArray.TextyID;

        document.writeln(‘<p><a href=”articles.aspx?’+val+'” title=”‘+Title+'”>’+Title+'</a></p>’);



    //If parameters passed in the URL do not match any content, clean up the URL by removing failed parameters. This prevents people from bookmarking incorrect pages, and allows the “Table of Contents” script above to run

    if (winsplit.length>1 && marker==””){


    }  </script>

This relatively simple script allows you to, essentially, create an entire Web site by coding only a single page and using Texty’s powerful content management system to deliver variable content to that single page. I think Texty is an excellent solution for this, but just for your information, this same type of content management system can be used with files stored on your Web site. Instead of loading the Texty script containing the identified content, you can use AjaxIncludes to write the contents of a file on your site into the page (Some people have expressed concerns about Texty’s future in the crowded Web 2.0 marketplace, although I hope/believe Texty is here to stay).

Please keep in mind that none of the content management systems I have described in this blog will allow search engines to properly index your Web site and display your Web pages in search results. To ensure your pages are optimized for search engines, you would need to write your codes on the server-side using a scripting language like ASP.NET or PHP. However, I have yet to find a free Web hosting solution that offers these scripting languages, and I don’t want to pay money for my Web site, so I stick with my SEO-free pages, and rely on my blog to drive traffic to my site (

To be honest, though, I’m quite happy that my site is improperly indexed by Google and other major search engines. I’ll explain why I feel this way in my next series of posts, which will provide a very rough sketch of how search engines view your Web site, and why none of them are doing the job properly.

That’s all for today. I know that this blog has become increasingly technical over the past few months, which is fine with me. However, I originally intended this blog to help out not only the advanced HTML-coder and site designer, but to also be of more use for the middle- and entry-level users. Furthermore, I want to do more reviews of other free Web resources besides Microsoft Office Live Basics and Zoho Creator. I’m looking forward to getting “back to the basics” in addition to writing more advanced content.

One Reply to “Content Management: Building a sitemap for your dynamic Texty content”

Comments are closed.