vulpress / app-vulpress Goto Github PK

Implement a service capable of storing jpg, png files to the file system, identified by a unique key (which can be the stored filename. Images should be stored with a reasonable compression with a maximum file size limit (let's say 1MB).

Investigate whether images stored should have a descriptor present in the database (storing information like uploader, upload date, original filename and maybe tags associated with the image).

create dialog for category creation and connect it to the backend

• #66
• #40
• #42

article/category title of Παρακαλώ is normalised to CF%80%CE%B1%CF%81%CE%B1%CE%BA%CE%B1%CE%BB%CF%8E to ensure URL safety. Make it normalise into parakalw instead

Extra columns:

• email for sending verification emails (if they don't match the username)
• verified to check if they completed email verification

When a user registers, they start out with inactive == true and verified == false.
Verification flips both flags.
If both flags are true, this means a banned user!

• #4
• #63
• #64
• #65

• #70
• #71 (app started, login, login failure, upload, move, delete, create)
• #72

• BE - #35
• BE - #36
• BE - #37
• API - #38
• FE - #39
• FE - #40
• FE - #41
• FE - #42

Schedules is a special kind of document describing an approximately weekly business schedule.

It has some metadata (uploader, creation date, title, valid from, valid until, additional comments) and a list of ScheduleEvents: these consist of a date-time, a title, and an event type. The event type may be only a string for now, think about refining it to an enum.

Create the relevant database tables, repository class and service class

• BE - #56
• API - #57
• FE - #58
• FE - #59

• #67
• #68
• #69

the service accepts an AuthenticationRequest and returns Created or Conflict. Username must be a valid e-mail.

• #8
• #7

Facilitate uploading images and tagging them.

• deleteCategory already exists to move all articles of a category to sys_archive
• create deleteArticle
• create moveArticle

Define a document table containing title, author, date of creation. A list of detail objects representing paragraphs or an outside reference for locating the object containing the documents paragraphs. Paragraphs should have three types for now - 'section-title', 'illustration' and 'text'.

Create the relevant entity record, a JDBC repository and a service class for managing the above documents.

Create an init script loading the dev database with mock document data.

RESTful API definition for serving articles and schedules

• #60
• #3
• #9
• #61
• #62

• login and logout
• hamburger responding to login state
• app title is now a link

title

• #27
• #28
• #29

Should have the following methods:

• sendVerificationMail(RegistrationAttempt) ?
• sendPasswordResetMail(User) ?

View and endpoints for uploading a Word document serving as an article and previewing the parsed result.

high-level specification for views and their features

endpoints:

• /auth/register - called when clicking 'Register'
• /auth/verify - called when clicking the button in the e-mail
• /auth/resetPass - called for forgotten password

parse uploaded Word documents using Apache POI into articles, ready to be saved into the database.