As you see, the get() and get_page() methods are largely generic so that we could create a generic FilterableListView class with these methods in the utils app. Then, in any app that requires a filterable list, we could create a class-based view that extends FilterableListView to handle such scenarios. This extending class would define only the form_class and template_name attributes, and the get_queryset_and_facets() method. Such modularity and extensibility represent two of the key benefits of how class-based views work.