On 01-07-2020 18:59, Mark Rotteveel wrote:
>
> A large table of contents that covers everything will only overwhelm. I think
> a short list of the documentation with a short
> summary of the subjects covered would be better than a cross-document
> table-of-contents.
>
> But I also think that
Branch: refs/heads/master
Home: https://github.com/FirebirdSQL/firebird-documentation
Commit: 23670c6d3b2974565e501a62278ff9703ed7c8b1
https://github.com/FirebirdSQL/firebird-documentation/commit/23670c6d3b2974565e501a62278ff9703ed7c8b1
Author: Martin Köditz
Date: 2020-07-01
On 01-07-2020 18:43, Köditz, Martin wrote:
I think a large table of contents makes sense. Even I find it difficult
to find documents sometimes. How should a newcomer know in which area a
document is or that it exists at all.
That's why I prefer a single large table of contents.
A large
Branch: refs/heads/master
Home: https://github.com/FirebirdSQL/firebird-documentation
Commit: 2bb1540c17ca4523144124d7a9c6e5b89f1ffd6a
https://github.com/FirebirdSQL/firebird-documentation/commit/2bb1540c17ca4523144124d7a9c6e5b89f1ffd6a
Author: Mark Rotteveel
Date: 2020-07-01
Hello,
I think a large table of contents makes sense. Even I find it difficult to find
documents sometimes. How should a newcomer know in which area a document is or
that it exists at all.
That's why I prefer a single large table of contents.
Regards
Martin
Hello,
I support the idea of the single Page list/index for all docs.
I suggest that we should create such page, and then ask people about their
opinion (it will also increase awareness of documentation).
Regards,
Alexey Kovyazin
ср, 1 июл. 2020 г., 16:31 Paul Vinkenoog :
> Mark Rotteveel
Branch: refs/heads/master
Home: https://github.com/FirebirdSQL/firebird-documentation
Commit: d07fd69be29e427f5ecc742ecfcd2877c74923db
https://github.com/FirebirdSQL/firebird-documentation/commit/d07fd69be29e427f5ecc742ecfcd2877c74923db
Author: Martin Köditz
Date: 2020-07-01
Mark Rotteveel wrote:
> I migrated the Firebird File and Metadata Security document.
(...)
> I do wonder if this document really belongs under 'Reference Manuals', I
> think it would be more suitable under White Papers & Presentations..
I think the whole categorization is seriously flawed.
