← EasyEnglishPrint Complete selected book and course series

Source-backed English writing guides

Browse complete writing, composition, rhetoric and technical-writing series from the local English Wikibooks and Wikiversity canonical dumps. Every detail retains its source revision and full cleaned native sections; media is deliberately excluded.

274
long-form local pages
6
source series
500+
cleaned characters per detail
Grouped by book or course

No isolated wikitext fragments

Each page belongs to a named source series. Redirects, template-only pages and pages below the 500-character native-text threshold are excluded from independent details. Source links are secondary revision and attribution references, not the main reading path.

Runtime
Local canonical SQLite → startup memory view
Media
Not materialized; text-only rights boundary
License
CC BY-SA 4.0 with revision attribution
Visitor upstream
None
Writing guides

274 matching long-form pages

Technical Writing · English Wikiversity

Audience/Exercises

Exercises from Technical_writing_audience: According to the Wikipedia page "Wikipedians," 91% of Wikipedia contributors are male. One in five lives in the U.S., followed by Germany and Russia. India is the only country outside Europe and North America represented in the top ten. The English…

Native text
1984 characters
Revision
2112752 · 2019-12-28T13:35:03Z
Read the full local page →
Technical Writing · English Wikiversity

Audience/Persona/Michail

back to Audience Analysis back to Audience Analysis *age: 35 *Geography: Moscow, suburbs *Languages: **Russian **English *** learned through study/courses *** strong reading skills - upper intermediate *** speaking/listening skills - intermediate *** strong technical vocabulary *Education: ** BS -…

Native text
2867 characters
Revision
2112756 · 2019-12-28T13:36:35Z
Read the full local page →
Technical Writing · English Wikiversity

Classroom

* Technical writing main page * Easy English technical writing courses * TW Fred - Technical writing * Bob Cooper - Easy English technical writing * Susan F. ;Your instructor is TWFred ;TWFred talking about how to test Requirement Specifications (YouTube Video) * Part of the Engineering and…

Native text
1336 characters
Revision
2112707 · 2019-12-28T13:27:13Z
Read the full local page →
Technical Writing · English Wikiversity

Collaborating EE

* back to Technical Writing Level 1 Before more than one person can work on a document everyone must be sure which copy of the document they are working on. It is very easy to start working on an outdated copy and this will duplicate work and sometimes create multiple parallel copies none of which…

Native text
5343 characters
Revision
2112737 · 2019-12-28T13:31:49Z
Read the full local page →
Technical Writing · English Wikiversity

Cost and schedule estimating

back to Technical Writing Level 2 All projects cost time and money. It is important to accurately estimate how much a project will cost. Most projects are late and more expensive than planned. According to a study on Estimating Software Costs, documentation accounts for 10% of the total cost of a…

Native text
2119 characters
Revision
1414163 · 2015-08-18T02:41:10Z
Read the full local page →
Technical Writing · English Wikiversity

Courses

cellspacing="0" cellpadding="0" style="margin:0em 0em 1em 0em; width:100%" rowspan="2" style="width:40%; vertical-align:top; border:1px solid Gold; background-color: LightYellow;" Technical Writing Courses :We offer Level 1 and Level 2 courses in technical writing, plus a workshop on writing system…

Native text
2250 characters
Revision
2347767 · 2021-11-21T14:13:26Z
Read the full local page →
Technical Writing · English Wikiversity

Document Design

back to Technical Writing Level 2 The design stage is when decisions of how a project will look are taken. In documentation, the design phase is about deciding the following: *What will the document cover look like? *What format will the document take? *How will the document look? *In what order…

Native text
1264 characters
Revision
2230782 · 2020-10-20T17:57:47Z
Read the full local page →
Technical Writing · English Wikiversity

Edits

back to Technical Writing Level 1 Technical writing relies on delivering accurate and precise information. Commonly, management and designated subject matter experts review all work performed prior to a documentation release. It is important to understand that a documentation review is not…

Native text
3930 characters
Revision
2112658 · 2019-12-28T13:16:27Z
Read the full local page →
Technical Writing · English Wikiversity

Exam02

back to Technical writing This Level 1 exam paper was originally written in a word processor. It has been slightly modified to fit wiki formatting. TWFred 14:38, 2 December 2007 (UTC) SDLC means Software Development Life Cycle, sometimes it is called the System Development Life Cycle. The SDLC is a…

Native text
6272 characters
Revision
2112727 · 2019-12-28T13:29:03Z
Read the full local page →
Technical Writing · English Wikiversity

i18n l10n and g11n

Back to Technical Writing Level 2 With the same products being used around the globe, it is important to adapt products to local markets particularly where the original comes from a different culture and language. Not only does the product require adaptation, but the technical guides and Help…

Native text
3276 characters
Revision
2112692 · 2019-12-28T13:20:16Z
Read the full local page →
Technical Writing · English Wikiversity

Job interview

Technical Writing is a flexible career that lets you learn for a lifetime. The demand for technical writers is strong worldwide. The conditions and pay are professional. Landing a technical writing position is difficult for novices. It's also a challenge for those who are leaving their first…

Native text
11952 characters
Revision
2690387 · 2024-12-05T13:16:26Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good

#Read the following paragraphs #Copy the paragraphs to a new page (in the section below) #Separate the chunks and give them UniqueIDs #Re-write the chunks in proper requirements style #Save your page At the beginning of each month all clients (Customer Alpha, Customer Omega) print invoices for…

Native text
1732 characters
Revision
1824082 · 2018-02-25T14:54:23Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/AdamHanaExercise

*Billing Session (referred to as a Session for Bill Results, SFBR) *Hot-bill *Personal Account Prerequisits: The system shall allow customers to have several contracts that may contain several Personal Accounts each. *PI 01: The system shall automatically print invoices at the end of a Billing…

Native text
1843 characters
Revision
1824083 · 2018-02-25T14:54:33Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/BobrobExercise

I010 All clients must print invoices for the previous month. I020 Invoices must be printed from a list of Personal accounts. I030 Must have the option to select and print invoices. I040 Must be able to use bulk printing including. *Hot-billing the bill includes ** date period ** accounts **…

Native text
1182 characters
Revision
1824084 · 2018-02-25T14:54:43Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/FredRequirementExercise

Invoices: I-010 Clients must print invoices at the beginning of each month I-020 Invoices contain records for the clients previous month's activity I-030 The system must allow bulk printing Parameters: P-010 The parameters for selecting an invoice include: *Session for Bill Result (SFBR)…

Native text
1613 characters
Revision
2186627 · 2020-08-11T15:04:06Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/JanaPetrExercise

Invoices: I-010: Customers must print invoices at the beggining of each month for the previous month I-020: The system must enable bulk invoice printing for: * Invoices * Hot-bills I-030: The system prints an invoice or a hot-bill for one date/time range Parameters: P-040: The system prints…

Native text
1966 characters
Revision
2105023 · 2019-12-08T05:09:52Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/WlodekZdenkaExercise

Invoice requirements I01. The system must print the invoice on the specified date of the month by default/the date is optional I02. The system must print the invoice for each customer/ optionally 1 customer, default ALL I03. The system must be able to print the invoice for the particular…

Native text
2133 characters
Revision
1824085 · 2018-02-25T14:54:53Z
Read the full local page →
Technical Writing · English Wikiversity

Making a bad requirement good/YanaMartinExercise

System performance: *SP-010: The system must enable bulk printing of invoices for all customers at the beginning of the next month. *SP-020: The system shall contain a visible list of accounts. *SP-021: Each contract can have several personal accounts. *SP-022: One customer can have several…

Native text
1036 characters
Revision
1710259 · 2017-07-21T23:07:23Z
Read the full local page →
Technical Writing · English Wikiversity

Our experience

In theory I love all the things this proposed policy/method/recommendation envisions learning. And according to some interpretations of the standards in the "Wiki Way" I'm an abject failure. Rather than having most of the content sort of self-form (as in the Wikipedia Way), I've found that I have…

Native text
3552 characters
Revision
1414164 · 2015-08-18T02:41:10Z
Read the full local page →
Technical Writing · English Wikiversity

Overview

* How to edit Wiki * Wikiversity Main Page * Back to Technical Writing Level 1 __NOTOC__ * "What is Technical Writing" - Warren Clendining, Mount Royal University Continuing Education instructor (YouTube Video) * Technical Writing in 20 minutes - Part 1, Cherryleaf (YouTube Video) * TWFred…

Native text
11585 characters
Revision
2793917 · 2026-02-26T01:21:00Z
Read the full local page →
Technical Writing · English Wikiversity

Overview EE

* back to Technical Writing Level 1 This overview module and the following modules have been written intentionally in the style of a technical document. This is so that the reader sees the type of content needed for technical documents from the outset. The language of the document has been kept…

Native text
6810 characters
Revision
2196588 · 2020-08-26T18:20:12Z
Read the full local page →
Technical Writing · English Wikiversity

Persona/Joe Smith

Back to Talk:Technical Writing Note: Need copyright free pictures for personas... Joe is from Idaho. At university he studied English literature and decided to spend a year teaching English as a foreign language, and did a four-week training course straight after university. Now 28, Joe has spent…

Native text
1988 characters
Revision
2112711 · 2019-12-28T13:28:00Z
Read the full local page →
Technical Writing · English Wikiversity

Persona/Wing Lee

Back to Talk:Technical Writing Note: need to get photo with no copyright issues Wing Lee is a 38 year old project manager from Hong Kong. Wing is married and has one son. Her family lives in the Taikoo area, in an area which has many expatriates living close by. Wing's husband works as a property…

Native text
2074 characters
Revision
2112754 · 2019-12-28T13:36:00Z
Read the full local page →
Technical Writing · English Wikiversity

Presenting

back to Technical Writing Level 2 __TOC__ cellspacing="0" cellpadding="0" style="margin:0em 0em 1em 0em; width:100%" style="width:100%; vertical-align:top; border:1px solid Gold; background-color:LightYellow;" Technical Writing at Wikiversity When preparing a presentation it is essential to have…

Native text
5739 characters
Revision
2248687 · 2020-12-30T11:27:40Z
Read the full local page →
Technical Writing · English Wikiversity

Project management

back to Technical Writing Level 2 In the planning phase the system is created on paper. *Defining the proposed system *Scope – setting the project boundaries *Developing project plan – the what, when and who of the project *Managing and monitoring the project plan – tracking and validation *Setting…

Native text
17048 characters
Revision
2209533 · 2020-09-22T22:45:06Z
Read the full local page →
Technical Writing · English Wikiversity

Project management/Environment

Back to Technical Writing PM The literal meaning of environment is the surroundings in which a person finds himself and environment is an essential question which is to be addressed by the technical writer as it affects not what is written but also in what format it is presented. Take for example…

Native text
639 characters
Revision
2112674 · 2019-12-28T13:18:47Z
Read the full local page →
Technical Writing · English Wikiversity

Project management/Research

Back to Technical Writing PM Knowing your audience is a vital skill for the successful technical writer. It is of paramount importance to know exactly who it is you are writing for, what are their aspirations and goals in life, as well as the environment in which they will be using the materials…

Native text
1847 characters
Revision
2112676 · 2019-12-28T13:18:48Z
Read the full local page →
Technical Writing · English Wikiversity

Project management/User Goals

Back to Technical Writing PM Simply put, goals are the things you want to achieve in both your professional and personal life. By knowing what things a user or business persona wants to achieve it is possible to work out the abstract motivations behind those goals. The more abstract the goal, the…

Native text
860 characters
Revision
2112678 · 2019-12-28T13:18:48Z
Read the full local page →
Technical Writing · English Wikiversity

Requirements analysis

back to Introduction to Technical Writing This is a working page for the task of the Fred's TW training course. Scope of possible requirements (something to begin with): *Content of the training wiki page: **Must contain only topics related to TW **Level of TW (for wide audience, for beginners, or…

Native text
3195 characters
Revision
2112739 · 2019-12-28T13:32:12Z
Read the full local page →
Technical Writing · English Wikiversity

Requirements and Functional Specifications EE

back to Technical Writing at Wikiversity This course aims to improve the way that Business Analysts, Developers, Project and Product Managers: * Interact with each other by understanding each other’s roles * Identify and understand the initial objectives (Goals) of the Customer * Actively guide the…

Native text
4547 characters
Revision
2112743 · 2019-12-28T13:32:22Z
Read the full local page →