A question (or three) about linking content between packages

Not sure what you mean by lose the /usr guide entirely?
Hitting the back button in Yelp should take you back to wherever you
were before, at least it does here.You can also simply provide a link
back within the page itself.
But honestly, I don't think that's going to work for you anyway.
If I understand correctly you would want to just be able to drop new
help files in and have them automatically show up.Ideally, all these
random help files from different places in the filesystem would then
get merged onto one page.
Am I right?
For that I think you're going to have to separate this into System and
User.
Then have a default index.page for each and some kind of standard
template for pages added.
You could have a separate "landing" page which describes each and links
to them  - then those could simply link back to that page.
Yes, this means random packages will be dropping package.page into a
shared directory and could get messy...
But as long as your template makes clear what is allowed and what isn't
it should be fine.
The alternative is some kind of service which scans and rewrites,
nevermind that sounds like a terrible idea already.
HTH
On Sat, 2019-05-04 at 14:55 +0100, Nathan Willis wrote:
> Hi list,
> 
> Thought I might try this again, see if I can catch a different set of
> eyes or something.
> 
> I'm trying to figure out how to link between a Help guide page
> provided by one package and individual pages provided separately.
> 
> My closest attempt was to install a guide page in /usr/share/help/
> and link in subsequent pages from .local/share/help/, but when I
> tried that, opening Yelp would _only_ show the .local page, and lose
> the /usr/ guide entirely.
> 
> I'm really not clear if this is breaking the spec, simply undefined
> behavior (and where), or a Yelp bug.
> 
> Anyone have thoughts?
> 
> Thanks,
> Nate
> 
> On Wed, Sep 5, 2018 at 11:44 PM Nathan Willis <
> nwillis at glyphography.com> wrote:
> > Hello Mallard Nation,
> > I'm rather new to designing Mallard books and I'm trying to spec
> > out a proposed project. So I've got a couple of questions I'm
> > hoping the community can educate me on.
> > The core idea is to add help (in the form of individual per-package 
> > topic pages) to a set of desktop Linux packages so that you could
> > visit the guide page and it will show you all the pages from
> > whichever individual packages you happen to have currently
> > installed.
> > ... 
> > 
> > As I understand it from the manual and a couple of tests, though, I
> > can't have a guide page (e.g., /usr/share/help/installed-system-
> > fonts/index.page) that automatically finds and links to HTML pages.
> > Is that correct? If so, is there some workaround worth exploring?
> > ...
> > The second wrinkle is that, ideally, we'd also be able to do the
> > equivalent for things installed in the user's home directory (that
> > being the use case for a font manager app as well as what you get
> > when downloading from Google Fonts and the like). So, if that user-
> > mode installer copies help files into ~/.local/share/help/fonts-
> > bar/ (from a downloaded .zip file, not via a distro package), what
> > would be the best way to pick that up in the same help guide?
> > ...But with some test files I played around with, I couldn't get
> > that to work at all. Specifically, launching yelp on that guide (as
> > above) shows only the ~/.local/ page, and drops the content in
> > /usr/share/ entirely. That was on a fresh Ubuntu 18.04 machine.
> > It's possible there's something funky going on that I just haven't
> > noticed yet, but I'm more concerned that I'm missing something
> > crucial in the fundamental topic/guide/page/HTML architecture. If
> > so, I'd certainly appreciate some help figuring out what it is.
> > 
> 
> 
> _______________________________________________mallard-list mailing 
> listmallard-list at projectmallard.org
> http://projectmallard.org/mailman/listinfo/mallard-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://projectmallard.org/pipermail/mallard-list/attachments/20190513/0439cf83/attachment.html>