Stream: IG creation
Topic: Artifacts page is empty
Jose Costa Teixeira (May 24 2018 at 20:36):
I cannot render the page that shows the artifacts - structureDefinitions, CapabilityStatements...
Can someone please point me at a working example (source) so that I can see what I am missing?
Grahame Grieve (May 24 2018 at 20:38):
well, typically, there's a page you create with an include that includes one of the generated lists
Jose Costa Teixeira (May 24 2018 at 21:01):
ok saw it. It's generated in the same set f xslts indeed.
Jose Costa Teixeira (May 24 2018 at 21:19):
@Lloyd McKenzie i am updating the sdc2 xslts to support the new implementationGuide structure. i assume you haven't done that exercise
Grahame Grieve (May 24 2018 at 21:29):
I haven't yet rejigged the IG publisher to use the new IG instead of the json file. probably next week
Lloyd McKenzie (May 24 2018 at 22:12):
@Jose Costa Teixeira Hadn't gotten around to that one yet, so feel free. There'll be a whole lot more rejigging when Grahame is done support for the new IG structure. I'm hoping that @Eric Haas and I can agree on a common framework design that we need for DaVinci and that we can then roll that out across the various HL7 IGs too - SDC, Gemonics, US Core, etc.
Grahame Grieve (May 24 2018 at 22:32):
I want that ASAP for my own stuff
Eric Haas (May 24 2018 at 23:20):
IG-Template2 -which is the latest and greatest version of the USCore framework is my candidate. What parts of that need to be addressed. You can switch on and off feature with status codes (tabs) and front matter (to top arrow, section numbering). All in kramdown markdown ( which means html too ), liquid, and bootstrap. Easy to customize menus, images, logos, accordian style content, add your own css.
My issues:
- I have is not being able to turn off and what gets injected into the profiles (intro, summary, search) without changing the FrontMatter in sd.html so that part is clunky and so I create the includes out of the box to prevent build failure.
- I do think the css could use a an upgrade especially ##### and ######,
- I tried to put the TOC in the left margin but gave up. (the menu must stay on top since that is FHIR defined real estate.)
- Being able to generate a TOC across pages from the published output instead creating before hand would be fantastic.
- Figure how to develop the history and change logs in the IG but publish separately ( GG gets grumpy because I always stick em in there )
- My ultimante is goal is to inject swagger/openapi content inline and be able to run something like a postman collection right from the IG.
- generate python models dynamically ;-)
Grahame Grieve (May 24 2018 at 23:26):
"GG gets grumpy" - not really. I just mantain them manually so I'll just rip the content. but at least you have a history this way
Grahame Grieve (May 24 2018 at 23:26):
"My ultimante is goal is to inject swagger/openapi content inline " - everything I can imagine this already means is done
Eric Haas (May 24 2018 at 23:31):
the accordion stuff and other goodies like an intermediate profiles are here: https://argonautproject.github.io/clinicalnotes/guidance.html
Eric Haas (May 24 2018 at 23:33):
I know and I have not had a chance to try it out but here is what I would like https://developers.zomato.com/documentation
Eric Haas (May 24 2018 at 23:33):
except that means less markdown and more capability statements ugh (My least favorite part of ig publishing)
Grahame Grieve (May 24 2018 at 23:34):
ok I generate openAPI documents, but not stuff like that
Eric Haas (May 24 2018 at 23:35):
I have no idea how its done.
Eric Haas (May 24 2018 at 23:35):
But is for the future
Eric Haas (May 24 2018 at 23:37):
Can you hide inline examples using the accordian folding for HL7 igs?
Eric Haas (May 24 2018 at 23:38):
The python thing was a joke btw
Grahame Grieve (May 24 2018 at 23:46):
the publication requirements for HL7 IGs are here:
Grahame Grieve (May 24 2018 at 23:47):
http://wiki.hl7.org/index.php?title=FHIR_Implementation_Guide_Publishing_Requirements - the relevant text is:
Grahame Grieve (May 24 2018 at 23:47):
implementation guides should present information to the user such that by default, nothing is hidden unless there are clearly defined tabs for changing views
Jose Costa Teixeira (May 25 2018 at 06:05):
So.
much.
weekend.
fun.
Jose Costa Teixeira (May 25 2018 at 06:05):
@Eric Haas I will look at that also. At this moment I am lookng for a simple way to publish already-available conformance resources in IHE.
Jose Costa Teixeira (May 25 2018 at 06:07):
but my goal is to have the rest of content. I like the swagger ui stuff.
Jose Costa Teixeira (May 25 2018 at 11:01):
I have updated the xslts from Lloyd:
1. igToConfig adds the license from the IG to the config file
2. CreateArtifactSummary has been updated to reflect the new disposition of resources and packages in the new IG resource.
Jose Costa Teixeira (May 25 2018 at 11:03):
I don't know if this should be somewhere on github.
ATM they are art of my sandbox but that is for IHE experiments.
Last updated: Apr 12 2022 at 19:14 UTC
