The reasoning totally makes sense to me. Honestly just having a good central place with links to documentation for the RIPE (NCC) services would solve the issue I had.
-Cynthia On Mon, Jul 18, 2022, 09:39 Edward Shryane <[email protected]> wrote: > Hi Cynthia, > > Thanks for your feedback, > > > On 15 Jul 2022, at 17:12, Cynthia Revström <[email protected]> wrote: > > > > This looks great! > > > > I just have one small question, why did you choose to have it on > > apps.db.ripe.net instead of some more general RIPE (NCC) services > > documentation thing to have it all in one place? > > We co-host the DB documentation with the DB application because they > belong together (the documentation also linked from the left-hand menu of > the application), and it's easier for the DB team to keep updated (we can > deploy changes ourselves with the application). > > > I think it was RIS or Atlas that I saw that have this same style of > > docs so to me it would make some sense to collect it all in one easy > > to find place. > > You are correct, the other applications do use the same relative location > (/docs/) for consistency. > > > > > It is not like it matters much and this is still very good but I just > > know that earlier I have sometimes had a bit of a difficult time > > navigating to the documentation for various RIPE (NCC) services. > > > > I will discuss internally how to make all RIPE NCC services documentation > accessible from one place (and easier to find). > > The DB documentation will continue to be linked from "Database Support" on > the main website: https://www.ripe.net/manage-ips-and-asns/db/support > > > Regardless, great job DB team! > > > > -Cynthia > > > > Thank you! > > Regards > Ed Shryane > RIPE NCC > > >
-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
