greenfield and new structure

[John Sgammato]

I made great progress today. I was able to open the DITA files and get them pretty consistent with new master pages, etc. 
I see two issues right now that I cannot figure out: 
* I want to get rid of many, many paragraph formats that I won't need, but I don't know if it is safe to do that, or if it will break something. 
* I have many topics that I want to nest as H2s under H1s, etc, and I cannot see how to do that, but today was only my first day so I am sure I will get there. 
I am grateful for the progress I have made, but I wish I had some documentation!
I tried the Yahoo group and Yahoo won't let me in with my old credentials - I'll resolve that tomorrow. It's getting late here in Boston!

On Nov 29, 2012, at 7:16 PM, Writer <generic668 at yahoo.ca> wrote:

>> T hanks Nadine!
> 
>> Yes, the existing product documentation was authored in oxygen in India. I 
>> don't have good access to those resources, but I have the DITA files. I have 
>> to make them look presentable, and then improve the quality of the writing, fill 
>> in gaps, etc. 
>> So I have no legacy FM content, only DITA content. I want to use FM's 
>> publishing capabilities. I am well familiar with unstructured FM10, but 
>> unfamiliar with structured FM11. 
>> john
> 
> 
> I'm pretty sure what I'm about to say is accurate. Someone correct me if I'm wrong...
> 
> You should be able to open those files in FM (make sure you're in structure mode). You can edit the EDD files and template files to look as close to your print documentation as you can so that when you generate FM books/files, the formatting is almost exactly as you need it.
> 
> Have you tried just opening the DITA files in FM? If so, did you encounter any problems? 
> 
> When I used FM9, I only edited EDD and template files a little bit. I relied on my processors to format output completely. In the case of production PDFs, that meant generating FM books/files, and then applying an FM template to the generate files. Part of the reason for doing it this way was so we could use the generated FM files in different ways (branded/custom documentation, quick guides as opposed to full books, etc). BTW, we used WebWorks ePublisher to create draft PDFs and online help systems. ePublisher ingests ditamaps directly; you don't have to create FM files first.
> 
> Nadine