My approach to solve this issue is to generate a NarrativeWeb report.
The “main” computer is used for data entry with Gramps. This is the only computer allowed to access the Gramps DB, notably because SQLite in general does not provide features to lock the DB between multiple users. Additionally, inside Gramps, it is extremely difficult to determine which DB records should be locked for write access while a Gramps “object” is edited (a Gramps “composite object” corresponds to several DB records). For all these and other reasons, I consider Gramps as the entry tool, not the display/browsing tool. Regarding tree browsing, I consider Gramps is not really user-friendly for casual visitors. It is rather technically-oriented, meaning it facilitates management of the various “contributions” (notes, citations, …) for a person or family.
I configured a dedicated genealogical server on the computer using NarrativeWeb report as data source. Then my family can connect to this server to browse the tree. The pages offer a consolidated view for a person, family, place where all relevant information is collected and aggregated in a stand-alone exhaustive “article”.
For convenience, I added several modified (clickable) family lines graphs to show various parts of the “extended” family with links to person and family pages. This allows a more “intuitive” navigation.