slitaz-forge view forum/themes/slitaz/README.txt @ rev 1
Add slitaz themes for vanilla
| author | Eric Joseph-Alexandre <erjo@slitaz.org> |
|---|---|
| date | Wed Dec 22 10:36:12 2010 +0100 (2010-12-22) |
| parents | |
| children |
line source
1 How to create a theme:
3 Part 1: CSS / Design
4 ================================================================================
5 1. Copy this "default" theme folder and rename it to your new theme name.
6 2. Open the "about.php" file and edit the information to reflect your theme. Be
7 sure to change the array key like this: $ThemeInfo['YourThemeNameHere'].
8 3. Create a "design" subfolder and copy /applications/dashboard/design/style.css
9 and /applications/vanilla/design/vanilla.css into it.
10 4. Any background images you want to continue using (like the star png images
11 for bookmarking) should be copied along with their respective stylesheets.
12 5. Go to your Dashboard, Themes, and apply your new theme.
13 6. Edit the copied CSS files to look however you wish!
15 Other things you should know:
17 + All non-forum pages should be edited in the global "style.css" file.
19 + If you want to edit the look & feel of the administrative screens, also
20 copy /applications/dashboard/design/admin.css in step 3. Similarly, you can
21 copy other CSS files like /applications/vanilla/design/vanillaprofile.css to
22 customize those pages as well.
25 Part 2: HTML / Views
26 ================================================================================
27 If you want to customize the HTML, you can edit that too.
28 Our pages are made up of two parts:
30 1. Master Views - these represent everything that wraps the main content of the
31 page. If all you want to do is add a menu or banner above Vanilla, this is
32 all you need to alter. To do so, copy the default master view from
33 /applications/dashboard/views/default.master.php to
34 /themes/yourtheme/views/default.master.php and edit it there.
36 2. Views - these represent all of the content in each page. Every application
37 has a "views" folder that contains all of the HTML for every page. So, for
38 example, if you wanted to edit the HTML for the Discussions list, you could
39 copy the views from /applications/vanilla/views/discussions to
40 /themes/yourtheme/views/discussions and edit them there.
42 You can avoid naming conflicts between applications' views and specify which
43 app a view is for by optionally adding a subfolder with the app's name in
44 /themes/yourtheme/views/ (e.g.: /themes/yourtheme/views/appname/) and placing
45 views there rather than directly in the "views" folder.