I am a new Flare user trying out Capture. Like Flare, Capture is highly customizable which is ultimately a great feature but can be a bit overwhelming for the new user. Are there any best practices in existence that may help me as I try to figure out just how to I want to set up my profile?
1. Specifically, I would like to know if there are W3C standards that I can be sure I adhere to with regard to WebHelp output and the correct display of screen captures and the vectors I am adding to them (callouts, arrows; etc.).
2. And, I would like to know if there are any organizational tips to managing all of the captures I am accruing. For instance, is it recommended to set the capture path to a location w/in my project(s) or is it really better to identify a location outside of my project(s)?
Thank you!
Capture Best Practices?
Re: Capture Best Practices?
We store images in the default images directory.
It simply seems like the logical thing.
I do make sure the file names are understandable and follow a common naming convention though.
identify the type of picture.
Is it an icon, chart or screen, common collateral like cover pages and branding assets.
Then incorporate that into the filenames with 2 letter code prefix.
icxxxxyyyy.
That's it.
If I want to classify the pictures further i add prefixes or suffixes.
I do see the wisdom of creating classes of subdirectories. This make managing 1,000s of pictures easier when you are working with large sets of media data.
Prune or look for orphans with the unused file reports every three months or so. That's it
It simply seems like the logical thing.
I do make sure the file names are understandable and follow a common naming convention though.
identify the type of picture.
Is it an icon, chart or screen, common collateral like cover pages and branding assets.
Then incorporate that into the filenames with 2 letter code prefix.
icxxxxyyyy.
That's it.
If I want to classify the pictures further i add prefixes or suffixes.
I do see the wisdom of creating classes of subdirectories. This make managing 1,000s of pictures easier when you are working with large sets of media data.
Prune or look for orphans with the unused file reports every three months or so. That's it
If you submit your bug feedback request here, the more likely it'll get fixed or included in a future release
Open Utilities PageLayout Resizer for Flare/Blaze | Batch builder
Open Utilities PageLayout Resizer for Flare/Blaze | Batch builder
Re: Capture Best Practices?
Thank you for your input. I really appreciate knowing what has made sense to others and continues to work in practice. If you or anyone else continues to find best practices for Capture image storage, settings; etc. keep 'em coming!