From: Alyssa Ross <alyssa.ross@unikie.com>
To: Jenni Nikolaenko <evgeniia.nikolaenko@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH v4] Docs: new structure
Date: Tue, 8 Nov 2022 18:33:36 +0000 [thread overview]
Message-ID: <20221108183336.lypr2oiqlxrzdafy@x220> (raw)
In-Reply-To: <20221108145228.21188-1-evgeniia.nikolaenko@unikie.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Tue, Nov 08, 2022 at 04:52:28PM +0200, Jenni Nikolaenko wrote:
> Create separate folders for new parent pages, update Introduction page,
> remove a and the articles from titles, quick check text for simple english
>
> Signed-off-by: Jenni Nikolaenko <evgeniia.nikolaenko@unikie.com>
> ---
Applied, thank you so much for your effort and persistence!
Something I'm thinking about now as follow-up:
Both of the topics in the new Appendices section are development
topics, so I think it would make sense for them to be in the
Development section. But I'm not sure whether they should go
directly under development, or whether it would be better to have
some sort of subcategory or subcategories so keep the most useful
information the most visible, so it doesn't get lost among niche
information like the UUID reference. But maybe using the nav_order
to keep the most useful stuff at the top would be fine? I'd be
very interested in your thoughts.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-08 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 14:52 Jenni Nikolaenko
2022-11-08 14:57 ` Jenni Nikolaenko
2022-11-08 18:33 ` Alyssa Ross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221108183336.lypr2oiqlxrzdafy@x220 \
--to=alyssa.ross@unikie.com \
--cc=devel@spectrum-os.org \
--cc=evgeniia.nikolaenko@unikie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).