9/15/2023 0 Comments Madcap flare demoSimply put, single-source publishing cannot handle - and was never designed to govern and manage - a disparate mix of documentation formats in a practical, efficient way. And while much of it may be in DITA, there is usually plenty of other stuff, such as markdown, legacy content (FrameMaker, Word, Madcap Flare, etc.), multiple XML structures, content obtained through corporate acquisitions, content written in systems like Salesforce and Confluence, and the list goes on. This is because content in multi-source publishing environments is created and used by different teams, business units and so on. However, when they are expected to apply this approach in a multi-source publishing environment, the concept breaks down – and the dream of streamlined efficiency and greater ease, often turns into a nightmare of extra work and added stress. To change the logo image in the top-left, edit the master page and change the references to to your logo image.For years, tech writers have successfully instituted single-source publishing. If you find that you need to change a style in foundation.css, you can edit that in Resources > foundation > css. If you use the browser's inspect mode (or equivalent), you can see the styles for each element, and the css file that contains the style definitions. Change Foundation styles by Editing the Foundation.css file (I tend to only use the Flare editor when I want to make sure the path to an image or other file is correct). Of course, you can edit these outside of Flare if you want. If you need to change heading levels, paragraph fonts, and the like, this is the place to do it. The FlareStyles.css file is called last in the master page, and so you can edit the styles in it without messing up the workings of the layout. Modify the Look of your Content by Editing the FlareStyles.css in Flare There's some sort of glitch that occurs if you edit this stylesheet in Flare and It stops the output from working as we want it.If you need to make changes to any of the classes or ids in this stylesheet, open it in some other text editor, such as Notepad++ and make the changes there.Made a tit of yourself and opened it in Flare's editor? Not to worry, you can download just the TopicStyles.css file using the button below. If you are going to change anything in this file DON'T DO IT IN FLARE'S BUILT-IN EDITOR. For most of the look and feel stuff, you shouldn't need to edit these, but there may be a couple of things you decide to alter. Some of the styles for the layout are set in the TopicStyles.css file. Below, I've included the basic info you need. For the most part, I recommend that you build the project and use the browser's inspect (or equivalent) tool to find the classes you want to change, and the stylesheets where they are defined. You're going to need to customise the layout to use your own images and styles. Make sure it is set as the Master Page in the Target's Advanced settings.Ĭustsomise the Look and Feel Changing the Styles Use the Foundation-responsive-offcanvas.flmsp master page. The only things you need to make sure are in place are the target settings. Much of the project can be set up in the same way as any other Flare project. If you run into problems and come up with solutions, please post them in the comments - other people may find them helpful. For example, I'm not sure how menu proxies inside topics will behave. There may be some things that won't work, as I've not tested everything. Copy and paste your variables, snippets, conditions, etc., into the equivalent folders in the project.Copy and paste your toc into the TOCs folder.Copy and paste your topics from a Flare project into this project.I've made various versions of this project, and I reckon the easiest way to get it to work with different content is to:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |