Glad to hear it.<p>Here&#x27;s some bullet point thoughts:
1) Workflow needs to be uber-fast and not require saving&#x2F;naming the images (at least at the user level, the program will of course). Many images are screen shots from SW installs. Workflow goes: Run SW in VM-&gt; screenshot portion of interest -&gt; Copy+Paste into word doc. I never even save the image in that case. The rest of the images are photos of HW. I just want to drag and drop into the document, not rename them all and move them to a same folder with the document. The document&#x2F;CMS&#x2F;program should take care of that all for me (like Word does).<p>2) I do need the text and images to match better and be more WYSIWYG. Location is more important than aesthetics for a guide.  It cannot be the abomination that LaTeX is. LaTeX figures are terrible to work with (and that&#x27;s having published multiple academic papers + PhD thesis in LaTeX). Sizing is less important (that can be [width=x, height=y]).<p>3) Variables&#x2F;snippets: Libraries of text snippets and variables is what we do quite a bit of. Right now with a few kludged together macros and custom Word doc properties. Lots of docs go &quot;Run the &lt;SW install name&gt; for &lt;device&gt;&quot; with &lt;&gt; items defined at document level. Sounds like you do this, and it&#x27;s probably better than how word does :)<p>sorry for dumping on ya, but I&#x27;m excited to find people working in this space. It&#x27;s something I feel like there should be better tools for but just haven&#x27;t found yet.