Article Publishing Endpoints

[Dufuna-Fem]

A publishing house wants to create a web app to manage their content (publishing, editing, etc). As part of their database setup, there is an articles table in the database which has columns (id, title, description, status, created_by, created_at). The created_by is a foreign key that references the admin table with columns (id, name, email_address, created_at).
Articles are created by an admin and new articles have a default status value of unpublished.

As the Tech resource of the publishing house you have been tasked with creating;

1. An endpoint to create a new article.
2. An endpoint to update an existing article.
3. An endpoint to delete an existing article.
4. An endpoint to publish an unpublished article.
5. An endpoint to show all published articles
6. An endpoint to retrieve just a single article
7. The response for 3 above should be

{
     "status": "success",
     "message": "This article was successfully deleted"
}

8. The response for others (1,2,4 - 6) should be similar to the Example Response as seen here
9. Submit your code and create a .txt file and place the link to the documentation there Here's a guide on how to create an API documentation
   
10. Note, you are not to push the following along your code : vendor, composer.lock and .env. Kindly place then in a .gitignore file. For .env file, push a .env.sample file instead