Stream: IG creation
Topic: artifacts page
Osaid Nabulsi (Dec 07 2021 at 08:36):
Dears, I notice that every time I generated the web ig the page "artifacts.html" is auto generated and contained all of (Profiles, Extensions, Examples, ValueSets and CodeSystem), but I do not need all of these to be in the same page (I need to separate them in multiple pages), could you help me in identify how the "artifacts.html" page is built, and how could I change on it (or at least choose what to aartifacts I need to be built in it) ?
Lloyd McKenzie (Dec 07 2021 at 14:08):
It's built using XSLT as part of the generic template. The only way to change it is to modify the template (which would mean you couldn't use HL7's continuous integration build). We've discussed leveraging Composition to allow defining alternative organizations of the content. Your other choice is to define your own page(s) that list only the artifacts you care about and don't bother linking to the artifacts.html page at all. (That said, you should provide a way to easily navigate to all of the artifacts in your IG.)
Sheila Connelly (Mar 01 2022 at 14:46):
Thank you Osaid and Lloyd. I have this same question. I also want to separate artifacts into multiple pages. Since the artifacts are generated automatically, if I create separate pages, how do I indicate that I want ValueSets to generate on this page, and Profiles on this other page. etc.
Did you solve this @Osaid Nabulsi ?
I was going to ask @Jose Costa Teixeira and then found this chat on the topic. Jose, do you have any instruction to share about this? (I stepped thru, at a slow pace, your recorded DevDays demo of the Belgian IG template. Thank you for that. So helpful.)
Lloyd McKenzie (Mar 01 2022 at 14:57):
There's a longer-term plan to allow doing this using Composition, but no timeline to get there yet.
Jose Costa Teixeira (Mar 01 2022 at 15:00):
Indeed. Allowing the artifacts page to be split - or tabbed - would mean some serious hacking to make your own XSLT (and maintain it, and have nobody to complain to). There was some discussion on reworking this so that the editor has a bit more control over the grouping and paging (with a Composition).
Jose Costa Teixeira (Mar 01 2022 at 15:00):
The latter would need the thing that powers the community: Some time
And upvotes. Two things
Jose Costa Teixeira (Mar 01 2022 at 15:01):
(Perhaps three things: Time, upvotes and enough chocolate :) )
Eric Haas (Mar 01 2022 at 15:35):
What I do is either :
- create direct links to the anchors in the FHIR artifacts page in menu bar like here: http://build.fhir.org/ig/HL7/VhDir/
- create my own pages and ignore the artifacts page like here: http://build.fhir.org/ig/HL7/US-Core/ - it is still reachable via the breadcrumbs and TOC
John Moehrke (Mar 01 2022 at 15:39):
i tend to treat the artifacts page like a glossary. Figuring that my narrative pages need to be pointing at the most important artifacts; such that only those most familiar with the IG scope/purpose/intent will use the artifacts page. in this way the current artifacts page is functional, and having it be automatically generated and complete is useful.
Last updated: Apr 12 2022 at 19:14 UTC
