This template set is a translation of the popular Wordpress Sandbox theme for TypePad Advanced Template users. Sandbox, originally developed by Andy Skelton and Scott Wallick, is designed to be skinned with CSS. As noted on the home page of Sandbox (http://www.plaintxt.org/themes/sandbox/), "the core feature of the Sandbox is its markup. The class-generating functions included with the Sandbox create an extensible and semantic XHTML structure."
I made this a couple of years ago, and haven't updated it since. Thought it would be worthwhile to make it available more broadly.
I recommend that you have some familiarity with TypePad Advanced Templates before installing the Sandbox template set for TypePad.
First, of course, you'll need a Pro-level account or above at TypePad. (Get one today at www.typepad.com.) And you'll need to create a new Advanced Template set for your blog, and then apply it to your blog.
You'll only need to replace two of the index templates that are listed: the archives index template, and the main index template.
-
Replace the contents of the Archives Index Template (that outputs archives.html) with the contents of the file archives.html.
-
Replace the contents of the Main Index Template (that outputs index.html) with the contents of the file index.html
You can leave the other index templates alone, though if you're not into clutter, you can feel free to remove...
- The RSS 2.0 Template and the RSS Template, since our Sandbox Theme references only the Atom Template for its feeds.
- The Stylesheet and Theme Stylesheet templates, since our Sandbox Theme is designed to point to a Sandbox theme stylesheet that lives locally in TypePad or remotely on one of your other servers.
You'll need to replace all of the Archive Templates; these control the design of your blog's date-based archives, category-based archives, individual entry archives and page archives.
-
Replace the contents of the Category Archives template with the contents of the file archive-template.category.html.
-
Replace the contents of the DateBased Archives template with the contents of the file archive-template.dabasebased.html.
-
Replace the contents of the Individual Archives template with the contents of the file archive-template.individual.html.
-
Replace the contenst of the Pages template with the contents of the file archive-template.pages.html.
You'll need to replace all of the content modules. These are used to provide commonly used sidebar and navigation modules across your blog, as well as one content module that you should customize in order to point to a sandbox-enabled style.
Here are a list of the content modules included with the theme...
-
About, a module intended to provide a short description of your blog, which is included in module.about.html
-
Archive-listing, a module that provides links to recent monthly archives pages for your blog. Included in the file module.archive-listing.html
-
Categories, a module that provides links to your category archive pages. Included in the file module.categories.html
-
Footer, a module that provides the navigation footer for your blog. Included in the file module.footer.html
-
Site-navigation, a module that provides the top navigation for your blog. Included in the file module.site-navigation.html
-
Stylesheet-pointer, a module that gets included in the head of all of the pages of your blog, so that you can change the pointer to your CSS file once across the site. Included in the file module.stylesheet-pointer.html
Once you've installed the templates and the modules, you should customize the "stylesheet-pointer" module to point to the Sandbox theme CSS of your choice. If you're using a pre-built Sandbox theme from the Wordpress community, I highly recommend that you upload the CSS file and related images to your TypePad account, or FTP them to a server you control and point your stylesheet to that location.
And, of course, once the theme's installed you can customize it to your heart's content...
- Modify the navigation, footer and about modules
- Add new modules if you'd like
- Change the order of modules in the templates themselves
- Etc., etc.
I have not included any stats tracking JavaScript in the template files. If you'd like to include stats tracking, I recommend adding an MTInclude module statement to the end of every page that references an include module containing your stats code.
- There is no styling of odd / even comments
- There is no styling of comments by the author of the post