Staging

[Riyad-Murad]

Summary by Sourcery

Reorganize README documentation to reflect staging updates, refresh UI demo visuals, add deployment snapshots, and refine admin sidebar navigation and layout styling.

Enhancements:

• Replace the admin sidebar’s navigation-page link with a view-providers link and remove duplicate entries.
• Increase left margin in ProviderPowerPrediction CSS layout from 300px to 400px.

Documentation:

• Rename “System Architect Diagram” section to “Component Diagram” and update its image reference.
• Move “Project Box Design” section after Development & Testing and refresh its description and images.
• Rename “Remarkable Features” to “Features Highlight” and adjust landing, client, and provider UI demo sections with updated screenshots.
• Add AWS S3 deployment visuals under the Deployment section.

[sourcery-ai]

Reviewer's Guide

This PR overhauls the project README by renaming and reorganizing sections, updating image paths and tables, adding new screenshots and deployment visuals; it also refines the admin sidebar navigation links and tweaks a CSS layout margin.

File-Level Changes

Change	Details	Files
Reorganized and updated README content	Renamed headings (e.g., “System Architect Diagram”→“Component Diagram”, “Remarkable Features”→“Features Highlight”) Reordered and moved “Project Box Design” into Development & Testing Reworked demo screen tables: updated section titles, swapped and replaced images for landing, client and provider screens, and added new user/profile visuals Inserted AWS S3 deployment screenshot section under deployment	README.md
Adjusted admin sidebar links and icons	Replaced obsolete “Navigation Page” link with “View Providers” Reordered sidebar links to position “View Providers” first Removed duplicate view-providers link entry	amp-client/src/Components/AdminComponents/AdminSidebar/AdminSidebar.jsx
Tweaked layout margin in provider prediction page	Increased left margin from 300px to 400px for centered content	amp-client/src/Pages/ProviderPages/ProviderPowerPrediction/styles.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!

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 @Riyad-Murad - I've reviewed your changes - here's some feedback:

• The README section headings and content have been reorganized but seem inconsistent in naming and ordering—consider standardizing heading titles and grouping related sections for clarity.
• Several image filenames and paths include spaces and URL-encoded characters which may lead to broken links—renaming files to remove spaces and updating paths accordingly will improve reliability.
• Instead of using a hardcoded margin-left: 400px in styles.css, consider leveraging flexbox or grid layouts to ensure responsive alignment across different viewports.

Here's what I looked at during the review

• 🟡 General issues: 2 issues found
• 🟢 Security: all looks good
• 🟢 Testing: 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]

issue (typo): Multiple typos and grammatical error in sentence.

Change 'demostration' to 'demonstration', 'contain' to 'contains', and 'elecrical' to 'electrical'. Also, rephrase 'electrical wire lines' to 'electrical wiring' or 'electrical lines'.

Suggested change

	This box is a demostration of a power room that contain elecrical wire lines and the microcontroller is connected to the circuit.
	This box is a demonstration of a power room that contains electrical wiring, and the microcontroller is connected to the circuit.

[sourcery-ai]

issue: Placeholder and non-descriptive alt texts for deployment images.

Change the second image’s alt text (fsdaf) to a descriptive label (e.g., “S3 Deployed Website”) and refine the first image’s alt text (Landing) to clearly convey the React files in the AWS S3 bucket (e.g., “AWS S3 Bucket React Files”).