mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

docs: fix broken link to commit message guidelines (#13233)

Browse source 
* docs: fix broken link  to commit message guidelines

* Fix another broken links
This commit is contained in:
Vlad Hashimoto 2018-06-16 03:43:03 +03:00 • committed by Charles Kerr
parent 1647c12c73
commit a67c992c36
7 changed files with 26 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/tutorial/code-signing.md
View file

@ -1,6 +1,6 @@
# Code Signing
Code signing is a security technology that you use to certify that an app was
Code signing is a security technology that you use to certify that an app was
created by you.
On macOS the system can detect any change to the app, whether the change is
@ -11,23 +11,23 @@ if you don't have, or if your trust level is low will cause security dialogs to
appear when users start using your application. Trust level builds over time
so it's better to start code signing as early as possible.
While it is possible to distribute unsigned apps, it is not recommended.
While it is possible to distribute unsigned apps, it is not recommended.
For example, here's what macOS users see when attempting to start an unsigned app:
![unsigned app warning on macOS](https://user-images.githubusercontent.com/2289/39488937-bdc854ba-4d38-11e8-88f8-7b3c125baefc.png)
> App can't be opened because it is from an unidentified developer
If you are building an Electron app that you intend to package and distribute,
it should be code signed. The Mac and Windows app stores do not allow unsigned
If you are building an Electron app that you intend to package and distribute,
it should be code signed. The Mac and Windows app stores do not allow unsigned
apps.
# Signing macOS builds
Before signing macOS builds, you must do the following:
1. Enroll in the [Apple Developer Program](Apple Developer Program) (requires an annual fee)
2. Download and install Xcode
1. Enroll in the [Apple Developer Program] (requires an annual fee)
2. Download and install [Xcode]
3. Generate, download, and install [signing certificates]
There are a number of tools for signing your packaged app:
@ -74,4 +74,4 @@ See the [Windows Store Guide].
[Xcode]: https://developer.apple.com/xcode
[signing certificates]: https://github.com/electron-userland/electron-osx-sign/wiki/1.-Getting-Started#certificates
[Mac App Store Submission Guide]: mac-app-store-submission-guide.md
[Windows Store Guide]: windows-store-guide.md
[Windows Store Guide]: windows-store-guide.md

2
docs/tutorial/macos-dock.md
View file

@ -1,7 +1,7 @@
# MacOS Dock
Electron has APIs to configure the app's icon in the macOS Dock. A macOS-only
API exists to create a [a custom dock menu](#custom-dock-menu-mac-os), but
API exists to create a custom dock menu, but
Electron also uses the app's dock icon to implement cross-platform features
like [recent documents][recent-documents] and
[application progress][progress-bar].

2
docs/tutorial/windows-taskbar.md
View file

@ -3,7 +3,7 @@
Electron has APIs to configure the app's icon in the Windows taskbar. Supported
are the [creation of a `JumpList`](#jumplist),
[custom thumbnails and toolbars](#thumbnail-toolbars),
[icon overlays](#icon-overlays-in-taskbar-windows), and the so-called
[icon overlays](#icon-overlays-in-taskbar), and the so-called
["Flash Frame" effect](#flash-frame), but
Electron also uses the app's dock icon to implement cross-platform features
like [recent documents][recent-documents] and