[BUG] make the tailwind styling consistent across the repo

[TenzDelek]

Describe the bug.

in most of the files, we are using hard coded styling like my-[70px], w-[1130px] and etc. this makes the design inconsistent

Expected behavior

consistent preset style that we can use across the website so that consistency is maintain

Screenshots

NA

How to Reproduce

related with Repo Cleanup

🖥️ Device Information [optional]

• Operating System (OS): mac
• Browser: zen
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[aeworxet]

Looping in @Mayaleeeee since this is a UI GitHub issue.

[TenzDelek]

Looping in @Mayaleeeee since this is a UI GitHub issue.

This is a code quality improvement . Hence not design changes.👍

[Mayaleeeee]

Thanks for the clarification, @TenzDelek and @aeworxet

Good catch, if this is strictly refactoring the code to use standard, already established layout rules, it would be a pure engineering task. However, because the conference website doesn't currently have a standardized set of UI tokens, replacing these hardcoded values right now means guessing new layout scales. To ensure we don't cause layout regressions on mobile or desktop, we need an intentional scale to map them to.

For our next bounty cycle next month, I am preparing a microgrant proposal to audit the site and establish a standardized UI Token and Spacing Guide (Layout Grids, Typography Scales, and Spacing Tokens).

Let's hold off on refactoring these arbitrary code values for now; we can use the official tokens as the foundation for this cleanup once the proposal is approved next month!

[TenzDelek]

holding this card until update from @Mayaleeeee regarding the token. thank you

[Mayaleeeee]

Hey @TenzDelek, just a heads-up: I've opened the formal proposal for the spacing token system here:(#1046). Wanted to get it in before this microgrant cycle closes. Once it's done, the blueprint will give you and the team a clear mapping of exactly what to replace these arbitrary values with. Holding this until then is the right call; thanks for being patient!