Prompt for the EventSeriesApp

Please create a React-JS application for the EventSeriesModule. The application  has to offer the following views for the user interface: 
    1. ContactRequestView 
    2. ContactTopicView 
    3. EventSeriesView 
    4. NewsArticleView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The ContactRequestView must contain the following fields: 
    - name: ConsentMarketing   type: BOOL 
    - name: ContactTopic   type: ContactTopic 
    - name: CreatedAt   type: DATE 
    - name: Email   type: STRING 
    - name: Message   type: STRING 
    - name: Name   type: STRING 
    - name: PhoneNumber   type: STRING 
    - name: Subject   type: STRING 
The data source for the [ContactTopic] select control should be loaded from the relative URL: 
    "/EventSeriesService/contacttopic"   (HTTP-GET) 
An existing ContactRequest entity should be loaded from the relative URL: 
    "/EventSeriesService/contactrequest/{id}"   (HTTP-GET) 
If a new ContactRequest entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/contactrequest"   (HTTP-POST) 
If an existing ContactRequest entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/contactrequest/{id}"   (HTTP-PUT) 
If an existing ContactRequest entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/contactrequest/{id}"   (HTTP-DELETE)

2. The ContactTopicView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing ContactTopic entity should be loaded from the relative URL: 
    "/EventSeriesService/contacttopic/{id}"   (HTTP-GET) 
If a new ContactTopic entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/contacttopic"   (HTTP-POST) 
If an existing ContactTopic entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/contacttopic/{id}"   (HTTP-PUT) 
If an existing ContactTopic entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/contacttopic/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ContactRequest columns: 
    - column: Email 
    - column: PhoneNumber 
    - column: ContactTopic 
    - column: Subject 
    - column: CreatedAt 
    - column: Message 
    - column: ConsentMarketing 
    - column: Name 
The table should have the title "ContactRequests" und the data must be loaded from the server with the following relative URL: 
    "/EventSeriesService/contactrequest/contacttopic/{id}"

3. The EventSeriesView must contain the following fields: 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: Name   type: STRING 
    - name: StartDate   type: DATE 
An existing EventSeries entity should be loaded from the relative URL: 
    "/EventSeriesService/eventseries/{id}"   (HTTP-GET) 
If a new EventSeries entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/eventseries"   (HTTP-POST) 
If an existing EventSeries entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/eventseries/{id}"   (HTTP-PUT) 
If an existing EventSeries entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/eventseries/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Event columns: 
    - column: ExternalReference 
    - column: TicketUrl 
    - column: DoorOpenTime 
    - column: StartDateTime 
    - column: Organizer 
    - column: EndDateTime 
    - column: Subtitle 
    - column: VenueArea 
    - column: Language 
    - column: Arena 
    - column: Name 
    - column: Description 
    - column: IsCanceled 
    - column: EventSeries 
    - column: IsPostponed 
    - column: EventCategory 
    - column: MinimumAge 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/EventService/event/eventseries/{id}"

4. The NewsArticleView must contain the following fields: 
    - name: Content   type: STRING 
    - name: Event   type: Event 
    - name: IsHighlighted   type: BOOL 
    - name: PublishedAt   type: DATE 
    - name: Slug   type: STRING 
    - name: Teaser   type: STRING 
    - name: Title   type: STRING 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
An existing NewsArticle entity should be loaded from the relative URL: 
    "/EventSeriesService/newsarticle/{id}"   (HTTP-GET) 
If a new NewsArticle entity has been created, the new entity should be posted to the relative URL: 
    "/EventSeriesService/newsarticle"   (HTTP-POST) 
If an existing NewsArticle entity has been updated, the modified entity should be sent to the relative URL: 
    "/EventSeriesService/newsarticle/{id}"   (HTTP-PUT) 
If an existing NewsArticle entity has to be deleted, the following relative URL should be called: 
    "/EventSeriesService/newsarticle/{id}"   (HTTP-DELETE)