Thanks for the feedback. Sticky view selection is in the backlog to be done soon. 

Thanks for the feedback. I'll see what we can do with this.

Yes, sorry I missed that in the release notes and I will add that now. I had hoped for the "redesigned HTML email" feature to make it in but the timing wasn't right so we settled for just taking the existing template to HTML. We have some changes planned on this for the June 17th release pending completion of some higher-priority items.

Interesting observation, thanks. So if the user is looking at the contents of a book, but in the left pane chooses Back, leave that book content visible until they choose something else?

Yes, this is using the same DOCBOOK content. We just put a different UI on top of it.

Thanks for the feedback. I'll see if we can do some kind of "copy link" icon at the book/section level to make it easier to reference a particular section of the content.

Thanks for the feedback. Yes, we will add filtering capabilities to narrow your results.

We recognize there's a need for a class reference, so don't worry, it's not going away. The question is about functionality and completeness of the current class reference utility so there may be some refactoring in addition to changing the UI skin. There's some internal discussion about how it works and the way the information there is obtained. They'll be more on this in the next few weeks.

Thanks for the feedback. I didn't see the large right padding on the iPhone or an Android tablet but maybe something changed. We'll check that out and the other comments.

Class reference styling will come soon, pending some debate on the usefulness and functionality of the class reference itself.

Thank you. Last minute decision to deploy to docs.intersystems.com/beta vs. a completely different alias throws off those references which need to be relative to the root. We'll fix this on that landing page.

Mike - thanks for the comment. The stand-alone documentation is being reworked, first with a new UI and then with a new search engine. In the meantime you have two other options for searching documentation that didn't exist a few months ago, or were not that effective.

1. Use Google - we've cleaned up (most) of the old documentation references and fed Google's crawlers what they need to index the documentation properly. Example: site:docs.intersystems.com ensemble HL7

2. Use Developer Community's search and then select Product Documentation to narrow the results. All of the documentation is indexed here.

As for the code samples inline with the documentation, this is great feedback and something we will put some focus on.

Hi Randy,

This is just the start and we will be adding new filtering capabilities to the online documentation once we release the new UI. Also, we probably haven't done a great job of advertising the fact that the product documentation is in Developer Community and searchable. 

- click on search

- in the search box type in a keyword or phrase, let's try "web service" (without quotes)

- you will then see the search results, along with a selection widget labeled "tags". You can open this and add a constraint to the results. In this case you can select "Ensemble", which will include the child tags under it.

- the results will be refined to only include those tagged with "Ensemble" (and it's children)

- you can also use the Categories filter to choose "Product Documentation" to only see the documentation rather than everything on the site.

Great, thanks for the quick response.