-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/write: simplify and streamline new item workflow #130
Comments
I like the idea of this. I would suggest just displaying an optional password input instead of a checkbox. But I'm fine with both! |
Thought about this, too. We would need to indicate, that it’s an optional input/parameter, and explain what the password is meant for, e.g. “access password” or “password protection”; we probably can’t and shouldn’t do this via the placeholder text, as the We could implement/test it as follows:
Not happy with the (optional) placement; but I’m sure we’ll find some good place. |
👍 No strong preference, but I'd choose option (1) with the checkbox. EDIT: @andirueckel mentioned he'd like the checkbox to be a toggle. @aofn Maybe this is the chance to start embedding shadcn/ui components? |
sounds good, also happy with a toggle |
I'll create a draft PR for this |
@aofn Well, I visually kinda like it, but also it feels wrong to use a toggle, i.e. “switch” to show/hide other UI elements. There’s also the “accordion” and “collapsible” components which maybe are more suited for this purpose? |
For our first release candidate, we wanted to simplify and streamline the new item workflow for
/write
. Currently there’s too many options, as #129 describes, hence the following suggestion with conditional<input type="password">
field.Additionally, MyPads allows to change the visibility from public (world-readable if URL is known) to private (password-protected), and vice-versa; as well as changing the password itself. In my opinion, adding this functionality would be more important than adding external public pads via URL—which should be handled similar to other hyperlinks, not /write-specific.
What do you think, @aofn @fnwbr?
The text was updated successfully, but these errors were encountered: