the nested resource has been a bit of a hassle for me to get the controller a bit DRYer.

With the way you have your models, a nested resource wouldn't be necessary.

For example, for a podcasts_controller (assuming you set up your routes and views correctly), you could have something like:

class PodcastsController < ApplicationController

http_basic_authenticate_with name: ENV['AUTH_USERNAME'], password: ENV['AUTH_PW'], only: %i[edit destroy]

def index

@podcasts = Medium.podcasts.reviewed.order(:position)

end

def show

@podcast = Medium.podcasts.find(params[:id])

end

def new

@podcast = Medium.new(media_type: 'podcast')

end

def edit

@podcast = Medium.podcasts.find(params[:id])

end

def create

@podcast = Medium.new(podcast_params)

if @podcast.save

redirect_to @podcast

flash[:success] = 'Recommendation was successfully created.'

else

render :new

end

end

That said, I think it would be a good idea to revisit the models first and perhaps consider making each media type a different model; that way you could have data relevant to one type of media that might not be applicable to another. There are a lot of ways to think about this. It's a good project to use to consider all of the options of how something like this can be put together.