Docs, Guides, and Recipes

There are a number of existing issues from version 1 where users are trying to add a custom tool but experiencing issues. We should revisit: How we configure the available tools When they're available for use Where they're located Contextually applying the above - IE. Does my tool work for active viewport? This may be a good discussion item for project week, and with @JamesAPetts

Our Embedded recipe is aimed at less technical users looking for a quick way to "drop-in" the viewer, or use it with no build step and only minimal config. We should frame it to target that audience, and to be as straightforward and hassle free as possible. > What I was expecting to see is something like "use from script tag" and a short <pre> section that had something like: // add config first // ... <div id="root"></div> //... <script src="https://unpkg.com/ohif-viewer@0.1.9/dist/index.umd.js" crossorigin></script> <script> var Viewer = window.OHIFStandaloneViewer.App; var app = React.createElement(Viewer, window.config, null); ReactDOM.render(app, document.getElementById("root")); </script> Feedback from Steve Pieper

Add documentation for sopClassHandler in Extensions . Usage can be found in createStacks in ohif-core

Add diagram to "Extensions" readme to explain where they fit in to the larger picture