-
Notifications
You must be signed in to change notification settings - Fork 15
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
Migrate from Picocss to Tailwind and Cleanup Frontend Code #5
Comments
/bounty $20 |
💎 $20 bounty • DaytonaSteps to solve:
If no one is assigned to the issue, feel free to tackle it, without confirmation from us, after registering your attempt. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code. Please respect others by working on PRs that you are allowed to submit attempts to. e.g. If you reached the limit of active attempts, please wait for the ability to do so before submitting a new PR. If you can not submit an attempt, you will not receive your payout. Thank you for contributing to daytonaio/devcontainer-generator! Add a bounty • Share on socials
|
/attempt #5 I will install pytailwindcss to generate the css as listed here https://pypi.org/project/pytailwindcss/ Options |
sounds good @AliYar-Khan |
@nkkko thanks ... Also i want to tell that uvloop is not supported in windows. In fact it is not being used in the project as well. So can i remove it ? |
@AliYar-Khan Project for sure would benefit from some optimisation, sure you can remove it if it is not used. |
@nkkko there are some classes on main.py that are being used in main.js. Should I remove them as well? What does this mean ? |
/claim #5 |
💡 @AliYar-Khan submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
/cancel #5 |
Is your feature request related to a problem? Please describe.
The current project utilizes Picocss for styling the frontend. Tailwind CSS provides a more modern, utility-first approach to styling, which can make the codebase cleaner and more maintainable. Additionally, there is some mix of tailwind already in the frontend that needs to be cleaned up.
Describe the solution you'd like
Additional context
Please ensure that all sections in
content.py
are updated to reflect the changes. Below are some specific sections that will need modification:hero_section
generator_section
benefits_section
setup_section
examples_section
faq_section
cta_section
footer_section
Review and update
main.py
and other related files to ensure integration is seamless and effective. Make sure to test thoroughly to maintain the functionality and design consistency.The text was updated successfully, but these errors were encountered: