Reputation
Next privilege 250 Rep.
View close votes
Badges
5
Impact
~2k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
23h
awarded  Popular Question
1d
awarded  Nice Question
1d
comment Better term than “hardcoded” for end-user documentation
In consultation with others writers in the office, we landed on "preset". This seemed to be the easiest to understand on its own.
1d
awarded  Scholar
1d
accepted Better term than “hardcoded” for end-user documentation
1d
comment Better term than “hardcoded” for end-user documentation
The issue that caused me to post this question was related to documentation for laboratory software. Users have to enter to samples under specific "projects". Some of these projects are part of the application and can be used but not modified.
1d
comment Better term than “hardcoded” for end-user documentation
Preset is close but it doesn't convey the fact that in this case the user can't modify the object. Fixed is more accurate, but might not make immediate sense to some users (e.g. "fixed template? As opposed to a broken one?") Preset/fixed is what I want to convey, but using the slash feels sloppy.
1d
comment Better term than “hardcoded” for end-user documentation
In the example, I would think "default" would refer to the template that would be used automatically when you create a new document. What I mean is if the user could chose between multiple "hardcoded templates", so it's not really a default (although the default template would be a "hardcoded template").
1d
awarded  Student
1d
asked Better term than “hardcoded” for end-user documentation
Nov
22
awarded  Supporter