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.
Subject:Re: newsletter approaches From:Sean Wheller <sean -at- inwords -dot- co -dot- za> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Mon, 8 Jan 2007 09:45:52 +0200
On Monday 08 January 2007 09:40, Erika Yanovich wrote:
> We are sending an HTML e-newsletter to our customers which includes
> contents exclusively created for the newsletter (cannot be found on our
> website as articles). However, the entire newsletter archive can be
> found on the site. Since the newsletter editor is on maternity leave,
> I'm getting help from a graphic designer and according to her this is
> not the way a newsletter should look like. She prefers a much shorter
> HTML, full of links to articles that appear on the site and no actual
> contents. I must say I'm subscribed to such a newsletter, but it always
> annoys me me that there is no real contents, just a bunch of links. Is
> this a de-facto standard? Opinions appreciated.
Perhaps a compromise. When adding too much content, subscribers may not want
to scan down all articles to see if there is something worth reading. So give
them a few lines per article, usually an abstract, then follow it by a read
more ... link.
This way you can put many headlines and shorter abstracts into a single
letter. Readers can glimpse the overall of what is going on from these pieces
of information and click-through when they want to read more. In this way,
readers can get a better overall view of what is going on and still access
the meat.
Hope this helps,
--
Sean Wheller
Technical Author
email: sean -at- inwords -dot- co -dot- za
im: seanwhe -at- jabber -dot- org
skype: seanwhe
cel: +27-84-854-9408
web: http://www.inwords.co.za
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-