Tutorial for setting up a well-organized consistent efficient Windows menu system
 

Note that this philosophy of mirroring your file system and menus
transcends all common consumer operating systems (excepting iOS).

And it has the same benefits:
a. It makes organization a breeze, and,
b. It makes backup a breeze (e.g., no need to ever use Google Play!)

The proof of concept screenshots below, for example, are on Android, where
Windows was intimately used to create the file-system hierarchy (since
Windows and Linux are both very good at organizing Android file systems).

The point of this example below is that the concept of mirroring your
tasks-based menus to your file system is easy to accomplish, and it pays
vast dividends in that ...
a. The software installer hierarchy (i.e., APKs for Android)
b. Mirrors the software data hierarchy (e.g., sdcard\0data in this example)
c. Which mirrors the menu hierarchy (i.e., the single homescreen below).

Here is a work-in-progress Android homescreen organized into a dozen tasks:
http://img4.imagetitan.com/img.php?image=18_android_apk022.jpg

Here are the filesystem folders for the appdata for those dozen tasks:
http://img4.imagetitan.com/img.php?image=18_android_apk023.jpg

Each task has a folder hierarchy to store the app data & readme logs:
1. time (e.g., calendars, clocks, timers, tasks, stopwatches, etc.)
2. talk (e.g., phone, mail, voip, contacts, sms, etc.)
3. file (e.g., file editors, file browsers, folder shortcuts, etc.)
4. buy (e.g., barcode scanners, calculators, shopping lists, etc.)
5. map (e.g., roadmaps, topomaps, logers, compasses, starmaps, etc.)
6. dock (e.g., phone, sms, contact, mic, dashcam, & camera)
7. audio (e.g., recorders, call recorders, ringtone generators, etc.)
8. pic (e.g., gallery, camera)
9. vid (e.g., youtube clones, youtube, players, etc.)
10. network (e.g., wifi scanners, cell scanners, servers, vpn, etc.)
11. browse (e.g., tor browsers, firefox browsers, chromium browsers, etc.)
12. sys (e.g., app drawer, settings, backup ops, repositories, etc.}

Note that Windows is used to create all these folders, where, just as in
Windows itself, each task-based folder contains a directory for each of the
hundred freeware applications above, which contains whatever you want to
put in that folder for each application.

Either directly, or using links, you might put in each application folder
the application data (e.g., maps or tracks), and a readme file describing
what you've learned about those applications (e.g., tricks, tips, settings,
etc.).

In summary, the philosophy of mirroring your data, installer, and menu
hierarchies pays dividends on most consumer OS platforms (excepting the
Orwellian iOS platform) - where Windows is used efficiently to create the
desired hierarchy, in this case, on Android.