Skip to content

Commit 16e4ce6

Browse files
authored
Merge branch '5.0' into 5.0-add-js-removals-to-44-50-removed-backward-incompatibility.md
2 parents 88f8a94 + dc9587a commit 16e4ce6

16 files changed

+1357
-811
lines changed

docs/common-errors/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,12 @@ Some frequently asked questions on Error messages and how to resolve them.
88

99
As a developer you somtimes will be stuck in your code.
1010
If it happens to you, also have a look on https://joomla.stackexchange.com/ - a huge collection of valuable knowledge.
11-
Here we collect some frequently aske questions.
11+
Here we collect some frequently asked questions.
1212

1313
Class [..] not found
1414
--------------------
1515

16-
You need to understand the namespace concept as described in sction General Concepts (work in progress)
16+
You need to understand the namespace concept as described in section General Concepts (work in progress)
1717
Then check:
1818
- Is the namespace defined in your manifest file?
1919
- Has every class in your extension the correct namespace?

docs/user-interface-text/A-Z.md

Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
sidebar_position: 2
3+
---
4+
5+
## 'a' or 'an' before H?
6+
* Use 'an' before a silent H: an heir, an hour
7+
* Use 'a' before an aspirated H: a hero, a hotel, a historian
8+
* With abbreviations, be guided by pronunciation: eg an HTML document
9+
10+
## Abbreviations and acronyms
11+
* The first time you use an abbreviation or acronym explain it in full on each page then refer to it by initials unless it's well known, eg HTML, CSS etc.
12+
* If you think your acronym is well known, please provide evidence that 80% of the UK population will understand, and commonly use, the term. Evidence can be from search analytics or testing of a representative sample.
13+
* Don't use full stops in abbreviations – BBC, not B.B.C.
14+
* Use all capitals if an abbreviation is pronounced as the individual letters (an initialism): HTML, CSS
15+
* If it is an acronym (pronounced as a word) spell out with initial capital, eg Nasa, Nato, Unicef, unless it can be considered to have entered the language as an everyday word, such as laser and sim card.
16+
* Note that pdf is lowercase.
17+
18+
## Accents
19+
* Use on French, German, Portuguese, Spanish and Irish Gaelic words (but not anglicised French words such as cafe, apart from exposé, lamé, résumé, roué).
20+
21+
## Americanisms
22+
* Don't use Americanisms. You 'fill in' a form, not 'fill out' a form.
23+
* Exceptions include where it's part of a specific name, eg '4th Mechanized Brigade'.
24+
* Use the 'ise' rather than 'ize' suffix, eg organise not organize (this isn't actually an Americanism but is often seen as such).
25+
26+
## Amounts
27+
See numbers
28+
29+
## Check
30+
See select.
31+
32+
## Colour codes
33+
Hex colours are case insensitive so it doesnt matter if we use upper or lowercase. However we should be consistent in our usage. As the color selector fields uses lowercase then the text should also user lowercase for consistency.
34+
35+
## Contractions
36+
Use contractions sparingly eg can't. Avoid using you'll, you've, should've, could've, would've etc – these are hard to read.
37+
38+
## Dates
39+
* use upper case for months eg January, February
40+
* don't use a comma between the month and year, eg 14 June 2012
41+
* when space is an issue, eg tables, publication titles etc, you can use truncated months, eg Jan, Feb, Mar
42+
* use 'to' in date ranges – not hyphens, en rules or em dashes. For example: copyright year 2011 to 2012
43+
* Monday to Friday, 9am to 5pm (put different days on a new line, don't separate with a comma etc)
44+
* 10 November to 21 December
45+
* don't use 'quarter' for dates; use the months, for example: 'expenses, Jan to Mar 2013'
46+
* when referring to 'today' (eg in a news article) make sure you include the date as well eg 'The minister announced today (14 June 2012) that…'
47+
48+
## Email and Email Address
49+
Email should refer to the item that you send
50+
Email address should be used if referring to their actual address
51+
52+
Example
53+
* Enter an email address for the user.
54+
* Select which mailer for the delivery of site email.
55+
56+
## File Size display:
57+
* If less than 1 KB, display <1 KB
58+
* 1 KB to 1,023 KB, display 357 KB
59+
* 1 MB to 1,047 MB, display 2.5MB (only one decimal place)
60+
* 1 GB+, display 3.8 GB (only one decimal place)
61+
62+
## Geography and regions
63+
Use lower case for north, south, east and west, except when they're part of a name or recognised region. So, 'the south-west' (compass direction), but 'the South West' (administrative region).
64+
Use lower case for: the north, the south of England, the south-west, north-east Scotland, south Wales, the west, western Europe, the far east, south-east Asia.
65+
Use upper case for: East End, West End (London), Middle East, Central America, South America, Latin America.
66+
67+
## Maths
68+
* Use a minus sign for negative numbers with no space: –6
69+
* Ratios have no space either side of the colon: 5:12
70+
* One space each side of symbols: +, –, ×, ÷ and = (eg 2 + 2 = 4)
71+
* Use the minus sign for subtraction not the dash.
72+
* Use the correct symbol for the multiplication sign (×), not the letter x. (&times; or &#215;)
73+
74+
## Measurements
75+
* Use lower case for all measurements eg px, em, w and h
76+
* Use the metric system for mass and non-web measurements eg kg, cm and m
77+
* Use celcius for temperature eg 34c
78+
* For all other measurements use SI
79+
80+
## Money
81+
* Use the £ symbol with no space: – £75.
82+
* Don't use decimals unless pence are included, for example use: £75.50 but not £75.00.
83+
* Don't use '£0.xx million' for amounts less than £1 million.
84+
* Write out 'pence' in full eg 'calls will cost 4 pence per minute from a landline'.
85+
* Currencies are lowercase.
86+
87+
## Multi-factor Authentication
88+
Always use the hyphenated word. Multi-factor must always be a single hyphenated word and only the complete words should be capitalised.
89+
90+
## Numbers
91+
(I have changed this based on the NNG findings (http://www.nngroup.com/articles/web-writing-show-numbers-as-numerals/))
92+
* Write numbers with digits, not letters (23, not twenty-three).
93+
* Use numerals even when the number is the first word in a sentence or bullet point.
94+
* Use numerals for big numbers up to one billon. As a compromise, you can often use numerals for the significant digits and write out the magnitude as a word. For example, write 24 billion.
95+
* "Enter the **number** of hits to increase the counter by."
96+
* "Limit the **amount** of text to display"
97+
98+
## Seasons
99+
Try to avoid using them as they are not global. spring, summer, autumn, winter are lowercase.
100+
101+
## Select
102+
Select a check box item not check a check box item.
103+
104+
## Sentence length
105+
Don't use long sentences – check any sentences with more than 25 words to see if you can split them to make them clearer.
106+
107+
## Singular and Plural
108+
In general a string with a constant of ARTICLE_PUBLISHED_1 should have a value of "Article published." and not "1 Article ...
109+
110+
## Times
111+
* use 'to' in time ranges – not hyphens, en rules or em dashes, eg 10am to 11am (not 10–11am)
112+
* 5:30pm (not 1730hrs)
113+
* midnight, not 00:00
114+
* midday, not 12 noon, noon or 12pm
115+
116+
## Titles
117+
Titles should:
118+
* be no longer than 65 characters
119+
* be unique, clear and descriptive
120+
* be front-loaded and optimised for search
121+
* use a colon to break up longer titles
122+
* not have a full stop at the end
123+
* not use acronyms unless they are well-known eg HTML
124+
125+
## Tooltips
126+
Tooltips should:
127+
* be as short as possible
128+
* end with a full stop
129+
* not repeat the title or body text
130+
* be clear and specific
131+
132+
## Trademarked Name
133+
This should always be written with a capital letter unless the trademark is for lowercase eg iPhone.
134+
135+
## Two Factor Authentication
136+
This should not be used. See Multi-factor Authentication.
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
sidebar_position: 2
3+
---
4+
5+
# Action or Description
6+
## Archive / Unarchive Vs Archived / Unarchived
7+
Archive is an action so it is used on buttons
8+
Unarchive is an action so it is used on buttons
9+
Archived is a description so it is used in filters and selects
10+
Unarchived is a description so it is used in filters and selects
11+
12+
## Check in, Check out
13+
Check-in is hyphenated when it’s a noun eg I was early for check-in
14+
Check in is two words when it's a verb eg I walked up to the counter to check in
15+
Checkout is one word when it's a noun eg you wait in the checkout line
16+
Check out is two words when it's a verb eg you are ready to check out of the hotel
17+
18+
## Feature / Unfeature Vs Featured / Unfeatured
19+
Feature is an action so it is used on buttons
20+
Unfeature is an action so it is used on buttons
21+
Featured is a description so it is used in filters and selects
22+
Unfeatured is a description so it is used in filters and selects
23+
24+
## Log in, Log out
25+
Login is one word (not hyphenated) when it's a noun eg go to the login page
26+
Log in is two words when it's a verb eg you log in with your username
27+
Logout is one word (not hyphenated) when it's a noun eg select the logout menu
28+
Log out is two words when it's a verb eg you log out by clicking on the button
29+
30+
## Logged-in
31+
When counting the number of users we are counting those who are logged-in not logged in.
32+
33+
## Publish / Unpublish Vs Published / Unpublished
34+
Publish is an action so it is used on buttons
35+
Unpublish is an action so it is used on buttons
36+
Published is a description so it is used in filters and selects
37+
Unpublished is a description so it is used in filters and selects
38+
39+
## Trash Vs Trashed
40+
Trash is an action so it is used on buttons
41+
Trashed is a description so it is used in filters and selects
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
sidebar_position: 3
3+
---
4+
5+
# Capitalisation
6+
DON'T USE BLOCK CAPITALS FOR LARGE AMOUNTS OF TEXT AS IT'S QUITE HARD TO READ.
7+
8+
Sentence case is preferable but use capitalisation for:
9+
10+
* Menu Items
11+
* Labels
12+
* Buttons
13+
14+
Do not capitalise joining words and words of three characters or less such as and, to, for.
15+
16+
## Examples
17+
* Show Intro Text
18+
* Position of Article Info

docs/user-interface-text/index.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
sidebar_position: 999
3+
---
4+
5+
# User Interface Text Guidelines
6+
The official language of Joomla is en-GB and this guide is intended to assist anyone writing language strings in en-GB (British English). This guide should not be translated but may help serve as a starting point for Translation Teams to localise and produce their own guide.
7+
8+
## Purpose
9+
* Establish official style guidelines for writing en-GB strings.
10+
* Ensure consistency throughout Joomla.
11+
* Traditional rules of grammar do not always apply to the web. See [Break Grammar Rules on Websites for Clarity](http://www.nngroup.com/articles/break-grammar-rules/).
12+
* See [NNG on American vs British english for the web](http://www.nngroup.com/articles/american-vs-british-english-for-web/).
13+
14+
## Target audience
15+
* Primary: Developers writing en-GB strings.
16+
* Secondary: Translation teams.
17+
18+
## Uses
19+
* Primary: Basis for all en-GB strings.
20+
* Secondary: Assist non native en-GB developers writing language strings in en-GB.
21+
* Tertiary: Provide guidelines for translation teams to localise.
22+
23+
## Notes
24+
### Avoid over-communication
25+
Be explicit wherever necessary but don't explain the obvious. On the web scanning is the norm and too much text weakens the effectiveness of the message - it does not enhance it.
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
sidebar_position: 4
3+
---
4+
5+
# Use of the Joomla Name
6+
"Joomla!" is our name, and as such it deserves everyone's best efforts to protect it. It defines our brand for both our software and our community. It signifies our reputation for excellence. We have specific guidelines for when and how to properly use our trademarks in public-facing content such as marketing materials and Joomla.org web pages. Those guidelines are excessive within a controlled user-facing environment like the Joomla backend.
7+
8+
## "Joomla!" should always be capitalised ... ALWAYS
9+
Our project's name is a proper name. Please always capitalise the "J" of Joomla.
10+
11+
## When to bang your Joomla "!"
12+
Our registered trademark is "Joomla!" including the exclamation point. (The exclamation point is sometimes also called a "bang" from both copy editing and comic book usage.) The proper and complete use of our name is with the exclamation point. But, there are many circumstances where including punctuation that also signifies the end of a sentence makes a passage of text difficult to read or confusing. Also, punctuation is not allowed in certain contexts such as aliases and URL's. To clarify when to use the exclamation point, here are simple rules <b>applicable only to Joomla CMS language strings.</b>
13+
14+
### Rule: No Bang!
15+
References to Joomla in language strings should not include the exclamation point unless it is at the end of a sentence that is intended to be exclamatory.
16+
17+
#### Rule of thumb
18+
Whenever you can substitute "your Joomla CMS" in place of "Joomla" and still make sense, then it's descriptive and no bang needed.
19+
20+
### Exception to the Rule: Trademarks that contain Joomla
21+
Whenever the Joomla name is part of or nested inside another multi-word Joomla-related trademark or service mark then the exclamation point should be used even though it is mid-sentence. If the use is a proper name it should have capitalised initials, Joomla should include the exclamation point and it should be followed by a TM indicia.
22+
Examples: References to the Joomla! Extensions Directory&trade;, the Joomla! Framework&trade; or Joomla! 3.4 as a product.
23+
24+
---------
25+
26+
## When to Include Trademark Indicia ( <sup>&reg;</sup> or &trade; )
27+
28+
### Rule: Do not use &reg; in language strings
29+
Part of protecting a trademark, whether registered or not, is giving notice to viewers that we consider the mark to be our property. Considering the Joomla! trademark itself, since all backend users must login and will see the Joomla signature and registered trademark indicia on the login module, there is no need to include a registered mark indicia (&reg;) anywhere else in the backend.
30+
31+
### Rule: Always use &trade; following other Joomla-related trademarks
32+
With other Joomla-related trademarks or service marks, such as a reference to the Joomla! Extensions Directory&trade;, the proper indicia to use is the TM indicia (&trade;) at the end of the entire mark. Notice the exclamation point is included and the registered indicia (&reg;) normally used with Joomla standing alone, is removed. The &trade; indicia should be used with any reference to a Joomla product or service other than a release of Joomla itself (such as Joomla! 3.4)
33+
34+
These other trademarks are not registered. Nevertheless, they are protectable trademarks and service marks. A superscript circle-R should <em>NOT</em> be used with them; instead a superscript TM should be used. Because these are unregistered trademarks, extra care is needed to use them consistently on order to emphasize and retain their trademark status. The registration and broader recognition of the main Joomla! wordmark is the reason why we have more flexibility with the Joomla name being used without the exclamation point and as a noun in descriptive context than we do with these other Joomla-related product and service marks.
35+
36+
----------
37+
38+
## Summary
39+
* Refer to Joomla in general without the exclamation point.
40+
* Refer to a specific product release or series as "Joomla! 3" or "Joomla! 3.4" (with an exclamation point.)
41+
* Refer to the JED as Joomla! Extensions Directory&trade; (with exclamation point and TM indicia.)
42+
43+
--------------
44+
45+
## HTML Codes
46+
For consistent display across fonts, use the html codes for copyright and trademark symbols or indicia. For proper display, wrapping with a superscript `<sup>` tag is necessary for positioning the &reg; indicia. It is not needed for the &copy; or &trade; indicia.
47+
48+
* &reg; - for a registered trademark indicia use `<sup>&reg;</sup>`
49+
* &trade; - for a trademark indicia use `&trade;`
50+
* &copy; - for a copyright indicia use `&copy;`
51+
52+
Provenance: This page was written by Marc Antoine Thevenet and Duke Speer on behalf of the Trademark Team.
Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
sidebar_position: 5
3+
---
4+
5+
# Punctuation
6+
## Ampersand
7+
Unless in a title or referring to a title use 'and' rather than an '&', unless it's part of a trademark. Where it is used then it should be `&amp;` and not `&`
8+
9+
## Apostrophes
10+
Used to indicate a missing letter or letters (can't, we'd) or a possessive (David's book).
11+
12+
## Brackets
13+
Use (round brackets), not [square brackets]. The only acceptable use for square brackets is to indicate that it is a placeholder eg [name] is replaced with the real name.
14+
15+
## Bullet points (ul) and numbered steps (ol)
16+
You can use bullet points to make text easier to read. Make sure that:
17+
18+
* you always use an introductory line
19+
* the bullets make sense running on from the lead-in line
20+
* you use lower case at the start of the bullet
21+
* you don't use more than one sentence per bullet point – use commas, dashes or semicolons to expand on an item
22+
* you don't put 'or', 'and' after the bullets
23+
* if you add links they appear within the text and not as the whole bullet
24+
* there is no full stop after the last bullet point
25+
26+
Use numbered steps instead of bullet points to guide a user through a process. You don't need an introductory line and you can use links and downloads (with appropriate markup) in steps. Each step ends in a full stop because each step should be a complete sentence.
27+
28+
## eg, etc and ie
29+
Don't use full stops after or between these notations.
30+
User testing has shown that some people are not familiar with abbreviations such as eg, so consider your audience before abbreviating.
31+
32+
## Ellipsis
33+
An ellipsis a special character that resembles a set of three periods ( ... ) indicating an omission. In html this is represented by &hellip. There should be a single space on either side. Unless it is at the end of a string where there is no space or period after.
34+
Example
35+
* Read more ...
36+
* Create some text ... add some pictures.
37+
38+
## etc
39+
* See eg, etc and ie
40+
41+
## full stop
42+
* See period
43+
44+
## Hyphenation
45+
Hyphenate:
46+
* 're-' words only if they start with 'e', eg re-evaluate
47+
* co-ordinate
48+
* co-operate
49+
50+
Don't hyphenate:
51+
* email
52+
* reuse
53+
* reinvent
54+
* reorder
55+
* reopen
56+
57+
If in doubt, don't use a hyphen
58+
59+
## ie
60+
* See eg, etc and ie
61+
62+
## Italics
63+
Don't use italics. Use 'single quotation marks' if referring to a document, scheme or initiative.
64+
65+
## Lists
66+
See bullets and steps
67+
68+
## Period
69+
All sentences end with a period. All tooltips end with a period. Bullet points (ul) do not end with a period. Each Numbered step (ol) ends with a period.
70+
71+
## Punctuation
72+
For quotes, single quotes and speech marks use the character code not the keyboard. Order of precedence is HTML Name, HTML Decimal Code, Unicode Hexadecimal.
73+
74+
### Oxford (or serial) comma.
75+
We don't use the Oxford comma so the final item in a list before the 'and' does not have a comma.
76+
77+
### Quotes and speech marks.
78+
Use `&quot; &#34; &#x22;` at the beginning and end.
79+
80+
### Single quotes
81+
Use either `&#39; &#x27;` at the beginning and end.
82+
Use single quotes:
83+
* in headlines
84+
* for unusual terms
85+
* when referring to words or publications, for example: Download the manual 'Understanding ACL' (PDF, 360KB)'
86+
87+
## Slashes
88+
A slash (/) should not have spaces around it eg show/hide not show / hide
89+
90+
## Spaces
91+
Use only one space after a full stop, not 2.

0 commit comments

Comments
 (0)