Configuration for Tailwind Integration

[devilkiller-ag]

Summary of Changes

This PR adds configuration for Tailwind CSS

Related Issue

Fixes first task of #179

Checklist

• I have read and followed the project's contribution guidelines, including code style and commit message conventions.
• My code is well-documented, and I've updated relevant documentation.
• I have added or updated test cases to ensure the code's functionality.
• I have tested these changes on my local environment.
• All tests pass, and there are no new linting errors.
• I have reviewed and proofread my code and the changes.
• The branch is up-to-date with the base branch.

Reviewer(s)

@Abhijay007

[Abhijay007]

Hey @devilkiller-ag, I've reviewed the code, and there are a few things that need to be considered. The Initialization of Tailwind to our Docusaurus site looks good to me, as it didn't break our site too much. However, some styling changes seem to have been adopted due to Tailwind, so we need to look into that. For instance, take a look at these screenshots here.

• one the blog page

• on docs pages

This issue needs to be resolved. Most of the custom components appear to be in good shape. To address these concerns, we may need to delve into the styles of custom CSS and adjust them accordingly using Tailwind. While you can incorporate these changes in the same file, I recommend considering a separate file for Tailwind, as demonstrated in the resources I shared earlier.

Let's ensure everything aligns smoothly with our design standards, it will help us in long run to use tailwind effectively.

[devilkiller-ag]

Sure @Abhijay007, I will look into this.

[devilkiller-ag]

Hi @Abhijay007, I have made changes to the heading styling. However, I think I will need to convert the whole custom.css into tailwind, to fix the styling. I am currently doing these changes in a different CSS file. I have changed the heading styling into tailwind in the above commit.

[Abhijay007]

The code changes LGTM. Now, you can work on converting one of the components and create a separate PR for that. Once that's done, we will merge both of these PRs.

[devilkiller-ag]

The code changes LGTM. Now, you can work on converting one of the components and create a separate PR for that. Once that's done, we will merge both of these PRs.

Okay Sure!

[Abhijay007]

closing this as we already have version of it here : #185