cleaning up the clutter
play

Cleaning Up the Clutter: Refresh Your MadCap Flare Project Design - PowerPoint PPT Presentation

Cleaning Up the Clutter: Refresh Your MadCap Flare Project Design PRESENTED BY Nate Wolf AGENDA Signs of Needing a Refresh 1 Global Project Linking 2 Refreshing Your Project 3 Staying On Track 4 Questions 5 SIGNS YOUR PROJECT NEEDS A


  1. Cleaning Up the Clutter: Refresh Your MadCap Flare Project Design PRESENTED BY Nate Wolf

  2. AGENDA Signs of Needing a Refresh 1 Global Project Linking 2 Refreshing Your Project 3 Staying On Track 4 Questions 5

  3. SIGNS YOUR PROJECT NEEDS A REFRESH • Multiple Stylesheets and/or TableStyles • Unused or inefficient file usage • Old HTML design/not responsive • Local Formatting • Not using Project Properties

  4. MULTIPLE STYLESHEETS/TABLE STYLES • Styles getting out of hand much?

  5. INEFFICIENT FILE USAGE • Unused topics • Similar topics used for different purposes • TOCs for every version of a product Rethink the ways you use files

  6. OLD DESIGN • Want to move from Tripane? • Does your layout and design look like it’s from the 90’s?

  7. LOCAL FORMATTING • Styles overridden with local formatting

  8. LOCAL SETTINGS Not set at project level • Target Level • Even worse, topic level

  9. Global Project Linking

  10. START WITH A GLOBAL PROJECT • Stylesheets • Variables • Master Pages • Table Styles • Page Layouts • Snippets

  11. WHY USE A GLOBAL PROJECT? • Files maintained in one place • Gatekeeper • Future-proof your documentation strategy

  12. GLOBAL PROJECT LINKING Global Project Project A B

  13. SETTING UP GLOBAL IMPORT FILE In your child project(s)

  14. SETTING UP GLOBAL IMPORT FILE Set up import options

  15. SETTING UP GLOBAL IMPORT FILE Accept files

  16. REIMPORTING GLOBAL PROJECT Reimport manually or automatically

  17. Refreshing Your Project

  18. Disclaimer • Not a complete list • Every project is different

  19. KEEP. IT. SIMPLE.

  20. BACKUP PROJECT(S) I cannot stress this enough! • Create a backup of your child project(s) for testing • If anything goes wrong, you’ll have a working backup

  21. REVISIT YOUR STYLESHEET(S) • Look at stylesheet implementation – Most likely can create a new one (run reports) – Think simple • Use templates • No need for styles that perform same function – Multiple indent styles – Over-defining styles

  22. • Moving to a new HTML design? Revisit Layout Files • Want to update your PDF design?

  23. REVISIT VARIABLES • Add new variables? • Start using them? • Find and Replace with a variable – <MadCap:variable name="DemoVariables.ProductName" />

  24. RUN REPORTS • What items are currently unused?

  25. REPORTS

  26. • Topics • Import Files • Stylesheets Delete Files • Table Styles • Variables • TOCs

  27. SET PROJECT DEFAULTS

  28. APPLY YOUR CHANGES • Targets

  29. APPLY YOUR CHANGES • TOCs • Styles

  30. REMOVE LOCAL FORMATTING • CTRL+A + Select – Removes from entire file

  31. REPLACE OLD STYLES W/ REGEX Regular Expressions (RegEx or RegExp) Example • Find <span class=“bold”>(.*?)< \/span> • Replace <strong>\1</strong> http://regexlib.com/CheatSheet.aspx

  32. IN SUMMARY Set Project Defaults Go global! 1 6 Backup Apply your settings 2 7 Revisit Design Files Remove Local Formatting 3 8 Run Reports Clean up with RegEx 4 9 Delete Stale Files Pat yourself on the back! 10 5

  33. Staying On Track

  34. DOCUMENT YOUR PROJECT …in your project Create files/comments in your project that details uses for: • Styles (CSS) • TOC setup • Global project • Etc.

  35. RUN REPORTS PERIODICALLY • Run the same reports from earlier • Set a timeline and reminders

  36. DON’T ADD UNNEEDED JUNK • Don’t revisit bad habits • Need to make a change? – Do it the right way! • Create an archive project • Remember, keep it simple

  37. Thank You! Questions?

Recommend


More recommend