Map short/mid term expected Features

[kaioteoi]

Context

• Before defining the Domain Entities of our platform, we must understand what kind of capabilities we understand that The Lodge must provide.

  Detail

• What kind of interface will we provide?
• Website with some search looking features like Wikipedia?
• Will it be as collaborative as Confluence page editing from Atlassian?
• Will it be something like Medium?

  Related issues

  issue #	description
  #2	history issue

[kaioteoi]

We can stick with something closer to Wikipedia functionalities.

• There'll be Posts with information in it, references are important to guarantee the content integrity.
• No comment section, people must come to The Lodge to seek knowledge, not to chitchat.
• Suggestion of content change can be considered, but not mandatory so soon.

[kaioteoi]

So, for the features we'll have:

• Website providing the content with a Wikipedia-like structure. (frontend)
• Suggestion engine for the mid/long term.
• We can consider 3 initial providers of data. Let's begin with multiple providers to understand from the beginning how to deal with multiple source of data. (data pipelines)
  • Wikipedia (filtering by relevant content for us)
  • Riot Games (League of Legends universe)
  • Blizzard
• With the multiple providers in mind, we'll have a base Insert API with 3 plugin Provider engines plugged to it. Working with a plugin-like approach will exercise our development on how to build a service easily extensible to new plugins. (backend)
• Text based search on the website. A parser to deal the text input and a data source that supports text indexing. (backend)

[kaioteoi]

Let's proceed to the next step with these features in mind. We'll now map all the domain entities that will support the main features.