About Tiki Profiles
TikiWiki has a lot of
features and can be used in a very wide range of
use cases. However, configuring TikiWiki can be very long and complex due to the numerous amount of options. "Sensible defaults" are not the same for a Corporate Intranet than a public Wiki.
Profiles will solve this problem partially by allowing to configure sets of options at once and build base configurations.
This website will be used as the documentation center for profiles and as a primary repository for TikiWiki experts to share their experience and collaborate on default configurations.
How it Works
Each profile is a configuration patch that can be applied on top of any TikiWiki installation. Profiles will allow to change configurations in a TikiWiki installation and create various objects. At this time, the exact object types that will be available is not defined. The objective would be to make all objects accessible, but this may take a significant amount of time.
Features
- Can be not only at install, but on an existing installation.
- Thus, profiles can be combined (the last one installed overrides any conflicting settings)
- Can handle
- Any of over 600 preferences (features & settings)
- Groups & permissions
- Modules
- Menus
- Categories
- Sample data (like content packs) & additional configurations for
- Wiki
- Trackers
- File Gallery
How To Use Profiles
How To Use Profiles - on your site.
Easy!
How to Create Profiles - on this site.
Harder!
Profiles for developers
Please help us improve this system.
Developer Documentation for Tiki Profiles
Todo
Technical
- After I install a profile I should be able to be sent to a URL
- For example, a wiki page (which I presumably just created), with the next steps to follow.
- Add missing handlers as we need them in an attempt to support all of TikiWiki's data types.
Non technical
Nice to have
- The possibility to ask for data which is to be used as variables in the profile (Something interactive)
- Ex.: ask the person for a username and the wizard-like thingy uses this information to put them in the Admins group.
- The Wizard asks the name of the blog
- The Wizard asks if you want A or B. This would permit simple variants to a profile without forking it.
- A list/log of loaded profiles locally in the Profiles Admin page.
- something on this site that verifies whether a profile works or not?
Once you have installed a profile you can't install again (even if profile has improved and you may have deleted the stuff created by the profile). Maybe an override option would be good. Done
Multiple YAML sections per page, to facilitate readability Done
- To be able to remove modules (ex.: remove login)
Additional settings for groups, like
- Group Homepage
- Users Information Tracker (should be variables of newly created groups, needed for User Trackers)
- Users Information Tracker Fields (should be variables of newly created groups)
- User can assign to the group himself
Questions
- In tiki-admin.php?page=profiles, should the profile field be a drop-down?