I’ve created channels and categories but there’s no navigation showing up.
You may need to assign some entries to your categories before site navigation will display. eeSiteKit works to prevent broken links to empty pages, so it removes links with no content to display. In a brand new website, it can seem a little strange with no navigation displaying, but once your site goes live it make more sense, as eeSiteKit removes links to empty pages and sends search engines an visitors a proper 404.
Navigation will display as content is added to the site, giving everyone immediate feedback on what pages have been correctly created and what pages are still in need of content.
If you want to test the navigation for a channel before you get actual site content, create 2 entries, assign one to the “landing” category and one to a “category” below “landing”. Make sure one of the entries has some content added to the extended content field so you can also test the single-entry template. With just 2 entries you can then check your navigation and templates on the landing, category and single-entry templates of your site.
Seeing 404 page instead of home page.
You may need to publish an entry and assign it to the “home” channel’s “landing” category. eeSiteKit works to prevent blank pages and broken links to dead-end pages within your website. If there is no entry assigned to a page of your site, then eeSiteKit tries to display a 404/page not found.
In the channel called “home”, create an entry for your home page and assign it to the “landing” category within your “home” channel. This will give eeSiteKit some content to display on your home page and if everything else is set up correctly, will remove the 404.
Default CSS is not working; unformatted pages.
You may need to adjust the paths to your CSS files. There are file paths that require manual adjustment in two templates:
Site Name › Templates › Template Management › kit_css › index
Site Name › Templates › Template Management › kit_css › kit_ie_repair
EE doesn’t parse tags in templates with the type of “CSS Stylesheet, so these paths need to be adjusted manually for each site. Replace the default “asitedomain.com” with your site’s domain or temporary development URL and your CSS should start working for you.