experiments in a post-browser web
notes and tasks
+43
+21
TODO.md
+21
TODO.md
···
1
1
# Roadmap
2
2
3
+
## v0.4 - Minimum viable web workbench
4
+
5
+
- [ ] Multi-protocol architecture
6
+
- [ ] Content publishing
7
+
- [ ] Event model
8
+
- [ ] Chaining
9
+
10
+
## v0.3 - Personal daily driver
11
+
12
+
- [ ] Design philosophy write-up w/ driving principles and characteristics
13
+
- [ ] Datastore
14
+
- [ ] Open URLs by default
15
+
- [ ] Page model and user interface
16
+
- [ ] Cmd bar adaptive matching and frecency
17
+
- [ ] Tags + Groups
18
+
- [ ] Notes (vim)
19
+
- [ ] Images
20
+
- [ ] Lists/feeds
21
+
- [ ] Peek:// extensibility model
22
+
- [ ] WebExtension integration for priority only
23
+
3
24
## v0.2 - MVCP (minimum viable concept preview)
4
25
5
26
minimum viable concept preview.
+21
notes/page-model.md
+21
notes/page-model.md
···
1
+
# Peek page model
2
+
3
+
This document describes the design paradigm for a web page lifecycle in Peek..
4
+
5
+
Key pieces:
6
+
7
+
- User actions and decisions
8
+
- Page metadata
9
+
- Windowing model
10
+
- Chaining integration
11
+
- Extensibility
12
+
13
+
## Page loading user actions and decisions
14
+
15
+
As a user, I need to:
16
+
17
+
- Open a web page URL
18
+
- See the web page and interact with it
19
+
- Easily access website information, such as the URL
20
+
- See extended information, such as the SSL cert info
21
+
- See extended information, provided by extensions or customizations
+1
package.json
+1
package.json
···
15
15
"debug": "DEBUG=1 electron-forge start",
16
16
"hot-debug": "nodemon --exec DEBUG=1 electron-forge start",
17
17
"package": "electron-forge package",
18
+
"package:install": "electron-forge package && rm -rf /Applications/Peek.app && cp -r out/Peek-darwin-arm64/Peek.app /Applications/Peek.app",
18
19
"moveapp": "rm -rf ~/Applications/Peek.app && cp -r out/Peek-darwin-arm64/Peek.app ~/Applications/Peek.app",
19
20
"make": "electron-forge make",
20
21
"publish": "electron-forge publish",