TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Product X Developer's Kit <download installer> <Release Notes>
<Programmer's Guide> (API reference is included with installer)
...
On Wed, Nov 9, 2016 at 6:05 AM, Kelly <kparr888 -at- gmail -dot- com> wrote:
> The marketing director where I work wants to put documentation (HTML only) and product downloads on a single page.
> Our downloads page is fairly detailed and divides links to resources by:
> - Binary downloads
> - Open source downloads
> - Packages
> It also points to the documentation landing page, which contains links to docs for 3 in-market releases.
> This setup is simple, easy to find, and no users have complained.
> Also, this division of resources (docs/downloads) is what I've experienced in > 15 years of tech writing.
> Given I have no experience with the pros and cons, I I feel at a disadvantage and want to make an informed decision in case I need to push back at Marketing. I was unable to find examples online of companies that combine the two.
>
> I'm hoping this group has opinions on combining docs/downloads into one page.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
