Secret Money Generator Documentation:
OVERVIEW
The Secret Money Generator program was designed to create static html pages based on a series of customer designed templates and a product data base.
Depending on the speed of the server and the size of the templates and database, this program can build approximately 250 pages per second! This number will vary depending on the size of your data feed, the size of your html templates, and the speed of your server.
By utilizing this merging of the product database with a few easy to design templates, a manufacturer or affiliate marketer, can create a complete product oriented website consisting of thousands of web pages in just a few minutes.
Template pages:
The template files are normal html pages. They can be edited with any html editor.
The operation of the templates is controlled by special tags which are inserted in the appropriate place in the template pages and the tags are identified from normal html code by putting them into brackets [ ]. For example [field KEY]. .
There are two basic types of template pages: a detail page, and an index page.
Detail pages: The detail page is usually a page devoted to a specific product. Typically a detail page would contain a photo of the item being sold, and such items as the product name, price, description, and a link to the purchase page for the merchant that provides the data feed. The Secret Money Generator creates one detail page for every item selected from the merchant’s data feed. Here is an example of a detail page:
http://www.sandalsite.com/shoes/Teva-133.html
Index pages:The index pages are, for the most part, used for navigation and categorization. We are not necessarily referring to the typical index.html home page. Index pages determine how a data feed is sorted and how the resulting website is organized. Typically they’ll create the navigation links to help visitors navigate quickly to the detail pages. The index pages also give the search engines a way to spider the entire site.
The Secret Money Generator can create up to 15 levels of index pages. These multiple levels of index pages are used when you have a main category that is broken into multiple sub-categories and each of those sub-categories is broken into sub-subcatgegories and so on. Using http://www.sandalsite.com as an example your main home page would just be a general intro dealing with sandals. The first index level would break that down into 4 different categories: Infants, Kids, Women's, and Men's If you were to go to the Men's category that would be further broken down into the sub-categories: Hydro, Nomadic, Originals, Sun & Moon, and Terrain. Each of those sub-categories is then broken down to the individual products. It is kind of hard to describe but if you go to http://www.sandalsite.com and follow the links on the left hand side of the page you will get a better idea of what we are saying.
This particular site has 3 levels. Each index level will have a separate template page. For a 3 level site you will need 3 index templates. A 4 level site will need 4 index templates and so on.
Tags:
The tags tell the program to put specified information into the right place on a page. Tags are identified from normal html code by putting them into brackets [ ]. For example [field KEY].
Naming Convention: In all our examples, the word KEY in capital letters refers to the name of the field in the data feed. Therefore if the name of the field is CATEGORY, the field tag would be written like this: [field CATEGORY]
The program will write the value of the field "CATEGORY" on the web page at the location where the tag is at.
Index Pages
One of the most powerful features of the Secret Secret Money Generator program is the ability to build up to 15 index levels. An index has three basic functions.
- To help people navigate quickly to the products they’re looking for.
- To help SEARCH ENGINES find and catalog all of your pages
- To provide additional information about your company, products, or service.
If you’ll go to this URL you’ll see an example of a site that was built using Teva’s data feed.
The first page you see is an index page. It divides the products up by Gender. Gender, as defined by the Teva data feed puts infants and kids separately. In this case it’s Infants, Kids, Men, Women. You’ll notice that each of those links takes the visitor deeper into the site. Click on any one of the items, and you’ll be taken to another index page. Those index pages are broken up even further.
Index Page Tags
The index pages use specialized site-builder tags to gather information from the data base and place it in the proper location on the index pages. Let's use the following datafeed snippet for our examples:
Record Tag: [record KEY: record body]
The record tag is only used in index pages.
This tag tells the program how to categorize the datafeed and how to display the results. The section indicated by “record body“ is repeated once for each record to be shown in this index page. Using the Teva data feed example:
[record Category: [*field Category]<br>]
- The data base is sorted by Category
- For each row, the field NAME is displayed as a link to the corresponding index or detail page. (The * tells the program to display as a link)… see the field tag description for a more complete explanation)
- After each such link, a line break <br> is inserted.
(Because it’s included in the above [record] tag before the closing
]
The resulting output would be (note: the links don't work, they are just in for the example):
Hyrdo
(which would link to http://www.sandalsite.com/hydro.htm)
Nomadic (which would
link to http://www.sandalsite.com/nomadic.htm)
Originals (which
would link to http://www.sandalsite.com/originals.htm)
Sun & Moon
(which would link to http://www.sandalsite.com/sun_&_moon.htm)
These links would take you to your second level index page which in this case would be the Product_Name page. On this template you would use the tag [record Product_Name: [*field Product_Name]<br>] and on the hydro.htm index page the output would look like this:
Teva
Proton II (which would link to http://www.thesandalsite.com/teva_proton_II.htm)
Teva Onium Pro
(which would link to http://www.thesandalsite.com/teva_onium_pro.htm)
Teva Neutron
II (which would link to http://www.thesandalsite.com/teva_neutron_II.htm)
etc.
If this is the last level index template (which this is in our example), the links will go to the detail pages.
[record KEY: max_rows=x: record body]
This record tag is used when you want to limit the number
or links on a page. For example, if you had 50 sub-categories you probably
wouldn't want to put all those on one page. You could set the max_rows=x
to 10 or 20 and it would only list that number or sub-categories on one
page and then create other index pages for the rest of the links.
#Record: [#record KEY]
This form of the record tag allows you to do the same thing, but within tables.
For example, the following table utilizes the [#record] tag within a table.
[#Record NAME] Name: [field NAME]
If we used this example….
|
[#record NAME] Name: |
[field NAME] |
Or in html it would look this way:
<table border="1">
<tbody>
<tr>
<td> [#record NAME] Name:</td>
<td> [field NAME] </td>
</tr>
</tbody>
</table>
In a preprocessing step, the [#record] tag searches for the enclosing <tr> HTML-tag and uses this record as record-body. ).
The result would look like this:
|
Name: |
Name1 |
|
Name: |
Name2 |
|
Name: |
Name3 |
|
Name: |
Name4 |
|
Name: |
Name5 |
|
Name: |
Name6 |
In short: If you want to generate a table with one row for each data base record, make a one row table in an index template and place [#record KEY] in one of the table cells.
You can (and probably will) use any of the detail page tags discussed below on index pages.
Note: On the last index template, you find one link for every data base record selected, even if there are many records with the same name. On the other levels of index pages if you have multiple items with the same name there will only be one link. In most cases if you properly categorize the datafeed and build the site correctly this won't be an issue but occasionally you might run into a scenario where a database has multiple items with the same name.
Detail Pages Tags:
A detail page template will build one page per record in the data feed. Basically the detail page will contain information about a specific product. Generally speaking you will have on product per page. Lets use the following data feed as an example:
In this case the program will build a separate page for each of the products in column A. Here are the tags you will use with the detail pages:
Field tag: [field KEY] : The Field tag is used to place the value of a field on the datafeed into the outputted webpage. For example, if I had a datafeed with a field called "Product_Name" and I put the tag [field Product_Name] in my detail template the program would write the product name into that spot on the outputted webpages. Using the above datafeed as an example, the first detail page will have "Teva Proton II" in place of the [field Product_Name] tag, the next detail page will have "Teva Onium Pro", and so on.
Image tag: [img KEY] : The img tag is used to place an image on the web page. The actual value of the KEY field is a valid image URL. The site-builder inserts this image into the page. Using the above sample datafeed as an example your tag would look like this: [img Image_URL] and would insert the images into your detail pages.
Link tag: [link KEY: link text] The database field KEY contains a valid URL. A link to that page is created around the link text. It’s possible to embed further links in the link text section. In this example your link tag would look like this: [link Buy_URL: Buy this sandal today] and on your page you would see the text Buy this sandal today which would be linked to the merchant's page relating to that particular sandal. This link is to the merchant's page for the Teva Proton II.
These three detail page tags can also be used (and in most cases will be used) on the index template but the index page tags cannot be used on the detail template.