chore(menu): detect db update by comparing against prev value

• syncs reload btn visibility b/w tabs
• doesn't trigger when switching profiles if identical

chore: refactor core/client.mjs, sync telemetry opt-in/out across profiles

feat(menu): indicate updates with popup & notification pings

style(menu): set landing tile bg to bg-secondary for consistency with mod tiles

chore: update vendored deps

feat(onboarding): require agreement to privacy policy + ts & cs, add landing tiles

chore(menu): add telemetry toggle

chore!: store config in electron-defined userData folder instead of home folder

• cli can no longer detect where config will be, so config-related cli prompts have been removed
• should avoid file conflicts and enable portable builds
• users can export their data in the more readable .json format from the profiles section of the menu and no longer require direct access to the config file

feat(menu): add sponsorship buttons & perks to banner

style(menu): set min width w/ overflow-x: auto

style(menu): add welcome banner

Are you asking for a CSS variable to change the colour of the title when making a theme, or for a way to change the colour per-title from within the Notion interface?

Match the rest of the themes on notion

Which themes in particular are you referring to?

fix(menu): preserve profile name on import, enabled repeat imports of same file

fix(menu): keyboard triggering of inputs and switches via space/enter, don't trap tab in hotkey input

feat(menu): allow only one theme of each mode to be enabled at a time

feat(menu): display profile upload status as popup

refactor(menu): menu.mjs render functions and components.mjs monolith -> islands/ and components/

BEFORE MAKING A FEATURE REQUEST, PLEASE READ THE CONTRIBUTING GUIDE.

FEATURE REQUESTS THAT DO NOT PROPERLY FILL IN THE TEMPLATE MAY BE IGNORED OR REJECTED. YOU MUST DELETE ALL TEXT ON OR ABOVE THIS LINE BEFORE SUBMITTING.

What makes the feature necessary? Password protecting a page is essential if notion wishes to encourage people to use notion for sensitive information. We all share our laptops with our family and friends once in a while and may not want them to have access to sensitive information.

How would the feature work? Just like we can lock a page, notion could provide a dropdown option to password protect a page.

BEFORE MAKING A FEATURE REQUEST, PLEASE READ THE CONTRIBUTING GUIDE.

FEATURE REQUESTS THAT DO NOT PROPERLY FILL IN THE TEMPLATE MAY BE IGNORED OR REJECTED. YOU MUST DELETE ALL TEXT ON OR ABOVE THIS LINE BEFORE SUBMITTING.

What makes the feature necessary? Password protecting a page is essential if notion wishes to encourage people to use notion for sensitive information. We all share our laptops with our family and friends once in a while and may not want them to have access to sensitive information.

How would the feature work? Just like we can lock a page, notion could provide a dropdown option to password protect a page.

The notion-enhancer runs after a Notion page has loaded, so any password protection that could be done would be superficial at best and easy to circumvent and could mess pretty seriously with your Notion content at worst - my initial testing of password protection last time this feature was requested ended with me losing a significant amount of work.

If you would like to prevent your family and friends from accessing Notion, consider logging out before giving them your device. Even better, if information is sensitive enough to require password protection (e.g. banking details or other passwords), you probably should be using something like 1Password, Bitwarden, Standard Notes, or another password protected vault of some sort to store that information instead of Notion.

perf(load): import all deps at once + wait for load.mjs completion, fix(electron): use ipc for reloadApp

feat(menu): profile deletion via confirmation popup

feat(menu): hotswapped profiles w/out reload

feat(menu): render profile list, create and switch b/w profiles

@hustrjh yes, I think this is close enough to the same issue. #2 is related as well.

I'm focusing on the notion-enhancer at the moment, but once I've pushed out the update for that I'll see what I can do about this.

Very sad that it will never be implemented.

There are multiple ways to do it! Either you can use some custom styling to make the column narrower, or use the workaround @vnavone described above. It's not impossible to have narrower columns, the way you do it just isn't as a toggleable option.

Possibly in future I'll revisit the feature and find a way to do it as a simple switch, but for now, there are already other options.

The mobile view is crippled, you can only see 2 columns when 10 or so would fit

The notion-enhancer doesn't support mobile devices anyway? So I'm not sure how this feature would help you if your issue is with the mobile view.

@MarkGStacey because... it's never going to be implemented, other than in the way that I linked, so there were no more actions to take related to this issue. If an issue is no longer relevant (out of scope, implemented, invalid, etc.) it gets closed so that I know that the ones that are opened do need attention. That's what opening/closing an issue is for: to determine what has been dealt with and what still needs attention.