environment.ts, there is dummy data file placed to mimic the behavior of a back-end.
E.g. Following images shows the data and its structure for slides on the landing page. The data is in JSON format.
E.g. Data is imported in the
page.ts file as
this.service.slides . Here, service is service provider name,
homeData is the JSON data in service
To make the app fully operational you will need to attach a back-end to the app. This will require several additions and you will need the assistance of a back-end developer.
We will provide a glimpse into the things you will require
There are several options when it comes to back-end. Some of the major ones are
Node.js custom back-end
Firebase back-end (node.js) (Read intro blog here)
Django custom back-end
Ruby-on-rails custom back-end
We recommend starting out with Firebase, if you want quick turn-around of features. Firebase is a BaaS platform and comes with a bunch of ready-made functionality, like
As explained in the section above, you will need to replace the Data coming in from individual JSON files with the data coming in from APIs (from your back-end).
You can either keep the same service file for all the data, or you can create individual service files to fetch data for individual pages or features.
To manage the data efficiently, you will need to arrange all API calls, and data manipulation in a single location. You can manage API calls with HttpClient services or firebase functions.