danna-aa / tumble

Tumble

Live Site

Background and Overview

Tumble is a social media app project inspired by Tumblr.

Technology

Tumble is implemented using Ruby on Rails on the backend, PostgreSQL database, and React / Redux on the frontend, to create a seamless single-page app experience. Users can make a variety of different content posts, follow other users, like and comment on posts, search tags, and more. Integrated with Amazon Web Services to store uploaded content.

Features

Create Posts

Create text, photo, video, audio, quote, link, and chat posts with tagging

Comments and Likes

Comment on posts and like your favorite posts

Search Functionality

Search tags for keywords to locate and discover specific posts faster

Search parameters utilize active record queries and are filtered in the backend for optimal performance

# posts_controller.rb
def index
    dashboard_posts = current_user.dashboard

    liked_posts = []
    current_user.likes.each do |like|
        liked_posts << Post.find(like.post_id)
    end

    all_posts = Post.all

    case 
        when params[:filter] =='dashboard'
            @posts = dashboard_posts
        when is_string_number?(params[:filter])
            user_id = params[:filter].to_i
            profile_user = User.find(user_id)
            user_posts = profile_user.posts
            @posts = user_posts
        when params[:filter] =='likes'
            @posts = liked_posts
        when params[:filter].present?
            search = params[:filter]
            @posts = Post.joins(:tags).where('tag_body LIKE ?', "%#{search}%")
        else
            @posts = all_posts
    end

end

tumble's Issues

Full Stack Project Checklist

Wiki Page Home

• Is the first page you see upon entering the wiki
• Contains a welcome message
• Contains a link/placeholder for a link to the live page
• All links in the right sidebar should contain each wiki page and link to the correct page
• Correctly formatted
  • each wiki page is listed in bullet points
  • all links route the correct page

Comments

---

MVP List

• Should have 7 MVPs.
  • 3 of those are User Auth, Heroku, and Production README.
  • The other 4 are from the MVP List or they have clarified them with you
• Contains a description sentence of the app
• Includes two to three detailed bullets on functionality and presentation of feature
• At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• Estimates how long it will take the code each MVP
• Correctly formatted
  • MVPs are listed in an ordered list
  • Each MVP is broken down into bullet points

Comments

---

Database Schema

• Contains correct datatypes
• Contains appropriate constraints/details
  • primary key
  • not null
  • unique
  • indexed
  • foreign key
• Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
  • foreign key and table name are lowercased, snake_cased and back_ticked
• Correctly formatted
  • schema is written in a table format
  • the table's name are lowercased, snake_cased and back_ticked
  • the table header column names are bolded
  • columns names are lowercased and snaked_cased and back_ticked

Comments

---

Sample State

• State shape is flat!
• State's keys are camelCased
• All keys within the values in the state are accessible in the schema
• Correctly formatted
  • Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • Top level slices
    • entities
    • session
    • errors (here or in ui)
    • ui (if needed)
  • Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
      • the author username and imageurl for a post. basically any info that the user can't change
      • like count and a boolean on whether the user likes the post instead of a likes slice

Comments

---

Backend Routes

• Contains the following sections: HTML, API Endpoints(Backend)
• Each route has a description
• API Endpoint routes contains wildcard variables written in snake_case
• Routes does not contain superfluous routes
• Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

Comments

---

Frontend Routes

• Frontend routes contains wildcard variables written in camelCase
• Correctly formatted
  • Routes are displayed with inline coding text (backticks)

Comments

User Auth Checklist

User Auth

Functionality

• The main button with logo should link to /
• Has working demo login
• Smooth, bug free navigation

Before Login

• The /login page should not display a link to Log In. Same for /signup
• Going to a random route /#/oweiniouewbrviuwebv should redirect or display a 404 page
• Errors should display for both /signup and /login.
• Errors should clear when moving between /signup and /login.
• Can sign up a user
• Can sign in as a user
• Can log out a user
• Can't sign up with the same username/email
• Pressing enter after filling out the session form should use the form data, not the demo user

After Login

• Should not be able to visit /login or /signup
• Should be able to refresh the page and still be logged in

Style

• The site should look exactly like the actual site
• All relevant elements should have cursor: pointer on hover
• When errors are displayed, most elements should not move around the page (particularly input boxes)
• Remove Redux logger and all console.log()'s from production

Seeds

• Adequate and appropriate seeds