Yeah, I did ramble on a bit in this suggestion, mostly since I figured I might as well point out a couple related issues, and didn't want to spam the comm with more than one suggestion. But anyway, what I meant to say wrt removing options was that the "Allow Mask" one should not be something that the user can opt out of at all. An option that makes the export useless as a backup is probably not something that should be exposed to users by default. Removing the option wouldn't neccesarily mean removing the field that is added to the export; that could just be added on as part of the baseline export without user input. That said, whether it shows up on the export form isn't hugely important to me so long as it is immediately obvious what it would do if you unticked it.
In that vein, I feel like you shouldn't need an FAQ to understand how to get a basic, complete export out of any system. Why not add the relevant information to the actual form or make the options there self-explanatory instead of putting all that on a separate page? If the goal is to make sure that people understand how to use it, most of the instructions should be right there in front of them when they are trying to use it. As for how to mask some of the information for advanced users, I'm thinking of the little question marks by fields in the update form, the ones that show helpful tooltips when you hover over them. That would be a better way to handle extra explanations, and it would be more usable than having to go elsewhere.
Also, why change labels on the form but not in the export file? I don't think the current export formats are actually compatible with any blogging services (Wordpress, etc), and I can't think of any clients that actually use it to produce exports or anything. And if they did implement a more granular access field that distinguishes between levels of access (access only, custom filters, etc) they would have to change things in the export file to match. Basically I'm just curious as to why you think those should be kept the same.
no subject
In that vein, I feel like you shouldn't need an FAQ to understand how to get a basic, complete export out of any system. Why not add the relevant information to the actual form or make the options there self-explanatory instead of putting all that on a separate page? If the goal is to make sure that people understand how to use it, most of the instructions should be right there in front of them when they are trying to use it. As for how to mask some of the information for advanced users, I'm thinking of the little question marks by fields in the update form, the ones that show helpful tooltips when you hover over them. That would be a better way to handle extra explanations, and it would be more usable than having to go elsewhere.
Also, why change labels on the form but not in the export file? I don't think the current export formats are actually compatible with any blogging services (Wordpress, etc), and I can't think of any clients that actually use it to produce exports or anything. And if they did implement a more granular access field that distinguishes between levels of access (access only, custom filters, etc) they would have to change things in the export file to match. Basically I'm just curious as to why you think those should be kept the same.