Giter VIP home page Giter VIP logo

ihe-ig-template's People

Contributors

costateixeira avatar grahamegrieve avatar johnmoehrke avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

Forkers

rrapio

ihe-ig-template's Issues

Define the feedback mechanism for Profiles

HL7 has Jira, so it is possible to have a link "provide feedback on this section".
We currently have a link at the bottom that sends the reader to the CP process, presumably that could also be made leaner

Update logos

Add logo with Registered mark and transparent background

history page not clear

There seems to be some support for a history page in the footer of the template. I would be happy to support this, but I have no idea what it is looking for. I think this is similar to the HL7 IG, where the historic versions of the IG are available to the user.

I think we should have a discussion about this in IHE, as we tend to only support the formal publication. pointing at the current build may not be bad. But we tend to hide our past revisions in an archive. These are maintained, but not easily accessible. This process is based on IHE governance that a profile version is not important, once a profile goes normative (Final Text) it can not be revised in a breaking way. We can add options. But if we need a totally new solution we must start a new Profile. Not clear we must maintain this process. Hence the need for discussion, and discussion that likely needs to go up many levels if we don't maintain current process.

IHE Template to not number headers

may be a second template used in IHE, where the numbering is dictated by the Technical Framework (RAD, IHE, PCC, QRPH). These domains can use this template that will NOT automatically assign header numbers. Thus these IG using this template will need to manually assign header numbers in the header text. (This is how we do this in WORD today. This is necessary because we use volumes, and assigned chapters).

change footer from CC0 to CC-By-4.0 license

The IHE-FHIR workgroup agreed today to recommend CC-By-4.0 license as the default license for IHE github repo and for IHE published IG.
When the ihe-ig-template does not have a license recommendation it should assume CC-By-4.0 rather the CC0.

Update colors

Color PMS RGB Hex
Dark purple 2695 46 26 71 2E1A47
Light purple 266 117 59 189 753BBD

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.