Hi,
so far I only have experience with documentation written in AOO itself.
I've been experimenting with Markdown and Pandoc from time to time, and
wasn't always happy with the results and the possibilities. An amount of
time that I was not willing to give. And even now I don't have the time
to go deeper into it. The maximum what I can do beside my other tasks is
to cooperate in the creation of the documentation.
Since this is supposed to be about the documentation, I consider the
tool for this to be of secondary importance. We have AOO. We can write
the documentation with it or update existing documentation with it.
There's certainly nothing to be said against converting the results into
another format later using Docbook (which I only looked some Minutes at)
or Pandoc.
However, I'm thinking about the people who want to work on the
documentation. I don't have any experience here, so I don't know how
many people want to or can work on it. Is there a plan? Maybe there are
some who read this and ask themselves the same questions. Apart from the
tools, this seems to me to be an important topic. Has it perhaps been
discussed before? I haven't found anything current on the AOO website.
For a task like documentation I think an organization is necessary.
Wouldn't it be fatal if, for example, three different people were to
write about a topic without knowing about each other? One person uses
AOO with templates, another person writes in a simple text editor.
--
Regards
Detlef
Translated with www.DeepL.com/Translator (free version)
Am 03.06.2020 um 15:11 schrieb Keith N. McKenna:
On 5/30/2020 8:41 PM, Keith N. McKenna wrote:
I should probably have my head examined but I am thinking of one more
time trying to revive the documentation effort for AOO. One of the
drawbacks is that most people that have started to help have left as
there has been very limited availability of mentoring. I do not see this
changing but I am hoping that by defining a new process we can reduce
the dependency on mentoring.
One idea for this would require that the MediaWiki extension be made
functional again. This would allow for using Writer to create the source
which could be stored in the git repository and then be transferred to
the mwiki for easy online access. By storing the source in the
repository it would give us better revision control over the
documentation. Plus it may help relieve the mentoring problem as many
more people are familiar with using Writer.
Another would be to use Docbook, though this is not as appealing as I
have no familiarity with it and it appears that there is a steep
learning curve to its use and that would be a disadvantage to attracting
new people.
I look forward to any other suggestions that could move this effort
along as it has languished for far to long.
Regards
Keith
AS part of this effort I am working on a document laying out What I see
as the need for this project and a number of alternatives that could be
used to to address those needs. Once completed I will share it both here
and on doc@for more comments and suggestions.
Thanks to all who have responded for there time and suggestions
Regards
Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
