Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Employing Domain driven design to building a Digital Health Application using Strapi and Next.js #1522

Closed
1 task done
Gitarackur opened this issue Aug 19, 2024 · 2 comments

Comments

@Gitarackur
Copy link

What is your article idea?

There are numerous articles on Strapi; however, they do not provide design principles or methodologies that can be leveraged to build scalable, strapi-dependent enterprise systems.
This tutorial will present an application on domain-driven design, a famous design pattern methodology in the development of a healthcare appointment application utilizing Strapi and Next.js.

What are the objectives of your article?

  1. Introduction

    • Overview: What is domain-driven design?
    • Benefits of domain-driven design
    • Benefits of using Strapi
  2. Setup

    • Setup the development environment (Node.js, pnpm, yarn).
    • Setup and configuration of a strapi project.
    • Setup of the frontend project
  3. CMS architecture design

    • Create content types for
      • Users
      • Patients
      • Doctors
      • Appointment
    • Establish relationships between content types.
      • Appointment content relationships with patients
      • Appointment content relationships with doctors
  4. Backend with Strapi

    • Create and model content types for users.
    • Set roles and permissions for users (patients, users).
  5. Creating the frontend

    • Abstract business logic application into layers

      • Domain-specific (i.e., patient domain, doctor domain, appointment domain) layer
      • Application layer
      • Service layer (layer responsible for fetching data from Strapi)
      • View Layer (UI, Components Layer)
    • Authentication and authorization

    • Creation of an appointment by a patient.

    • Edit appointment by patient

    • View appointments made by patients.

    • Reject or accept an appointment by the doctor.

  6. Advantages and disadvantages of utilizing the domain-driven design approach

  7. Conclusion

What is your expertise as a developer or writer?

Advance

What type of post is this?

Tutorial

Terms & Conditions

  • I have read the Write for the Community program guidelines.
@Gitarackur
Copy link
Author

Hi @Theodore-Kelechukwu-Onyejiaku,
Please let me know if this topic is a good fit.

@Gitarackur Gitarackur changed the title Employing Domain driven design to building a Digital Health Application using Svelte and Strapi Employing Domain driven design to building a Digital Health Application using Strapi and Next.js Aug 19, 2024
@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator

Hi @Gitarackur ,

Thanks for your time. I am sorry we have something similar already: #1508

Also, we have contents on content design and modeling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants