Intro
The following list of pros and cons are personal and written from a user view, not administration side. This list might be usefull on deciding what to use
SnipSnap for and if the use of
SnipSnap really fits your needs.
SnipSnap is not a document storage for exsting documents, it rather can be used to collect and share pinboard like notes. It also is nice for documenting a piece of software and also for propagating the support for it.
Pro
As blog
- configurable weblog ping
- mail-to-blog
- calendar macro
As CMS and generally
- post news (blog)
- css use ease adaption of own layout
- macros. Simple way to extend the possibilites.
- table macro
- code macro to display code blocks
- easy syntax, great outcome
- direct edit and easy linking (no extra tool needed)
- image (attachment) support
- javadoc support
- sniplinks
- powerful fulltext search
- commenting of snips
- user management (guest, user, editor)
- snip locking for editors
- fast updating enables better user acception
- recently changed feature (also changed snips since last login)
- index feature
Contra
editors could accidently delete snips (zap!) FIXED
- simple user management (no groups)
- limitations on layout and editing possibilites
requires css capable browser (mozilla works fine) NO PROBLEM
no history FIXED
- no html support
- no view access restriction
- (no commercial support: nobody to blame for on failures)