RE: same-named heading1s in different chapters ?

["Jelus, Susan C." <susan -dot- jelus -at- thermofisher -dot- com>]

I agree with you.  Every topic should have a different name.  Otherwise it can get confusing for the reader/searcher.  The only exception I can think of to this is when topics are clearly and always nested under the heading (such as is often the case with online help - and you probably want consistent topic names there).  

How about just using something like <topicname> for heading1?  The more specific a topic name is, the better, seems to me.  


Susan Jelus

-----Original Message-----
From: techwr-l-bounces+susan -dot- jelus=thermofisher -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+susan -dot- jelus=thermofisher -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Monique Semp
Sent: Tuesday, December 01, 2015 12:41 PM
To: TechWR-L
Subject: same-named heading1s in different chapters ?

Hello, WR-L-ers,

Iâve ended up with two chapters that both have a heading1, â<topic-name>â. It really is the correct name for both instances, within the context of their respective chapters.

But somehow it just doesnât seem quite right to do this. (Iâve just added an xref in the first chapter to the same-named heading1 section in another chapter, which is what made me wonder about the wisdom of my chosen heading1 titles.) So I thought Iâd query the hive to find out your thoughts?

I could see the answer varying depending on the delivery method. In this case itâs a FrameMaker-authored PDF doc. It will (never?) be delivered as HTML, so no chance of conflicting URL page names. And internal xrefs (which are live hyperlinks in the PDF) always have a page number included, so thereâs no chance of the user ending up in the wrong section.

I could of course make the headings have longer text to provide context, but then for parallelism Iâd want to rename the other chaptersâ topics (which by chance do not repeat). The result would be excessive wordiness and a much harder to scan/comprehend ToC.

Thoughts?
-Monique
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as susan -dot- jelus -at- thermofisher -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives