Browser Use
What it is
The browser path runs the MdWrk client directly in a supported browser. Documents stay local by default, and the workspace remains usable even when you are offline after the app assets have already been cached.
How to start
- Open the MdWrk site.
- Launch the workspace from the primary app action.
- Start writing, previewing, and organizing documents in the browser.
Best fit
- quick access
- personal writing on one machine
- environments where you cannot install local software
- trying editor and renderer behavior before adopting packages
Storage model
Browser use keeps workspace data in browser-managed local storage. That is convenient, but it also means your normal backup and export habits still matter.
When to choose another path
Choose the PWA route when you want a more app-like shell. Choose the local setup route when you need a repo checkout, a controlled local build, or self-managed hosting. Choose standalone modules when you want the reusable package surfaces inside another application.