TODO.org

[#A] simple auth for server bit?

[#C] how to test it? try on different pages?

https://www.blazemeter.com/blog/6-easy-steps-testing-your-chrome-extension-selenium looks tricky…

[#C] some sort of delayed append logic? e.g. don’t dump immediately and add as subitems?

[#C] or, add menu to extension?

[#C] hmm. if template is specified on client site, it’s easier to dispatch todo vs non-todo etc?..

CNCL not sure, maybe extension press should be default? control it via option?

• State “CNCL” from “TODO” [2022-12-29 Thu 17:41]

[#B] doesn’t look like hotkey working unless you manually rebind.. wtf?

• State “DONE” from “TODO” [2022-12-29 Thu 17:41]

[#D] do not minfy for dev

• State “DONE” from “TODO” [2022-12-29 Thu 17:40]

[#D] make manifest templated so we don’t have to hardcode actions

• State “DONE” from “TODO” [2022-12-29 Thu 17:40]

[#D] production build?

• State “DONE” from “TODO” [2022-12-29 Thu 17:40]

## Packing
After the development of your extension run the command

:

```
$ NODE_ENV=production npm run build
```
Now, the content of `build` folder will be the extension ready to be submitted to the Chrome Web Store. Just take a look at the [official guide](https://developer.chrome.com/webstore/publish) to more infos about publishing.

[#A] adjust permissions… I guess gonna have to make it include /capture endpoint?

[#A] move server to a separate folder, systemd install script

[#A] entering additional information and tags

[#B] circleci?

[#B] release somewhere? not sure if necessary

[#C] post on reddit?

• State “DONE” from “TODO” [2022-12-29 Thu 17:40]

[#B] get rid of kython, run ci for python too?

[#B] docs on using

[#C] update screens and video now that the notification is nicer

[#C] custom capture template?

[#C] make notification configurable or only in case of errors

[#C] motivation

the benefit is that you can also add anything as a backend, e.g. you might be more of markdown fan or todo.txt

[#D] nicer manifest?

unsafe-eval in content security policy??