Configuring The Default CSS
eeSiteKit’s default CSS is all located in the “kit_css” template group.
The templates within the kit_css group are divided into two sections. Those specific to eeSiteKit and those that are part of the YAML system. Each section is named with a “kit_” or “yaml_” prefix.
To get your default CSS working on your site, you’ll need to set a few paths by hand.
- Open the “kit_css/index” template and add your URL to the path settings
- For the IE browsers, there are two more paths you’ll need to configure in the “kit_css/kit_ie_repair” template.
- Pay attention to the order of the path settings in the “kit_css/index” template. If you change that order, your site display may break.
Why include default CSS at all?: Three reasons. One is that its easier for many people to learn a complex system when they have a fully functional model to study. We feel you’ll learn eeSiteKit faster if you have a working example you can study, play with, break, fix and disassemble.
Secondly, we believe that the YAML CSS system has a lot going for it and that just about anyone creating great websites would benefit from taking a look at it within EE’s template system. The YAML examples at its site all deal with how to set it up externally in files, so we believe that seeing it set up within EE’s templates gives developers more options.
Finally, having a default set of CSS allows us to install and set up a basic CMS website in eeSiteKit in about an hour. This allows us to start training our own clients on how to publish, create, edit and position pages at the very beginning of a project. This gives our clients something tangible and important to do while we’re working on the artwork, it also educates them to a level of understanding that enables them to make more informed decisions during development. In our business model at NetRaising, our clients create the site pages and publish 90% of the content. By having a working website from day one of the project, we get content published even before the artwork is ready and this cuts our development schedule by about a third, getting us from start to launch faster than our competitors.