Retake the screenshots that still showed 1.x, and show every README picture here too
Release notes for 2.1.2
Release notes for 2.1.1, and how the login panel picks its colour
Show every screen as it looks in 2.1
Document sidebar skins, the mini rail and the home page
Show the command palette, density modes and the What's new card
Document the command palette, density modes and the 2.0 release
Add Terms of Service and Privacy Policy The Frappe Marketplace listing asks for both, and there was nowhere to point it. Each says only what the code actually does, checked against the source: no outbound request of any kind, no cookies of its own, no external fonts or scripts, and two local-storage values that never leave the browser. Everything the app saves is a Theme Definition or a per-user preference in the site's own database. Terms restate the MIT licence in plain language, along with the as-is warranty, best-effort support through GitHub issues, and what installing and uninstalling actually change. Authored by: abbas0444 <abbasraza0444@gmail.com>
Stop naming a main branch that no longer exists The repository now has exactly two branches, version-16 and version-15, with version-16 as the default. Installation no longer says main is the same code as version-16, and the Developer Guide describes CI as it actually runs: one bench per branch, each asserting its framework version before the tests. Authored by: abbas0444 <abbasraza0444@gmail.com>
Say which branch goes with which Frappe version, and retake the login screenshots Installation now opens with a table pairing Frappe 16 with version-16 and Frappe 15 with version-15, and the get-app line names the branch. Home says the same in one line. The login screenshots come from a site whose panel now names the app rather than a generic ERP, and Login Page says plainly that those words are the administrator's to write. Authored by: abbas0444 <abbasraza0444@gmail.com>
Add the Record Types page, and screenshots for every screen A new page on Theme Definition, User Theme Preference and User Sound Preference: what each holds, what every field means, and the answer to the first question people ask -- no, you do not create these by hand, the studios write them for you. Also fills the gaps in Theme Studio, Theme Settings and Getting Started with pictures of the editor tabs, the two dialogs, the settings form and the avatar menu. Authored by: abbas0444 <abbasraza0444@gmail.com>
Add the Nexus Theme wiki Fifteen pages covering installation, the three studios, Theme Settings, the login page, recipes, troubleshooting, how it works and the developer guide, with screenshots taken from a live ERPNext 16 site. Authored by: abbas0444 <abbasraza0444@gmail.com>
Initial Home page