Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with style
Search options not deleted
user 19623
This tag should be used for questions that deal with a consistent style in your writing, such as when asking about typical ways to introduce a certain aspect to your reader by showing-telling or if you are concerned that your readers might feel that a change in the point of view might be perceived as inconcsistency.
21
votes
Does DRY (Don't Repeat Yourself) Apply to Documentation?
The more your documentation is aimed at people reading it like a book the less you should repeat yourself. The more your documentation is a look at this one page read it put it away the more you shoul …
- 626
17
votes
Accepted
Should IKEA assembly instructions be used as positive examples to train technical writers?
I think they are great examples—if your use case matches. They never explain two things differently across all their products. Take the world's most sold book case, that Billy you referenced. It has o …
- 626