There are many many technical documents describing a technical process. There are many technical documents describing tax process. These are both written by a domain specialist, as a reference for other specialists; and as context and guidance notes for non-specialists. The first case is normally fairly simple and ignored in this document. The second use-case is increasingly a concern e.g. 1, as the expectations on abilities by average people increases.
Under current legislation, plain English is required 2 ~ in broad terms ~ for legal documents. The CPS defines its documentation requirements in the following 3. According to 4, there are rarely prosecutions.
I agree with the concepts expressed in the above two paragraphs; except that not all documents are intended for all individuals. My linguistic style isn't very procedural, and I don't use that many heavy German-sounding structures. On this site, I intensionally skip all the “introduction to X” material, but link external resources. That anyone may read this is a goal; that everyone will want to, isn't. My target market is educated IT professionals (although I will deploy tool tip integration at some point, which will improve my user range.).
The following are useful references :
To focus on language itself, I write this with the context of academic journals. I am not forcing third person grammar, but wish to avoid much personal opinion. My goal is to inform (a buzz term in my current office). Larger or contentious statements should be supported by references. Inside the framework of plain English, I wish to support detailed technical language use. Precise nouns allow more terse documents, links may be provided as supporting material.
Referencing lingustic register structures 5 6 7, the more technical website/blogs tend to fall into two categories. Depending on the mood of the author, they are either formal or casual registers (the common scale has five categories). This site will tend towards the formal end, but I wish to retain conciseness. I use received pronunciation structures, intentionally, as a cultural territory away from en_US. I am mostly talking to en_UK readers. Secondly any people with English as a second language should find RP easier to understand.
Reading some tech business sites (e.g. 8), my language use is plain and avoids buzzwords. I generally sound like how I write on here, rather than another corporate “org spk”. I think this is a strength. Domain language is very useful for known audiences (like peers over the duration of a project), but is not communication otherwise. One of the characteristics of Engineering English is the lack of emotive works, values are quantitatively evaluated, rather than qualitatively.
A quick web search didn't supply any useful tools, for analysis. My sentences, as Engineering variant English, are not long. There are basic tools available through Google search; but these are to filter results, rather than inform on a particular page. There seems to a be trend in many news sites of splitting articles into 200word sub-pages to serve more advertising, and to pander to the US that thinks that text is educated. I am trying to target maximum of 1,500 words per article, which should be about 1screen at 1280pixels, ignoring some of the furniture. As my content quite often exceeds this, I am too serving multiple pages. In my case, there may be a several month gap between a part, and the next.