kanbanqube 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +287 -0
- package/demo_board.json +321 -0
- package/package.json +46 -0
- package/promo.jpg +0 -0
- package/public/about.jpg +0 -0
- package/public/app.js +2897 -0
- package/public/favicon.svg +11 -0
- package/public/icon_3d.png +0 -0
- package/public/icon_flat.png +0 -0
- package/public/index.html +318 -0
- package/public/styles.css +1554 -0
- package/screenshot.png +0 -0
- package/server.js +1347 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,287 @@
|
|
|
1
|
+
# KanbanQube
|
|
2
|
+
|
|
3
|
+
[](https://sonarcloud.io/summary/new_code?id=mathiasconradt_kanbanqube)
|
|
4
|
+
[](LICENSE)
|
|
5
|
+
[](https://ko-fi.com/mathiasconradt)
|
|
6
|
+

|
|
7
|
+
|
|
8
|
+

|
|
9
|
+
|
|
10
|
+
KanbanQube is a local-first Kanban board app backed by normal files in a vault folder. It is designed for personal or team workflows where the board should live in a regular directory, optionally inside a Git repository, so changes can be versioned and synced with the tools you already use.
|
|
11
|
+
|
|
12
|
+
The app provides lanes, cards, labels, checklists, comments, card covers, file attachments, archived cards, search, and a card-detail view. Uploaded files are stored in an `uploads/` folder, while board data is split into per-object JSON files under `board/` so Git can merge independent card and checklist edits more cleanly.
|
|
13
|
+
|
|
14
|
+

|
|
15
|
+
|
|
16
|
+
## Table Of Contents
|
|
17
|
+
|
|
18
|
+
- [Requirements](#requirements)
|
|
19
|
+
- [Run With npx](#run-with-npx)
|
|
20
|
+
- [Install](#install)
|
|
21
|
+
- [Homebrew](#homebrew)
|
|
22
|
+
- [Build](#build)
|
|
23
|
+
- [Vaults](#vaults)
|
|
24
|
+
- [Board Workflow](#board-workflow)
|
|
25
|
+
- [Git Sync](#git-sync)
|
|
26
|
+
- [Import](#import)
|
|
27
|
+
- [Demo Board](#demo-board)
|
|
28
|
+
- [Identity](#identity)
|
|
29
|
+
- [Attachments And Covers](#attachments-and-covers)
|
|
30
|
+
- [Keyboard Shortcuts](#keyboard-shortcuts)
|
|
31
|
+
- [Development](#development)
|
|
32
|
+
- [Release Automation](#release-automation)
|
|
33
|
+
- [Star History](#star-history)
|
|
34
|
+
|
|
35
|
+
## Requirements
|
|
36
|
+
|
|
37
|
+
- Node.js 18 or newer
|
|
38
|
+
- Git, if you want repository sync
|
|
39
|
+
- A folder to use as your board vault
|
|
40
|
+
|
|
41
|
+
## Run With npx
|
|
42
|
+
|
|
43
|
+
Run KanbanQube against a vault folder:
|
|
44
|
+
|
|
45
|
+
```sh
|
|
46
|
+
npx kanbanqube /path/to/your/vault
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Then open:
|
|
50
|
+
|
|
51
|
+
```text
|
|
52
|
+
http://localhost:3000
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
If no path is provided, KanbanQube uses the current working directory as the vault:
|
|
56
|
+
|
|
57
|
+
```sh
|
|
58
|
+
npx kanbanqube
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
You can choose a different port:
|
|
62
|
+
|
|
63
|
+
```sh
|
|
64
|
+
PORT=4000 npx kanbanqube /path/to/your/vault
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
## Install
|
|
68
|
+
|
|
69
|
+
Global install:
|
|
70
|
+
|
|
71
|
+
```sh
|
|
72
|
+
npm install -g kanbanqube
|
|
73
|
+
kanbanqube /path/to/your/vault
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Local development install from this repository:
|
|
77
|
+
|
|
78
|
+
```sh
|
|
79
|
+
npm install
|
|
80
|
+
npm start -- /path/to/your/vault
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## Homebrew
|
|
84
|
+
|
|
85
|
+
Install from the project tap:
|
|
86
|
+
|
|
87
|
+
```sh
|
|
88
|
+
brew tap mathiasconradt/kanbanqube https://github.com/mathiasconradt/kanbanqube
|
|
89
|
+
brew install kanbanqube
|
|
90
|
+
kanbanqube /path/to/your/vault
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
KanbanQube currently installs as a Homebrew formula for the Node.js command-line server, not as a macOS app cask. If a future app cask or manual macOS app zip is added, the cask should remove the macOS quarantine attribute during install. If you download an app release zip manually and macOS says the app is damaged, run:
|
|
94
|
+
|
|
95
|
+
```sh
|
|
96
|
+
xattr -cr "/Applications/KanbanQube.app"
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
## Build
|
|
100
|
+
|
|
101
|
+
KanbanQube has no frontend build step. The app is plain Node.js plus static browser assets.
|
|
102
|
+
|
|
103
|
+
Validate the server and browser JavaScript:
|
|
104
|
+
|
|
105
|
+
```sh
|
|
106
|
+
npm test
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
Package managers can install it directly because `package.json` exposes the `kanbanqube` executable through the `bin` field.
|
|
110
|
+
|
|
111
|
+
## Vaults
|
|
112
|
+
|
|
113
|
+
A vault is just a directory. KanbanQube stores:
|
|
114
|
+
|
|
115
|
+
```text
|
|
116
|
+
vault/
|
|
117
|
+
board/
|
|
118
|
+
meta.json
|
|
119
|
+
cards/
|
|
120
|
+
lists/
|
|
121
|
+
checklists/
|
|
122
|
+
actions/
|
|
123
|
+
labels/
|
|
124
|
+
members/
|
|
125
|
+
uploads/
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
If `board/` does not exist, KanbanQube creates it automatically. If an older `board.json` exists, KanbanQube imports it into the split `board/` layout the first time it starts. The original `board.json` is left in place but is no longer the active storage file. If `uploads/` does not exist, it is created when the first file is uploaded.
|
|
129
|
+
|
|
130
|
+
Uploaded filenames are made unique while preserving the original name in the UI. For example:
|
|
131
|
+
|
|
132
|
+
```text
|
|
133
|
+
MyExample.png
|
|
134
|
+
MyExample.kbq_20260609T092141981Zb7a252.png
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
The stored filename prevents conflicts. The app still displays `MyExample.png`.
|
|
138
|
+
|
|
139
|
+
## Board Workflow
|
|
140
|
+
|
|
141
|
+
Use the board view for quick work:
|
|
142
|
+
|
|
143
|
+
- Click `+ Add a card` to create a card directly in the lane and type its title inline.
|
|
144
|
+
- Click the board title or lane title to rename it inline.
|
|
145
|
+
- Click a card to open its details.
|
|
146
|
+
- Settings can enable inline editing for existing card titles in board lanes.
|
|
147
|
+
|
|
148
|
+
## Git Sync
|
|
149
|
+
|
|
150
|
+
Git sync is optional. If the vault is a Git repository with a configured `origin` remote, the Sync button is enabled.
|
|
151
|
+
|
|
152
|
+
When Sync runs, KanbanQube:
|
|
153
|
+
|
|
154
|
+
1. Saves pending board changes.
|
|
155
|
+
2. Checks whether anything in the vault repository changed.
|
|
156
|
+
3. Stages and commits all repository changes when needed, including `board/`, `uploads/`, and newly added files.
|
|
157
|
+
4. Runs `git pull --rebase` to bring in remote changes after local work is committed.
|
|
158
|
+
5. Pushes to the configured remote.
|
|
159
|
+
6. Reloads the board from disk so changes pulled from another machine are visible without refreshing the browser.
|
|
160
|
+
|
|
161
|
+
If the vault is not a Git repository, or no remote is configured, Sync stays disabled. You can still use the board locally.
|
|
162
|
+
|
|
163
|
+
Settings includes `Run Git sync in the background (no dialog)`. When enabled, the Sync button runs without opening the sync log automatically. The status text under the app title can still be clicked to open the sync log during or after sync.
|
|
164
|
+
|
|
165
|
+
Recommended setup:
|
|
166
|
+
|
|
167
|
+
```sh
|
|
168
|
+
mkdir my-kanban-vault
|
|
169
|
+
cd my-kanban-vault
|
|
170
|
+
git init
|
|
171
|
+
git remote add origin git@github.com:you/my-kanban-vault.git
|
|
172
|
+
npx kanbanqube .
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
Commit and push once if your remote requires an initial branch:
|
|
176
|
+
|
|
177
|
+
```sh
|
|
178
|
+
git add board
|
|
179
|
+
git commit -m "Initialize KanbanQube board"
|
|
180
|
+
git push -u origin main
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
## Import
|
|
184
|
+
|
|
185
|
+
KanbanQube can import a board export JSON from Settings. Import is only enabled when the current board has no cards. This keeps accidental replacement of an active board from happening inside the app.
|
|
186
|
+
|
|
187
|
+
Imported data is normalized and written into the split `board/` vault layout.
|
|
188
|
+
|
|
189
|
+
## Demo Board
|
|
190
|
+
|
|
191
|
+
The repository includes `demo_board.json`, a sample e-commerce product board with design, UX, frontend, backend, QA, content, and analytics work spread across the default lanes.
|
|
192
|
+
|
|
193
|
+
When a vault has no cards, KanbanQube asks whether to load the demo board. If accepted, the app loads `demo_board.json` and saves it into the current vault using the same path as a normal import.
|
|
194
|
+
|
|
195
|
+
## Identity
|
|
196
|
+
|
|
197
|
+
KanbanQube reads your Git identity from the vault repository first:
|
|
198
|
+
|
|
199
|
+
```sh
|
|
200
|
+
git config --local user.name
|
|
201
|
+
git config --local user.email
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
If local values are missing, it falls back to global Git config:
|
|
205
|
+
|
|
206
|
+
```sh
|
|
207
|
+
git config --global user.name
|
|
208
|
+
git config --global user.email
|
|
209
|
+
```
|
|
210
|
+
|
|
211
|
+
That name is used for comments and activity entries. The settings dialog shows the detected name and email as read-only values.
|
|
212
|
+
|
|
213
|
+
## Attachments And Covers
|
|
214
|
+
|
|
215
|
+
Drop files onto a card or into the card details view to attach them. Files are uploaded into the vault `uploads/` folder.
|
|
216
|
+
|
|
217
|
+
Images can be used as card covers. The cover is stored as a pointer to the attachment in `card.cover.idAttachment`, so removing a cover does not delete the attachment. You can also select another image attachment as the cover.
|
|
218
|
+
|
|
219
|
+
Deleting an uploaded attachment from a card also deletes the physical file from `uploads/` when no other card still references that file.
|
|
220
|
+
|
|
221
|
+
## Keyboard Shortcuts
|
|
222
|
+
|
|
223
|
+
Board view shortcuts are ignored while typing in inputs or while a dialog is open.
|
|
224
|
+
|
|
225
|
+
| Key | Action |
|
|
226
|
+
| --- | --- |
|
|
227
|
+
| Arrow keys | Select cards across lanes and rows |
|
|
228
|
+
| Enter | Open selected card details |
|
|
229
|
+
| Space | Toggle selected card done status |
|
|
230
|
+
| c | Archive selected card |
|
|
231
|
+
| 1-9 | Toggle the matching label by label-list order |
|
|
232
|
+
|
|
233
|
+
## Development
|
|
234
|
+
|
|
235
|
+
Start the app from the repository:
|
|
236
|
+
|
|
237
|
+
```sh
|
|
238
|
+
npm start -- /path/to/your/vault
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
Run checks:
|
|
242
|
+
|
|
243
|
+
```sh
|
|
244
|
+
npm test
|
|
245
|
+
```
|
|
246
|
+
|
|
247
|
+
Main files:
|
|
248
|
+
|
|
249
|
+
- `server.js` - HTTP server, vault storage, upload handling, Git sync
|
|
250
|
+
- `public/app.js` - board UI behavior
|
|
251
|
+
- `public/styles.css` - app styling
|
|
252
|
+
- `public/index.html` - static app shell
|
|
253
|
+
|
|
254
|
+
## Release Automation
|
|
255
|
+
|
|
256
|
+
KanbanQube is prepared for npm and Homebrew releases.
|
|
257
|
+
|
|
258
|
+
For `npx`, the package is published to npm as `kanbanqube` under the npm account `mathiasconradt`. The package exposes the `kanbanqube` executable through `package.json`.
|
|
259
|
+
|
|
260
|
+
Required GitHub secrets:
|
|
261
|
+
|
|
262
|
+
- `NPM_TOKEN` - npm automation token for publishing `kanbanqube`
|
|
263
|
+
|
|
264
|
+
Release flow:
|
|
265
|
+
|
|
266
|
+
1. A non-bot push to `main` runs the version bump workflow.
|
|
267
|
+
2. The workflow bumps the patch version in `package.json` and `package-lock.json`.
|
|
268
|
+
3. It updates the Homebrew formula version and pushes a matching `vX.Y.Z` tag.
|
|
269
|
+
4. The release workflow runs for that tag.
|
|
270
|
+
5. It runs tests, publishes to npm, creates the npm tarball release asset, and updates the Homebrew formula SHA on `main`.
|
|
271
|
+
|
|
272
|
+
After release, users can run:
|
|
273
|
+
|
|
274
|
+
```sh
|
|
275
|
+
npx kanbanqube /path/to/your/vault
|
|
276
|
+
brew install mathiasconradt/kanbanqube/kanbanqube
|
|
277
|
+
```
|
|
278
|
+
|
|
279
|
+
## Star History
|
|
280
|
+
|
|
281
|
+
<a href="https://www.star-history.com/?repos=mathiasconradt%2Fkanbanqube&type=timeline&logscale=&legend=top-left">
|
|
282
|
+
<picture>
|
|
283
|
+
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=mathiasconradt/kanbanqube&type=timeline&theme=dark&logscale&legend=top-left" />
|
|
284
|
+
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=mathiasconradt/kanbanqube&type=timeline&logscale&legend=top-left" />
|
|
285
|
+
<img alt="Star History Chart" src="https://api.star-history.com/chart?repos=mathiasconradt/kanbanqube&type=timeline&logscale&legend=top-left" />
|
|
286
|
+
</picture>
|
|
287
|
+
</a>
|