You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we have some links under docs/public that refer to files in the docs/internal. For each one of these we need to make up our minds on whether the linked information is public or not. If yes, the document (or part of it) should be moved into docs/public. If not, we should stop linking to it from documents under docs/public.
This command lists all public documents that link to internal documents.
grep -l -R docs/internal docs/public
The text was updated successfully, but these errors were encountered:
Your grep command returned nothing, but the following returns 8 links:
grep -R ../internal docs/public
I disagree on "stop linking to internal documents from public documents" if it is meant to mean never.
"Internal documents" are really not internal. Maybe we should call it something else. Those are documents that people outside the work group rarely need.
"Public" is not a good choice either. Maybe we should call it something else.
The "internal" documents that are linked to from the Public document tree should be reviewed and maybe moved to the Public tree.
The compilation of the Public document tree by mdbook has a limitation that relative links from document in the Public tree to a document inside this repository (zonemaster/zonemaster) but outside the Public tree do not work. A work-around is to use absolute link for those. That also applies to links documents in "test-zone-data"
Today we have some links under
docs/public
that refer to files in thedocs/internal
. For each one of these we need to make up our minds on whether the linked information is public or not. If yes, the document (or part of it) should be moved intodocs/public
. If not, we should stop linking to it from documents underdocs/public
.This command lists all public documents that link to internal documents.
The text was updated successfully, but these errors were encountered: