Formatted CSS files and fixed app's names color

[Laxmilashkare]

• Formatted some CSS files for better Readability
• Changed App's names color as they were merging with the background color making names Invisible

Screenshots-

Summary by Sourcery

Improve the app's readability by formatting CSS files and changing the app names color to ensure they are visible against the background.

Bug Fixes:

• Fix app names color to ensure they are visible against the background.

Enhancements:

• Format CSS files for better readability.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request includes CSS formatting changes for improved readability and a bug fix to ensure app names are visible by adjusting their color.

Class diagram for CSS changes

classDiagram
    class CSS {
        +color: #fff
    }
    note for CSS "Represents the CSS class '.text-white'"

    class AndroidTextBlock {
        +color: #000
    }
    note for AndroidTextBlock "Represents the CSS class '#android .text-block h4'"

    CSS <.. AndroidTextBlock : overrides

Loading

File-Level Changes

Change	Details	Files
Improved code readability by formatting CSS files.	Applied consistent formatting and indentation. Ensured consistent spacing and line breaks.	css/Newbootstrap/bootstrap-theme.min.css css/Newbootstrap/bootstrap.min.css css/bootstrap-theme.min.css css/bootstrap.min.css css/elegant-icons.min.css css/flexslider.min.css css/font-awesome.min.css css/lightbox.min.css
Addressed an issue where app names were blending with the background.	Modified the color of the app names to ensure they are clearly visible against the background. Added a specific style rule for app names within the Android context.	css/theme-lava.css

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Laxmilashkare - I've reviewed your changes - here's some feedback:

Overall Comments:

• It's great you're improving readability by formatting CSS files, but please keep these changes separate from functional changes like the app name color fix.
• Consider using a more specific class name than .text-block h4 to avoid unintended style changes elsewhere.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

Hey @Laxmilashkare - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a more specific CSS selector instead of targeting all h4 elements within the #android ID.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

Hey @Laxmilashkare - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a more specific selector than #android .text-block h4 to avoid unintended style changes.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Laxmilashkare]

@marcoag Could you please review this PR when you have time? Thanks!