|
5 years ago | |
---|---|---|
.. | ||
api | 6ecf729487 feat: default gtk darkTheme option to nativeTheme.shouldUseDarkColors for better platform support (#20138) | 5 years ago |
development | a53a2aaa45 build: we moved goma to build-tools (#22488) | 5 years ago |
fiddles | f8c4be7caa docs: replace electron.atom.io with electronjs.org in docs/fiddles (#22196) | 5 years ago |
images | 7932e28aa2 docs: Explain notarization, improve code-signing docs (#21373) | 5 years ago |
tutorial | fb1d2ce733 docs: Burn the about document (#22839) | 5 years ago |
README.md | fb1d2ce733 docs: Burn the about document (#22839) | 5 years ago |
breaking-changes-ns.md | 28fb2b7ed5 docs: move breaking changes out of API folder (#21870) | 5 years ago |
breaking-changes.md | b1f4ac00f0 docs: categorize breaking changes (#22834) | 5 years ago |
faq.md | c83f836faf refactor: prefer using app.whenReady() (#21972) | 5 years ago |
glossary.md | 8ba271efba refactor: eliminate brightray (#15240) | 6 years ago |
styleguide.md | 50f4977048 docs: differentiate static/instance class props (#19196) | 5 years ago |
Please make sure that you use the documents that match your Electron version. The version number should be a part of the page URL. If it's not, you are probably using the documentation of a development branch which may contain API changes that are not compatible with your Electron version. To view older versions of the documentation, you can browse by tag on GitHub by opening the "Switch branches/tags" dropdown and selecting the tag that matches your version.
There are questions that are asked quite often. Check this out before creating an issue:
These individual tutorials expand on topics discussed in the guide above.