-
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 workflow #133
base: main
Are you sure you want to change the base?
Conversation
…ending on selection. Add headline to component
…ew pad workflow directly.
sort etherpad translations alphabetically and add translation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
return ( | ||
<form | ||
className="mb-8 [&>*+*]:mt-4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of using this selector, how about adding a mt-4
to every component below? I think that would be the more correct "Tailwind"-approach.
@@ -25,6 +20,16 @@ import logger from '@/lib/Logging'; | |||
import { isMyPadsApiEnabled, path as etherpadPath } from '@/lib/Etherpad'; | |||
import { useMatrix } from '@/lib/Matrix'; | |||
import { useAuth } from '@/lib/Auth'; | |||
import CreateNewPad from './actions/CreateNewPad'; | |||
|
|||
const Header = styled.header` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use Tailwind instead of making these two new styled components?
closes #130