[FEAT] Implement Endpoint to UPDATE About Page Content: settable from admin

[thenoblet]

Description

Implement an endpoint to UPDATE the content of the About page, allowing administrators to modify the information efficiently.

---

Purpose

• Enable administrators to update the content of the About page dynamically.

---

Acceptance Criteria

Update About Page Content

• Update the content of the About page with new information provided by administrators.
• Return a success message upon successful update.
• Properly handle scenarios where the update fails.

---

Requirements

Update About Page Content

• Implement PUT /api/v1/content/about endpoint to update About page content.
• Validate incoming content to ensure it meets required criteria.
• Ensure authentication and authorization mechanisms for administrators.
• Handle and return errors gracefully, specifying different error conditions.

---

Expected Outcome

• Implementation of the endpoint to update About page content.
• Clear and appropriate responses for success and error cases.
• Documentation and testing to ensure reliability and functionality.

---

Checklist

1. Update About Page Content

   • [x] Implement PUT /api/v1/content/about endpoint.
   • [x] Validate incoming content and handle errors effectively.
   • [x] Secure endpoint with authentication for administrators.
   • [x] Document endpoint, including request and response formats.

Testing

• [x] Write unit and integration tests covering various scenarios.
• [x] Test successful update operations.
• [x] Test edge cases and error scenarios thoroughly.

Documentation:

• [x] Document the endpoint, including request and response formats.
• [x] Include information on authentication requirements and error handling.

---

Endpoint

Description: Update the content of the About page.
Endpoint: PUT /api/v1/content/about
Authentication: Required
Authorization: Administrators only
Request Body:

{
    "title": "More Than Just A BoilerPlate",
    "introduction": "Welcome to Hng Boilerplate, where passion meets innovation.",
    "custom_sections": {
      "stats": {
        "years_in_business": 10,
        "customers": 75000,
        "monthly_blog_readers": 100000,
        "social_followers": 1200000
      },
      "services": {
        "title": "Trained to Give You The Best",
        "description": "Since our founding, Hng Boilerplate has been dedicated to constantly evolving to stay ahead of the curve."
      }
    }
}

Response (Success):

{
  "message": "About page content updated successfully.",
  "status_code": 200
}

Response (Error: Server Error):

{
  "message": "Failed to update About page content.",
  "status_code": 500
}

Response (Error: Unauthenticated):

{
  "message": "Invalid authentication credentials",
  "status_code": 401
}

Response (Error: Authenticated but Unauthorised):

{
  "message": "You do not have permission to perform this action.",
  "status_code": 403
}

Additional Notes:

• This endpoint is designed to complement the RETRIEVE operation described in the issue #265 .
• Ensuring consistency with the UPDATE operation in issue #265 is crucial. Please review the request and response formats, validation rules, and authentication/authorization mechanisms stated in that issue.
• Consistent error handling is important for a seamless user experience. Align the error messages and status codes with those defined in issue #265
• Documentation and testing should cover both endpoints thoroughly. Please refer to the documentation and test cases of the UPDATE operation to ensure all scenarios are addressed.
• Authentication and authorization are mandatory for this endpoint to restrict access to administrators only. Follow the same security protocols as described in issue #265
• Keep the custom sections flexible and extendable. Future modifications should allow easy addition of new sections without major changes to the structure.

---

Database Schema

Diagram

Link To Diagram

Approved Issue

Link to approved issue: [FEAT] Implement Endpoint to UPDATE About Page Content: settable from admin

[thenoblet]

@markessien, @highb33kay, @buka4rill

An Afterthought (DB schema): Whilst implementing this, I realised it'd be cool to track which admin made changes to the content of the About Page. So, I'll need to extend the database schema and application logic to include user information for auditing purposes.

Is that something I can do, please? The DB and Auth guys are not really coming to through for us. Painful.