Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6793509
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T18:06:32+00:00 2026-05-26T18:06:32+00:00

I have a blog with posts in multiple categories. I’d like to give each

  • 0

I have a blog with posts in multiple categories. I’d like to give each category an individual landing page that lists all of the bog posts in that category.

What is the appropriate way to generate the routes and controller actions for each of these landing pages? Would it violate the spirit of REST to create multiple index-esque actions (one action per category) in my posts controller? If so, how else should I do it?

For example, my blog might have two categories, “Music” and “Movies”.

GET /posts/ # would list all posts.

GET /music/ # would list all posts in the "Music" category.

GET /movies/ # would list all posts in the "Movies" category.

Apologies if this question has an obvious answer, or if I’m asking the wrong question entirely. I’m new to both Rails and REST and I’m trying to understand the best way to structure applications.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T18:06:33+00:00Added an answer on May 26, 2026 at 6:06 pm

    I’m not sure it’s totally in REST spirit (i do not fully understand it yet), so i’ll leave that part of the question to someone else. As the collection method exists to extend RESTful routes, i assume that it is permitted as long as you don’t abuse of it.
    I don’t think, though, that having routes with no “/posts/” prefix is a good thing, because it would induce that the “/music/” path for instance relates to a completely different resource.

    you can do something like this :

    (in routes.rb)

    resources :posts do
       collection do
         get 'music'
         get 'movies'
       end
    end
    

    … and then add index-like actions to your controller, e.g.:

    def music
      @posts = Post.where( category: 'music')
      render :index
    end
    

    if you have a limited and constant set of categories, this can be DRYed up this way:

    class Post < ActiveRecord::Base
      CATEGORIES = [:music,:movies,:art,:jokes,:friends,:whatever].freeze
    end
    
    class PostsController < ApplicationController
      Post::CATEGORIES.each do |category|
        eval <<-INDEX_LIKE_ACTIONS
          def #{category}
            @posts = Post.where( category: '#{category}' )
            render :index
          end
        INDEX_LIKE_ACTIONS
      end
    end
    
    resources :posts do
       collection do
         Post::CATEGORIES.each {|category| get category.to_s}
       end
    end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a landing page on rails with blog style posts. Since it's the
Say that I have many blogs, and each blog has_many posts. These are stored
I have a team site blog with many posts that I wish to export.
In a blog in Rails I want to have paths like http://mydomain.com/posts/28383/comments#21 This is
I´m adding facebook like buttons to my wordpress-page. On single.php, for each blog post
I've seen a number of blog posts, and have experienced for myself, that Mercurial
Lately I have seen a lot of blog posts concerning how to build loosely
What libraries and/or packages have you used to create blog posts with code blocks?
So! Basically I have a database with a load of blog posts, these are
I like the layout that Facebook Timeline has with the staggered two column posts.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.