Configuration for Tailwind Integration

[devilkiller-ag]

Summary of Changes

This PR adds configuration for Tailwind CSS

Related Issue

Fixes first task of #179

Checklist

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

Reviewer(s)

@Abhijay007

[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.

[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 : https://github.com/uptane/uptane.github.io/pull/185