Prompt for the ConferenceRoomApp

Please create a React-JS application for the ConferenceRoomModule. The application  has to offer the following views for the user interface: 
    1. ConferenceEquipmentView 
    2. ConferenceRoomView 
    3. ConferenceRoomEquipmentView 
    4. LegalDocumentView 
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 ConferenceEquipmentView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing ConferenceEquipment entity should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceequipment/{id}"   (HTTP-GET) 
If a new ConferenceEquipment entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceRoomService/conferenceequipment"   (HTTP-POST) 
If an existing ConferenceEquipment entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceRoomService/conferenceequipment/{id}"   (HTTP-PUT) 
If an existing ConferenceEquipment entity has to be deleted, the following relative URL should be called: 
    "/ConferenceRoomService/conferenceequipment/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ConferenceRoomEquipment columns: 
    - column: ConferenceEquipment 
    - column: Quantity 
    - column: ConferenceRoom 
The table should have the title "ConferenceRoomEquipments" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceRoomService/conferenceroomequipment/conferenceequipment/{id}"

2. The ConferenceRoomView must contain the following fields: 
    - name: Capacity   type: LONG 
    - name: Description   type: STRING 
    - name: Floor   type: STRING 
    - name: Name   type: STRING 
    - name: RoomNumber   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing ConferenceRoom entity should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceroom/{id}"   (HTTP-GET) 
If a new ConferenceRoom entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceRoomService/conferenceroom"   (HTTP-POST) 
If an existing ConferenceRoom entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceRoomService/conferenceroom/{id}"   (HTTP-PUT) 
If an existing ConferenceRoom entity has to be deleted, the following relative URL should be called: 
    "/ConferenceRoomService/conferenceroom/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ConferenceBooking columns: 
    - column: Description 
    - column: ConferenceRoom 
    - column: Customer 
    - column: EndDateTime 
    - column: Title 
    - column: StartDateTime 
    - column: Status 
    - column: AttendeeCount 
    - column: CreatedAt 
The table should have the title "ConferenceBookings" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/conferencebooking/conferenceroom/{id}" 
Add a HTML table to the view with the following ConferenceRoomEquipment columns: 
    - column: ConferenceEquipment 
    - column: Quantity 
    - column: ConferenceRoom 
The table should have the title "ConferenceRoomEquipments" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceRoomService/conferenceroomequipment/conferenceroom/{id}"

3. The ConferenceRoomEquipmentView must contain the following fields: 
    - name: ConferenceEquipment   type: ConferenceEquipment 
    - name: ConferenceRoom   type: ConferenceRoom 
    - name: Quantity   type: LONG 
The data source for the [ConferenceEquipment] select control should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceequipment"   (HTTP-GET) 
The data source for the [ConferenceRoom] select control should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceroom"   (HTTP-GET) 
An existing ConferenceRoomEquipment entity should be loaded from the relative URL: 
    "/ConferenceRoomService/conferenceroomequipment/{id}"   (HTTP-GET) 
If a new ConferenceRoomEquipment entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceRoomService/conferenceroomequipment"   (HTTP-POST) 
If an existing ConferenceRoomEquipment entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceRoomService/conferenceroomequipment/{id}"   (HTTP-PUT) 
If an existing ConferenceRoomEquipment entity has to be deleted, the following relative URL should be called: 
    "/ConferenceRoomService/conferenceroomequipment/{id}"   (HTTP-DELETE)

4. The LegalDocumentView must contain the following fields: 
    - name: Content   type: STRING 
    - name: EffectiveFrom   type: DATE 
    - name: LastUpdated   type: DATE 
    - name: Slug   type: STRING 
    - name: Title   type: STRING 
    - name: VersionLabel   type: STRING 
An existing LegalDocument entity should be loaded from the relative URL: 
    "/ConferenceRoomService/legaldocument/{id}"   (HTTP-GET) 
If a new LegalDocument entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceRoomService/legaldocument"   (HTTP-POST) 
If an existing LegalDocument entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceRoomService/legaldocument/{id}"   (HTTP-PUT) 
If an existing LegalDocument entity has to be deleted, the following relative URL should be called: 
    "/ConferenceRoomService/legaldocument/{id}"   (HTTP-DELETE)