Added New techstack for CSS

[skullxcode]

📋 Pull Request Description

What does this PR do?

Type of Change

• 📝 New documentation
• ✏️ Documentation improvement (typo, clarity, examples)
• 🐛 Bug fix (non-breaking change fixing an issue)
• ✨ New feature (CLI enhancement, new functionality)
• 🎨 Refactoring (code improvement without changing functionality)
• 📚 New topic/section
• ❓ Interview questions added/improved
• 📄 Cheatsheet added/improved

Related Issue

Closes #(issue number)

Changes Made

• Added New techstack for CSS
• Change 2
• Change 3

Documentation Location (if applicable)

• Files changed: docs/folder/file.md
• New files: docs/css/css-basics.md

✅ Checklist

General

• My code follows the style guidelines of this project
• I have performed a self-review of my own code/content
• I have commented my code/documentation where necessary
• My changes generate no new warnings or errors

Documentation (if applicable)

• All code examples are tested and working
• Code examples include comments explaining key concepts
• Examples show expected output where relevant
• Markdown formatting is correct
• File naming follows conventions (lowercase with hyphens)
• Content is beginner-friendly yet comprehensive
• Links to related topics are included

Code Changes (if applicable)

• My code follows JavaScript best practices
• I have tested the CLI tool locally
• No breaking changes to existing functionality

Commit Messages

• My commit messages are clear and descriptive
• I used conventional commit format (Add:, Fix:, Update:, etc.)

📸 Screenshots (if applicable)

🧪 Testing

How to Test

# Example commands to test
npm link
devdocx javascript/arrays

Test Results

• Tested locally
• All examples work as expected
• CLI commands work properly

📚 Additional Context

🎃 Hacktoberfest

• This PR is part of Hacktoberfest 2025
• I have read and followed the Contributing Guidelines
• I have read and agree to the Code of Conduct

---

Note to Reviewers:

📝 Before Merging

• Documentation is clear and accurate
• Code examples work correctly
• No typos or grammatical errors
• Follows project structure and conventions