Provide common set of preferences out-of-the-box

[DivineDominion]

We could provide .general, .advanced, .updates and maybe .license:

Since almost everyone would have a General preference tab. I wonder if we should ship with a PreferenableGeneral type thing that has all these fields already filled out. My goal is to require the least amount of boilerplate possible to set up a preferences window. Thoughts?

We could do this for Advanced too. And eventually even ship some localizations for those, so users don't have to care about that either.

(Originally posted by @sindresorhus in https://github.com/sindresorhus/Preferences/pull/6)

---

IssueHunt Summary

sindresorhus has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #125 Fix: Ensure the settings window does not become the main window

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[sindresorhus]

I think we should only provide .general and advanced. Most apps only use .general and .advanced, or just .general, with the system icons. There's no common standard/convention for .updates or .license. Most apps I've tried just have update controls in the app menu or in .general. And for license, a lot of apps use and separate window for it.

[IssueHuntBot]

@IssueHunt has funded $60.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[sindresorhus]

Closing as I no longer plan this.