User Guide

Getting Started with eeSiteKit

Before you install eeSiteKit there are few things you should take care of first.

  1. Puchase eeSiteKit: There’s a *Buy eeSiteKit* button on this page if you have not already purchased a copy. Shortly after you’ve purchased a copy you’ll receive an email with instructions for downloading it.
  2. Read the License: We’ve done our best to keep the license simple. If you have any questions about the license, .(JavaScript must be enabled to view this email address).
  3. Install EE: Make sure you have a full copy of ExpressionEngine properly installed and running on your server or in your hosting account. You must install ExpressionEngine before you can install eeSiteKit.
  4. Current Version and Build of EE: If EE is already installed, make sure you are running the current version and build of EE. The version and build are listed at the very bottom of every page in the EE control panel. You can find out what the current version and build are by visiting your download page at EE’s website. If your version or build has fallen behind, you’ll want to update your install before you install eeSiteKit.
  5. Remove or Rename Conflicting Template Groups: By default, EE may have installed template groups, or you may have previously created template groups in a site that should be renamed before you install eeSiteKit. It’s important you insure that none of your current template group names match those of eeSiteKit before you run the installer script. You’ll find an “Edit Group” link in the second column of the “Templates” tab in the CP where you can rename a template group.

     

    eeSiteKit installs the following template groups:

    • kit_display
    • kit_display_light
    • kit_system
    • kit_css
    • kit_forms
    • kit_language
    • home
    • pages
    • print
    • search
    • share
    • sitemap
  6. Know the URL to Your Public Directory: If you are building or rebuilding your website at your domain address, then it’s pretty easy. The URL will likely be: 
    http://www.asitedomain.com/index.php

    but if you are working at a temporary URL, it can be a bit strange and may look more like these: 

    http://asitedomain.pmhclients.com
    http://subdomain.hostingcompany.com/~0001/index.php
    https://www.hostingcompany.net:8443/sitepreview/http/mydomainlcom/index.php
    Make sure you know exactly what your URL is.

  7. Create a Site Map Before You Configure eeSiteKit: This doesn’t have to be set in stone, but you should have a plan for your site map as it can save you hours in development time. It could look as simple as this example below showing the top level and sub-navigation plan. eeSiteKit allows you to change sub-navigation on the fly. Changing a top-level navigation name will require a few extra steps though, so if you can decide on these ahead of time you’ll have a lot more fun creating your new website.

    Sample Sitemap:

    • Home
    • About Us
      • Our History
      • Our Team
      • Contact Us
      • Locations

    • Services

      • Free Consultation
      • Package One
      • Package Two
      • Package Gold
  8. Take Notes: Seriously. There are a couple dozen new concepts and details that you’ll want to become familiar with when working with eeSiteKit, and taking notes from the beginning will help you get up-to-speed faster.
  9. Read The Friendly Manual (RTFM): Even experienced EE developers will likely find that eeSiteKit handles a few things differently than they expect. Savvy folks will read this user guide and be glad they did.
  10. Recommended: Caffeinated beverage and some dedicated time in a space free of external distractions.