-
Notifications
You must be signed in to change notification settings - Fork 6
Tailwinds conversions #425
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
base: main
Are you sure you want to change the base?
Conversation
- Replace custom pagination with Pagy bootstrap helper and ensure search filter params persist across pages - Update search ordering to use published_at instead of created_at for topics - Fix password reset page link text expected by tests (Login) and restore test description text - Adjust Searcheable concern year/month scopes to handle blank params safely
…ect and ensure correct ordering for tests
- Ensure state filter respects enums in Searcheable#by_state - Force immediate form submission for month and state selects to avoid stale content in tests
We do not have a surver/privacy policy/terms of use and only registered users can log in, so I removed those links and the card that made it sound like anyone could sign up.
With the old design, we were filtering out archived topics by default.
850fe0c to
a6811e4
Compare
|
I've resolved the conflicts/removed some unnecessary links, still need to fix:
|
This was causing the content of the table to be displayed by default on a green background, making it hard to read.
It wasn't clear to me what it meant when I saw it. Since it is not some kind of code to help idenfity a certain category of topic, I think it is best to remove it to avoid confusion and leave more space for the title.
82f5572 to
5afd19b
Compare
The choose_tag helper is no longer used so I removed it.
65481bf to
ef035af
Compare
| </footer> | ||
|
|
||
| <style> | ||
| @keyframes fade-in-up { |
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.
Is it possible to load this as an asset?
|
|
||
| content_tag :nav, 'aria-label': "Page navigation" do | ||
| content_tag :ul, class: "flex -space-x-px text-sm", style: "list-style: none; margin: 0; padding: 0;" do | ||
| safe_join([ |
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.
Do we need this to connect page with tailwind?
| <%= render "shared/errors", errors: language.errors.full_messages, resource_name: language.class.name %> | ||
|
|
||
| <div style="margin-bottom: 1.5rem;"> | ||
| <%= f.label :name, style: "display: block; font-size: 0.875rem; font-weight: 600; color: #374151; margin-bottom: 0.5rem;" do %> |
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.
Why do we use inline styles and not classes?
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.
I agree, it would be a lot more readable and it would help ensure we have consistent stylings across the app
| }); | ||
|
|
||
| // Smooth scroll for anchor links | ||
| document.querySelectorAll('a[href^="#"]').forEach(anchor => { |
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.
I think this should live in JS module that we can load here
Removing the ability to add new Tags from the Tag index was a conscious decision we took because we didn't want Tags that were not used on any Topics, and at the time it would not have been possible to determine for which language a Tag was meant. Now that we display all Tags regardless of a Topic's language, the language consideration would no longer be an issue, but the stakeholders haven't told us they needed this feature back. See the PR where we removed the ability to add Tags from the Tag index: 8f77030
This means we use overmind instead of foreman.
Users can already see this info on the form or when clicking on "View Topic Details" at the bottom of the form.
Red is generally displayed for destructive actions, but here we were displaying "Edit" in red and "Archive" in orange. Since we are using orange on the Edit forms elsewhere, I've used orange for the Edit button, gray for Archive, and red for Delete. But orange is also often used to indicate a mildly dangerous action, so I wonder if it should be changed to something less alarming, like blue, purple or green. But editing a Topic can indeed be slightly dangerous if the user makes a mistake, so it could also be argued that orange is appropriate.
I also removed the "Danger Zone" as I thought it was a bit confusing that it showed warnings for a Delete feature that does not exist. If the stakeholders need this feature, they will let us know and we can add it at that point.
Admins can already see that information on the form itself or by clicking on the "View Provider Details" button below.
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.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
|
I've asked Claude to help convert a lot of the repetitive inline styles into Tailwind classes, but there are still many files to cover.
|

WIP