[stphschne]

This PR fixes #2482

Implemented changes:

• Change 1: Added console.css
• Change 2: Added MainWindowView.css
• Change 3: Added ConsoleView.css

---

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

1.Run AppLauncher.java. Styling should stay the same.

---

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat and not feature/921 fixed setup.bat).
  If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labelled
  with internal
• You have not changed any dependency in pom.xml files or otherwise if runtime dependencies changed,
  you have updated our LICENSE.adoc
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

Checklist for tool commandlets

Have you added a new «tool» as commandlet? There are the following additional checks:

• The tool can be installed automatically (during setup via settings) or via the commandlet call
• The tool is isolated in its IDEasy project, see Sandbox Principle
• The new tool is added to the table of tools in LICENSE.asciidoc
• The new commandlet is a command-wrapper for «tool»
• Proper help texts for all supported languages are added here
• The new commandlet installs potential dependencies automatically
• The variables «TOOL»_VERSION and «TOOL»_EDITION are honored by your commandlet
• The new commandlet is tested on all platforms it is available for or tested on all platforms that are in scope of the linked issue

Checklist for GUI contributions

Did you make user-facing changes to the GUI? There are the following additional checks:

• You followed the ui-contribution-process.adoc and ui-structure.adoc
• The UI changes are designed in the Figma project and the design was approved in the team review
• You have added screenshots of the UI changes to the PR description

[coveralls]

Coverage Report for CI Build 40330319020

Warning

No base build found for commit 98873f9 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 75.096%

Details

• Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	19769
Covered Lines:	15498
Line Coverage:	78.4%
Relevant Branches:	8793
Covered Branches:	5951
Branch Coverage:	67.68%
Branches in Coverage %:	Yes
Coverage Strength:	3.37 hits per line

---

💛 - Coveralls

[samuelkos17]

Thanks for starting the work on improving our css styling. I have a few things that need to be changed:

• The stylesheets are misplaced, we have a seperate style subdirectory for css files
• The rest can be seen on my comments on the specific files.

Furthermore I want to ask if you found every hard-coded css and replaced it with the .css files?