I re-uploaded site.language. There were still some duplicate strings
and typos:
Typo 1) Use this form to select pages & files and conbine them into a
tool: <- conbine
Typo 2) Welcome to BoltWire's site administration area. Here you can
find links to many system pages used to control how this software
works. If you are not sure what something does, be sure to read the
appropriate tutorials. In other words, be careful! <- double space
before second sentence
I don't get the meaning of the following sentence:
"Any variables in the embed will be processed, including skin
variables, making it possible to dynamically change how the script
functions using data or get variables, for example."
Is "functions" a verb or noun here? Is there some sense-spending comma
missing?
After going through the whole updated site.language file I can't help
myself but to admit: for my taste the language of BoltWire is way too
verbose and at places non-standardized or inconsistent. The language
can't compete with the exceptional beauty of its implementation and
its concepts. I know, language is one of the hardest things. Microsoft
succeeded in confusing millions of people by bad language for decades.
I'll use some examples to make my point.
1) "Any installed plugins are listed below. Click here to
[[action.plugins|install]] additional plugins, or here to view your
[[site.plugins|installation log]]. Additional plugins can be
downloaded from [[www.boltwire.com/index.php?p=solutions|
BoltWire]]. ::
I mentioned my dislike of "click here" sentences. Either the link is
"here" but then the explanation of the link is elsewhere, or the link
is the explanation then you obviously can't click "here".
"Any installed plugins are listed below." These are six words. I
prefer "Installed plugins:". Two words and your brain processed these
two words a million times already. Look at any user friendly operating
system or CMS of your choice. You rarely find sentences. Who wants to
process a sentence if one can get the same information in two words?
There is much sense to naming a button CREATE and not CLICK HERE TO
CREATE THIS PAGE NOW.
Then there are three things the user can do according to the above
sentence: install plugins, see installation log, download plugins.
First, take notice that you need only 7 words to inform the user about
all three actions. Make them links and you are done. Instantly the
user can grasp it. He won't being presented 3 long sentences. Even
when the user uses that page very more often, he will have a much
harder time to find the link he needs if it is embedded in a long
sentence.
Sometimes lists could be useful.
Actions:
* install plugins
* download plugins
* see installation log
The best part is that such a skeleton could be used wherever the user
is presented several possible actions. He would then notice the common
structure across pages.
Another example: "Timestamped versions of this page exist. [[{p}
&action=history|Click here]] to restore one."
Alternative: [[{p}&action=history|Restore timestamped versions]]
Or: [[{p}&action=history|Timestamped versions exist]]
All else seems obvious to me. BoltWire wouldn't let you restore
timestamped versions if there were no timestamped versions.
Sometimes more verbose explanations are needed, I agree. But then I
would provide these explanations _in addition_ to the concise wording
and out of the way. You only read the explanation once or twice in
your life, not so for the concise version.
It might (!) be a good idea to hide longer explanations somehow. Maybe
a little help pic that opens an in-page popup when clicked. Out of the
way but instantly at hand.
Last but not least, I think some common "explanatory language" has
been formed which is concise and uses short, easy to understand
sentences. If you happen to sit in front of a Mac, open help and
enjoy. If we approach this gold standard of highly consistent and
concise language, BoltWire will gain much value.
Summary:
* click here :(
* long sentences :(
* concise :)
* consistent :)
* visually easy to grasp :)
* uncluttered :)
* grandma gets it :)
How to achieve it?
1) decide if we want to use common skeletons like action lists or
other reoccurring parts for the user interface
2) improve BoltWire page by page
Of course, this journey could be extended to BoltWire.com but I'll
stop my rant. One step after the other.
Happy Sunday,
Markus
On Jan 9, 1:42 pm, Markus <[email protected]> wrote:
> I changed site.language:
>
> * alphabetic ordering where it wasn't
> * removed some duplicates
>
> I uploaded the file to the group.
>
> Best,
> Markus
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en.
