New Issues

[MihajloVSc]

I added a text document with instructoons for new issue

[schlos]

Code Review

🔴 Critical

• No GitHub issue linked to this PR

✅ Issue Fix Verification

• No issue referenced in PR body
• Checked open issues: Organize file and code structure of CSS #176 mentions "Organize file and code structure of CSS" - this may be related

📋 Code Quality Assessment

Changed File: web/cobrands/sass/_base.scss

Aspect	Status	Notes
CSS Syntax	✅ Valid	No syntax errors detected
Global scope	⚠️ Caution	Removing font-weight: normal from p affects all paragraphs site-wide
Duplicate PR	⚠️ Review	Same change as PR #200 and #202

💡 Suggestions

1. Link to an issue (e.g., "Closes Organize file and code structure of CSS #176" for CSS organization)
2. If intentional, document why this reset is no longer needed
3. Consider consolidating with PRs Responsive #200 and New issue branch #202

✔️ Looks Good

• Minimal, focused change to single property

[schlos]

@MihajloVSc thank you for your interest in contributing! I noticed this PR also contains text files (error.txt, responsive_error.txt, idea.txt) that describe issues rather than using GitHub Issues.

Please use the Issues tab to report bugs and feature requests:

1. Click "New Issue"
2. Describe the problem clearly — what you expected, what happened, and steps to reproduce
3. Submit the issue for discussion

Pull requests should contain only code changes that fix a specific issue or add a feature. Each PR should reference an issue number (e.g., "Fixes #42").

I recommend closing these PRs and:

1. Creating GitHub Issues for each bug you want to report
2. If you want to fix something yourself, opening a new PR with only the relevant code changes
3. Removing the text files — they are not part of the code change

See Creating an Issue for a guide on how to get started.

Let me know if you have any questions! 😊