Skip to content
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

Create improvedcss #1003

Closed
wants to merge 1 commit into from
Closed

Create improvedcss #1003

wants to merge 1 commit into from

Conversation

avaniii21
Copy link

Contributor checklist


Description

Here are some enhancements to improve the readability, maintainability, and efficiency of your Tailwind CSS code:

Group Similar Styles: Consolidate related styles to avoid redundancy, especially for buttons and card styles.

Simplify Responsive Classes: Combine responsive padding and text classes where possible to reduce repetitive code.

Use Variables for Colors and Shadows: This allows easy customization across themes by using Tailwind’s custom configuration options.

Copy link

netlify bot commented Nov 6, 2024

Deploy Preview for activist-org ready!

Name Link
🔨 Latest commit c1690dc
🔍 Latest deploy log https://app.netlify.com/sites/activist-org/deploys/672b7a69a4777b0008d28687
😎 Deploy Preview https://deploy-preview-1003--activist-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

github-actions bot commented Nov 6, 2024

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

  • The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

  • The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

  • The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First PR Commit Check

  • The commit messages for the remote branch of a new contributor should be checked to make sure their email is set up correctly so that they receive credit for their contribution
    • The contributor's name and icon in remote commits should be the same as what appears in the PR
    • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo

@andrewtavis
Copy link
Member

Hi @avaniii21 👋 Sorry but we don't need changes to the given file, and if we did need them that they should go to the current file and not be in a new file that doesn't even have a file extension.

@andrewtavis andrewtavis closed this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants