Shibboleth Developers

["RL 'Bob' Morgan" <>]

On Wed, 30 Apr 2003, Nate Klingenstein wrote:

> In an effort to make Shibboleth's deploy guides as user-friendly as
> possible over the next few weeks, I'd like to collect feedback on using
> a front-end to the deploy guides to simplify things for users.  This
> would essentially filter the information in the guides based on what
> the user's needs are, and possibly point them towards different
> tarballs, and so forth, allowing for simpler documentation for most
> people.  This is not an approach I've seen taken anywhere else --
> though I'm not particularly worldly about documentation -- so I'd like
> to hear any alternate ideas as well.
>
> Check out the mock-up at http://204.144.238.122/shibindex.html.

I think we have general agreement that the docs need to be broken up into
smaller bits and support multiple paths through them, so this is on the
right track.  I'm kinda skeptical about this custom-build approach though,
since docs should be available both bundled with the package code and
online from the web site.  Seems like a more traditional approach with a
table of contents and hyperlinked chapters would be at least as effective
and simpler to build.  Also, I think our direction should be to separate
Shib docs from InCommon docs; your approach seems to link them together in
the build process.

I think Walter was going to propose a doc structure?

 - RL "Bob"


------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--