bgjug / website Goto Github PK

Crate ArticleService REST endpoint providing following backend functionalities:

• Add new article (POST /articles)
• Update existing article (PUT /articles). If id is null or such article does not exist, create it
• Delete article (DELETE /articles/{id})
• Get article by its ID (GET /articles/{id})
• Get all articles (GET /articles). This should not return the whole Article entities, but rather part of them - their ID and their title. They should be sorted by day (descending)

Out of scope for this task:

• Providing UI
• Some more sophisticated functionalities like better finders and paging for example

We should upgrade to quarkus 1.0 ?

I will create another issue for react.

Create page for session submissions similar to the one in the old site: https://jug.bg/%D0%BF%D1%80%D0%B5%D0%B4%D0%BB%D0%BE%D0%B6%D0%B8-%D1%82%D0%B5%D0%BC%D0%B0/

Create admin panel with section for:

• managing CFP (call-for-paper) submissions;
• managing articles (created from the JUG 3.0 site);
• manages blog aggregation
• manages users;
• manages JUG sponsors & partners

• As suggested use the Angular 2.0 webpack starter to quick start with AngularJS 2.0: https://github.com/AngularClass/angular2-webpack-starter
• Incorporate the site design with the Angular 2.0 code structure
• describe the structure and the deployment of the UI during development purposes

The idea is to create a JS layer for interaction with the REST services exposed by the JavaEE backend.

Please please please :) can u upgrade the react and webpack ?

:) we have hard time using any npm module with the current react and webpack version :(

Make sure that the PageService REST endpoint provides following backend functionalities:

• Add new page (POST /pages)
• Update existing page (PUT /pages). If id is null or such page does not exist, create it
• Delete page (DELETE /pages/{id})
• Get page by its ID (GET /pages/{id})
• Get all pages (GET /pages). This should not return the whole Page entities, but rather part of them - their ID and their title

Out of scope for this task:

• Providing UI
• Some more sophisticated functionalities like better finders and paging for example

The idea is to have a page similar (but preferrably UI-richer) to the old one: https://jug.bg/%D1%81%D1%8A%D0%B1%D0%B8%D1%82%D0%B8%D1%8F/

The idea is to create a separate menu for creation of articles in the JUG 3.0 website using a wiki editor. The resulting markup will be persisted over a web service to MySQL.

Create blog aggregator page similar to:
https://jug.bg/category/aggregated/