A01 chaf6542 06 se fm indd

Here were our implementation decisions:

Integration with LDAP and use of NTLM for automatic 

single sign-on is essential. We even hacked some-

one’s starting point and open sourced our improved 

version.

Rich text editing must be available and as  Word-  like 

as possible.

Users like hierarchy and structure, the Wiki should not 

feel disorganised or completely  free-  form. (Confluence 

supports this with an exact page hierarchy capability.)

Sacrifice power and flexibility for simplicity. For 

example, our page design is fixed into a title, alpha-

betical list of subpages, page content, alphabetical 

list of attachments. While it would be nice to be able 

to change this at times, or order the attachments, or 

change the look and feel, it’s far more important that 

everyone can contribute and clearly understands how 

things work.

Remove as many unnecessary features as possible. 

For example, labels are a great idea, but we already 

have hierarchy and most users don’t really know what 

labels are.

M10_CHAF6542_06_SE_C10.indd   508

7/22/14   1:28 AM

---

509