Back to swiftlet.org | To report bugs, please use the issue tracker at GitHub.
I made the CSS as modular as possible, you can just remove the #header, #content and #footer sections or rename the ids in the HTML. I don't want to split up the CSS because this way it's easier to find things and saves HTTP requests. I don't consider the layout for notices, form, tables etc. to be essential, many users will want to change that as well.
A little later, and perhaps a little smarter, I found out, that the Issue i had here, had nothing to do with the design itself, but with the fact that once you put you're own css file over it, all swiftlets design is kinda broken. Now an way 2 easy fix is the following : in _view/header.html.php
<?php if ( $contr->inAdmin ): ?>
<?php else: ?>
<?php endif ?>
good example of being noob. :D
Ye, I made CSS for my front website, while using swiftlet for the back-end, swiflets css is really cool, but 2 css files together is almost instant fail. (for me) so I searched for a way to remain swiftlet and my design. Now I found a "slow" way by making a inAdmin switch in de header and footer file. However, I don't like the solution as it slows my site (i know just a little), w/o an advantage for visitors.
I know there must be a way to switch the admin header, but then again, I'm not so very pro on the plugins topic.
It looks like you're new here. If you want to get involved, click one of these buttons!