T
Tim Hutchens
Guest
dmicozzi , HTML delivery is fine - this has been the case for a number of releases now. But you also used to provide links to download the HTML docs for offline/local reading. It sounds like you have moved the docs out of a statically written HTML site and into a Content Management System. If so, I'm pretty sure you won't be able to offer a downloadable version of the HTML docs.This trade-off is probably giving you excellent content indexing for searching, but that's not what we want most. I think most of the responses to this thread are ultimately saying that we are looking for a single hierarchical table of contents for the docs and the ability to view the docs locally/offline. It's less about HTML vs PDF. We would like a start.pdf for the PDF version like there used to be to provide the top level table of contents. For the online/HTML docs, we would also like a single table of contents that lists every article of the documentation set in its proper place in the hierarchy. The search-first strategy is good for finding isolated pieces of documentation (like finding the syntax reference for an ABL keyword). But we are looking for the book/manual that puts all the documentation in the context of the entire OpenEdge ecosystem. If you could merge the two, that would be a win-win. Previously, if you did a search in the online docs, it would list a set of search results. On clicking a result, it took you to the article AND showed where the article was in the left hand table of contents. If you could give us back the always-present table of contents, that would likely satisfy many of us. Two direct questions in response to your reply: 1) Instead of removing books that were out of date, shouldn't you update the book? 2) Where should we provide feedback on the OE Info Hub in general? The feedback links you mentioned seem to be for commenting on specific articles. See screenshot below. The community seems like the right place for this conversation.
Continue reading...
Continue reading...