Concerning the actual contents of a documentation system, I suppose a
framework might be composed of templates for:
1. Command syntax quick reference - fossil help ?cmd?
2. Command detailed reference
3. Cookbook-like containing "recipes" for various scenarios
4. Overview
4a. System introduction
On 10/11/2016 08:31 PM, Ron W wrote:
> Sounds like something Google Docs does or could easily do (at least in
> Google docs for Business).
I'm not familiar with any recent incarnation of Google Docs. A quick
glance at my white board and I see four loops of interaction with the
documentation system
On Tue, Oct 11, 2016 at 6:19 PM, Adam Jensen wrote:
> On 10/11/2016 03:39 PM, jungle Boogie wrote:
> > I would call that a wiki, not only inside fossil-scm but in general.
>
> I am inclined to think that a wiki probably isn't sufficient for many
> projects. What I am casually proposing (just brai
On Tue, Oct 11, 2016 at 6:19 PM, Adam Jensen wrote:
> On 10/11/2016 03:39 PM, jungle Boogie wrote:
> > I would call that a wiki, not only inside fossil-scm but in general.
>
> I am inclined to think that a wiki probably isn't sufficient for many
> projects. What I am casually proposing (just brai
On 10/11/2016 03:39 PM, jungle Boogie wrote:
> I would call that a wiki, not only inside fossil-scm but in general.
I am inclined to think that a wiki probably isn't sufficient for many
projects. What I am casually proposing (just brainstorming, really) is a
documentation framework that supports s
On 11 October 2016 at 12:12, Adam Jensen wrote:
> If a documentation framework included an interface that would enable
> users to provide feedback in a variety of ways (e.g., annotations,
> comments, ratings, etc.) that might be useful information.
I would call that a wiki, not only inside fossil
Here's an idea that might be a little complicated to describe:
Every time a [potential] user interacts with the documentation there is
human attention, intelligence, and effort that is engaging the system.
What if the system were designed to harness some of that?
If a documentation framework incl
Given the vast technical resources that are available (and becoming
available), documentation creation and refinement seems like a keystone
technology. Dedicating weeks or months to evaluate a piece of technology
is increasingly becoming a less viable practice. It's something that
I've thought abou
8 matches
Mail list logo
