Add mode READMEs and move Bigscreen app
Add comprehensive READMEs for Bigscreen and Desktop modes, and relocate the Tauri frontend prototype into a new Bigscreen/ subdirectory. This moves package.json/package-lock, src, src-tauri, assets, views, styles and related files into Bigscreen/ to separate the controller-first shell from top-level docs. Update the root README.md to reframe the project as "NebulaOS", describe Bigscreen/Desktop modes, the vision, tech stack and development notes. This reorganizes the repo layout for clearer mode separation and documentation.
This commit is contained in:
Andrew Zambazos
@@ -0,0 +1,271 @@
|
||||
# NebulaOS Desktop Mode
|
||||
|
||||
Desktop Mode is the full Linux desktop experience for NebulaOS.
|
||||
|
||||
It exists because NebulaOS should not only be a console-style interface.
|
||||
It should also be a capable desktop operating system when the user needs one.
|
||||
|
||||
Bigscreen Mode is for controller-first gaming and media.
|
||||
Desktop Mode is for everything else.
|
||||
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
Desktop Mode gives users access to a normal computer environment.
|
||||
|
||||
It is designed for:
|
||||
|
||||
* File management
|
||||
* Web browsing
|
||||
* Productivity
|
||||
* Development
|
||||
* Modding
|
||||
* Troubleshooting
|
||||
* Advanced settings
|
||||
* Desktop gaming
|
||||
* App management
|
||||
* System maintenance
|
||||
|
||||
NebulaOS should feel simple in Bigscreen Mode, but never locked down.
|
||||
|
||||
Desktop Mode is what keeps NebulaOS flexible.
|
||||
|
||||
---
|
||||
|
||||
## Recommended Foundation
|
||||
|
||||
The recommended Desktop Mode foundation is:
|
||||
|
||||
* Linux
|
||||
* KDE Plasma
|
||||
* SDDM
|
||||
* Wayland where possible
|
||||
* X11 fallback where needed
|
||||
* Custom Nebula theme
|
||||
* Custom Nebula session entries
|
||||
|
||||
KDE Plasma is recommended because it is:
|
||||
|
||||
* Highly customizable
|
||||
* Friendly to Linux gaming workflows
|
||||
* Themeable
|
||||
* Mature
|
||||
* Flexible
|
||||
* Suitable for both desktop and handheld layouts
|
||||
|
||||
---
|
||||
|
||||
## Design Direction
|
||||
|
||||
Desktop Mode should feel:
|
||||
|
||||
* Clean
|
||||
* Smooth
|
||||
* Modern
|
||||
* Minimal
|
||||
* Polished
|
||||
* Fast
|
||||
* Familiar
|
||||
* Slightly futuristic
|
||||
|
||||
The design should take inspiration from the clarity and polish of macOS while keeping the flexibility and openness of Linux.
|
||||
|
||||
NebulaOS Desktop Mode should not look like a generic KDE install forever.
|
||||
The long-term goal is to make it feel like a distinct Nebula desktop experience.
|
||||
|
||||
---
|
||||
|
||||
## Desktop Mode Responsibilities
|
||||
|
||||
Desktop Mode should provide:
|
||||
|
||||
* File manager access
|
||||
* Browser access
|
||||
* Terminal access
|
||||
* App launcher
|
||||
* System settings
|
||||
* Development tools
|
||||
* Game modding tools
|
||||
* Desktop game launching
|
||||
* Access to Bigscreen Mode
|
||||
* Advanced troubleshooting tools
|
||||
|
||||
---
|
||||
|
||||
## Relationship to Bigscreen Mode
|
||||
|
||||
NebulaOS has two main sessions:
|
||||
|
||||
```text
|
||||
Nebula Bigscreen
|
||||
Nebula Desktop
|
||||
```
|
||||
|
||||
### Bigscreen Mode
|
||||
|
||||
Used for:
|
||||
|
||||
* Controller navigation
|
||||
* Game launching
|
||||
* TV use
|
||||
* Handheld use
|
||||
* Couch workflows
|
||||
* Simple settings
|
||||
* Console-like experience
|
||||
|
||||
### Desktop Mode
|
||||
|
||||
Used for:
|
||||
|
||||
* Mouse and keyboard use
|
||||
* Advanced configuration
|
||||
* Development
|
||||
* File browsing
|
||||
* Modding
|
||||
* Productivity
|
||||
* Troubleshooting
|
||||
|
||||
Both modes should feel connected, but they should not try to do the same job.
|
||||
|
||||
---
|
||||
|
||||
## Session Switching
|
||||
|
||||
Long-term, NebulaOS should allow users to switch between modes easily.
|
||||
|
||||
Possible flows:
|
||||
|
||||
```text
|
||||
Bigscreen Mode → Power Menu → Switch to Desktop Mode
|
||||
Desktop Mode → App Launcher → Return to Bigscreen Mode
|
||||
Login Screen → Choose Nebula Bigscreen or Nebula Desktop
|
||||
```
|
||||
|
||||
The user should never feel trapped in either mode.
|
||||
|
||||
---
|
||||
|
||||
## KDE Customization Goals
|
||||
|
||||
Desktop Mode customization may include:
|
||||
|
||||
* Nebula global theme
|
||||
* Nebula icon theme
|
||||
* Nebula cursor theme
|
||||
* Nebula wallpaper set
|
||||
* Custom SDDM theme
|
||||
* Custom splash screen
|
||||
* Custom panel layout
|
||||
* Custom application launcher
|
||||
* Custom desktop widgets
|
||||
* Preinstalled Nebula apps
|
||||
* Desktop shortcut for Bigscreen Mode
|
||||
|
||||
---
|
||||
|
||||
## Suggested Desktop Layout
|
||||
|
||||
A possible default layout:
|
||||
|
||||
```text
|
||||
Top panel
|
||||
├── App launcher
|
||||
├── Active window title
|
||||
├── System tray
|
||||
├── Network
|
||||
├── Audio
|
||||
├── Battery
|
||||
└── Clock
|
||||
|
||||
Desktop
|
||||
├── Nebula wallpaper
|
||||
├── Minimal icons
|
||||
└── Optional widgets
|
||||
|
||||
Dock or bottom panel
|
||||
├── Browser
|
||||
├── Files
|
||||
├── Terminal
|
||||
├── Settings
|
||||
├── Nebula Bigscreen
|
||||
└── Nebula Library
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Visual Identity
|
||||
|
||||
Desktop Mode should share visual DNA with Bigscreen Mode.
|
||||
|
||||
Shared elements may include:
|
||||
|
||||
* Nebula gradients
|
||||
* Deep blue and purple tones
|
||||
* Soft glass panels
|
||||
* Rounded corners
|
||||
* Subtle glow
|
||||
* Clean typography
|
||||
* Space-inspired wallpapers
|
||||
* Calm animation
|
||||
* Consistent icon language
|
||||
|
||||
Desktop Mode should be calmer and more practical than Bigscreen Mode, but still recognizably Nebula.
|
||||
|
||||
---
|
||||
|
||||
## System Tools
|
||||
|
||||
Desktop Mode may eventually include Nebula-specific tools such as:
|
||||
|
||||
* Nebula Control Center
|
||||
* Nebula Update Manager
|
||||
* Nebula Library desktop app
|
||||
* Nebula Browser
|
||||
* Nebula Store
|
||||
* Nebula Settings bridge
|
||||
* Nebula account/profile manager
|
||||
* Nebula system diagnostics
|
||||
|
||||
---
|
||||
|
||||
## Development Goals
|
||||
|
||||
Initial Desktop Mode goals:
|
||||
|
||||
* Pick KDE Plasma as the base
|
||||
* Create a Nebula desktop theme
|
||||
* Create a Nebula SDDM login theme
|
||||
* Add Bigscreen and Desktop sessions
|
||||
* Add a launcher shortcut back into Bigscreen Mode
|
||||
* Keep normal Linux tools available
|
||||
* Avoid breaking standard KDE functionality
|
||||
|
||||
---
|
||||
|
||||
## What Desktop Mode Should Avoid
|
||||
|
||||
Desktop Mode should avoid:
|
||||
|
||||
* Removing normal Linux functionality
|
||||
* Hiding important system tools
|
||||
* Making KDE harder to use
|
||||
* Becoming too console-like
|
||||
* Depending on Bigscreen Mode to function
|
||||
* Locking users into one workflow
|
||||
|
||||
Desktop Mode should be powerful, normal, and clean.
|
||||
|
||||
---
|
||||
|
||||
## Success Criteria
|
||||
|
||||
Desktop Mode is successful when:
|
||||
|
||||
* Users can use NebulaOS like a normal Linux desktop
|
||||
* KDE feels visually integrated with NebulaOS
|
||||
* Bigscreen Mode can be launched easily
|
||||
* Advanced settings are accessible
|
||||
* Development and troubleshooting are possible
|
||||
* The desktop feels polished instead of temporary
|
||||
* The system still feels like one unified OS
|
||||
Reference in New Issue
Block a user