Prompt for the EditorialArticleApp

Please create a React-JS application for the EditorialArticleModule. The application  has to offer the following views for the user interface: 
    1. EditorialArticleView 
    2. EditorialArticlePersonView 
    3. PollVoteView 
    4. TitleTypeView 
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 EditorialArticleView must contain the following fields: 
    - name: AuthorName   type: STRING 
    - name: Body   type: STRING 
    - name: Language   type: Language 
    - name: PublishedAt   type: DATE 
    - name: TitleText   type: STRING 
    - name: UpdatedAt   type: DATE 
The data source for the [Language] select control should be loaded from the relative URL: 
    "/LanguageService/language"   (HTTP-GET) 
An existing EditorialArticle entity should be loaded from the relative URL: 
    "/EditorialArticleService/editorialarticle/{id}"   (HTTP-GET) 
If a new EditorialArticle entity has been created, the new entity should be posted to the relative URL: 
    "/EditorialArticleService/editorialarticle"   (HTTP-POST) 
If an existing EditorialArticle entity has been updated, the modified entity should be sent to the relative URL: 
    "/EditorialArticleService/editorialarticle/{id}"   (HTTP-PUT) 
If an existing EditorialArticle entity has to be deleted, the following relative URL should be called: 
    "/EditorialArticleService/editorialarticle/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EditorialArticleTitle columns: 
    - column: EditorialArticle 
    - column: Position 
    - column: Title 
The table should have the title "EditorialArticleTitles" und the data must be loaded from the server with the following relative URL: 
    "/TitleService/editorialarticletitle/editorialarticle/{id}" 
Add a HTML table to the view with the following EditorialArticlePerson columns: 
    - column: Person 
    - column: Position 
    - column: EditorialArticle 
The table should have the title "EditorialArticlePersons" und the data must be loaded from the server with the following relative URL: 
    "/EditorialArticleService/editorialarticleperson/editorialarticle/{id}"

2. The EditorialArticlePersonView must contain the following fields: 
    - name: EditorialArticle   type: EditorialArticle 
    - name: Person   type: Person 
    - name: Position   type: LONG 
The data source for the [EditorialArticle] select control should be loaded from the relative URL: 
    "/EditorialArticleService/editorialarticle"   (HTTP-GET) 
The data source for the [Person] select control should be loaded from the relative URL: 
    "/PersonService/person"   (HTTP-GET) 
An existing EditorialArticlePerson entity should be loaded from the relative URL: 
    "/EditorialArticleService/editorialarticleperson/{id}"   (HTTP-GET) 
If a new EditorialArticlePerson entity has been created, the new entity should be posted to the relative URL: 
    "/EditorialArticleService/editorialarticleperson"   (HTTP-POST) 
If an existing EditorialArticlePerson entity has been updated, the modified entity should be sent to the relative URL: 
    "/EditorialArticleService/editorialarticleperson/{id}"   (HTTP-PUT) 
If an existing EditorialArticlePerson entity has to be deleted, the following relative URL should be called: 
    "/EditorialArticleService/editorialarticleperson/{id}"   (HTTP-DELETE)

3. The PollVoteView must contain the following fields: 
    - name: PollOption   type: PollOption 
    - name: UserAccount   type: UserAccount 
    - name: VotedAt   type: DATE 
The data source for the [PollOption] select control should be loaded from the relative URL: 
    "/PersonService/polloption"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing PollVote entity should be loaded from the relative URL: 
    "/EditorialArticleService/pollvote/{id}"   (HTTP-GET) 
If a new PollVote entity has been created, the new entity should be posted to the relative URL: 
    "/EditorialArticleService/pollvote"   (HTTP-POST) 
If an existing PollVote entity has been updated, the modified entity should be sent to the relative URL: 
    "/EditorialArticleService/pollvote/{id}"   (HTTP-PUT) 
If an existing PollVote entity has to be deleted, the following relative URL should be called: 
    "/EditorialArticleService/pollvote/{id}"   (HTTP-DELETE)

4. The TitleTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing TitleType entity should be loaded from the relative URL: 
    "/EditorialArticleService/titletype/{id}"   (HTTP-GET) 
If a new TitleType entity has been created, the new entity should be posted to the relative URL: 
    "/EditorialArticleService/titletype"   (HTTP-POST) 
If an existing TitleType entity has been updated, the modified entity should be sent to the relative URL: 
    "/EditorialArticleService/titletype/{id}"   (HTTP-PUT) 
If an existing TitleType entity has to be deleted, the following relative URL should be called: 
    "/EditorialArticleService/titletype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Title columns: 
    - column: Storyline 
    - column: PrimaryTitle 
    - column: NumVotes 
    - column: OriginalTitle 
    - column: TitleType 
    - column: IsAdult 
    - column: Tagline 
    - column: PlotSummary 
    - column: EndYear 
    - column: AverageRating 
    - column: RuntimeMinutes 
    - column: ReleaseDate 
    - column: PosterUrl 
    - column: StartYear 
The table should have the title "Titles" und the data must be loaded from the server with the following relative URL: 
    "/TitleService/title/titletype/{id}"