electron/docs/styleguide.md

79 lines
2.7 KiB
Markdown
Raw Normal View History

2015-08-22 12:07:45 +00:00
# Electron Documentation Styleguide
2015-08-24 12:38:29 +00:00
Find the appropriate section for your task: [reading Electron documentation](#)
or [writing Electron documentation](#).
2015-08-22 12:07:45 +00:00
## Writing Electron Documentation
These are the ways that we construct the Electron documentation.
- Maximum one `h1` title per page.
- Use `bash` instead of `cmd` in code blocks (because of syntax highlighter).
2015-08-24 12:38:29 +00:00
- Doc `h1` titles should match object name (i.e. `browser-window`
`BrowserWindow`).
2015-08-22 12:07:45 +00:00
- Hyphen separated filenames, however, are fine.
- No headers following headers, add at least a one-sentence description.
- Methods headers are wrapped in `code` ticks.
2015-08-24 22:18:40 +00:00
- Event headers are wrapped in single 'quotation' marks.
2015-08-24 12:38:29 +00:00
- No nesting lists more than 2 levels (unfortunately because of markdown
renderer).
2015-08-22 12:07:45 +00:00
- Add section titles: Events, Class Methods and Instance Methods.
- Use 'will' over 'would' when describing outcomes.
- Events and methods are `h3` headers.
- Optional arguments written as `function (required[, optional])`.
2015-08-24 22:18:40 +00:00
- Optional arguments are denoted when called out in list.
- Line length is 80-column wrapped.
- Platform specific methods are noted in italics following method header.
- ```### `method(foo, bar)` _Mac_```
2015-08-22 12:07:45 +00:00
## Reading Electron Documentation
Here are some tips for understanding Electron documentation syntax.
### Methods
2015-08-24 12:38:29 +00:00
An example of [method](https://developer.mozilla.org/en-US/docs/Glossary/Method)
documentation:
2015-08-22 12:07:45 +00:00
---
`methodName(required[, optional]))`
* `require` String, **required**
* `optional` Integer
---
2015-08-24 12:38:29 +00:00
The method name is followed by the arguments it takes. Optional arguments are
notated by brackets surrounding the optional argument as well as the comma
required if this optional argument follows another argument.
2015-08-22 12:07:45 +00:00
2015-08-24 12:38:29 +00:00
Below the method is more detailed information on each of the arguments. The type
of argument is notated by either the common types: [`String`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String), [`Number`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number), [`Object`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object), [`Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array)
or a custom type like Electron's [`webContent`](api/web-content.md).
2015-08-22 12:07:45 +00:00
### Events
2015-08-24 12:38:29 +00:00
An example of [event](https://developer.mozilla.org/en-US/docs/Web/API/Event)
documentation:
2015-08-22 12:07:45 +00:00
---
Event: 'wake-up'
Returns:
* `time` String
---
2015-08-24 12:38:29 +00:00
The event is a string that is used after a `.on` listener method. If it returns
a value it and its type is noted below. If you were to listen and respond to
this event it might look something like this:
2015-08-22 12:07:45 +00:00
```javascript
Alarm.on('wake-up', function(time) {
console.log(time)
})
```