From 7ec467e337391efec3ac0abde1b9051675914323 Mon Sep 17 00:00:00 2001 From: Cheng Zhao Date: Mon, 30 May 2016 10:37:02 +0900 Subject: [PATCH] docs: Move the "Packaging Tools" out of "Rebranding" chapter --- docs/tutorial/application-distribution.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/tutorial/application-distribution.md b/docs/tutorial/application-distribution.md index c8ec1f6..4d3e12d 100644 --- a/docs/tutorial/application-distribution.md +++ b/docs/tutorial/application-distribution.md @@ -102,6 +102,14 @@ MyApp.app/Contents You can rename the `electron` executable to any name you like. +## Packaging Tools + +Apart from packaging your app manually, you can also choose to use third party +packaging tools to do the work for you: + +* [electron-packager](https://github.com/maxogden/electron-packager) +* [electron-builder](https://github.com/loopline-systems/electron-builder) + ## Rebranding by Rebuilding Electron from Source It is also possible to rebrand Electron by changing the product name and @@ -118,14 +126,6 @@ This task will automatically handle editing the `.gyp` file, building from source, then rebuilding your app's native Node modules to match the new executable name. -## Packaging Tools - -Apart from packaging your app manually, you can also choose to use third party -packaging tools to do the work for you: - -* [electron-packager](https://github.com/maxogden/electron-packager) -* [electron-builder](https://github.com/loopline-systems/electron-builder) - ### Creating a Custom Electron Fork Creating a custom fork of Electron is almost certainly not something you will -- 2.7.4