drinkyouroj / ttt Goto Github PK

Create Repositories for models which yet to have interfaces made.

1. Follow Model
   1. Generate the Repository for Follow model (you can look at the examples in the "repositories" folder)
      1. You can look for common functionality within the FollowLogic.php file in the applogic folders.
      2. You can also find common Follow queries in ProfileController, and Follow REST controllers
      3. You can find all places where we use "Follow::" to find all use cases within the codebase.
   2. Also, apply the repository changes to the applogic/followlogic.php file
2. Like Model
   1. Create a repository for the like model.
   2. Generate Applogic Facade for the Like model and look for common functions which require additional processing outside of model based interaction.
3. Favorite Model
4. Repost Model

The profile evolved over time in different directions. This refactoring requires some group discussion before hand as what is displayed in the user profile vs user feed are not 100% clear.

Combine REST/JSON/AJAX controllers so that they're not in as many files. Currently we have 19 REST controllers, we can do better than that.

This mostly pertains to the contenteditable system.
A lot WYSYWIGs use an iFrame in combination with the contentEditable property to get the work done. We need to develop this as part of our template system in all of our inputs.

In order to decrease overhead and to decrease some needs, we should use mongo or other key-value store types to store some relationships (likes, follows, etc).

Below are some likely targets for conversion:

• Likes
• Favorites
• Reposts
• Followers
• Comments

As Solr doesn't scale as well as ElasticSearch, we would like to transfer all search duties to ES.
Below is the PHP library for ElasticSearch.
https://github.com/elasticsearch/elasticsearch-php