Add cabin / cottage as a property type #1658
Reference in New Issue
Block a user
Delete Branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hope you would consider adding an option for cabins :) Open for suggestions on naming.
@eithe Thanks for the suggestion! How does this different from "Single Family Home"? The purpose of the types isn't so much to list every possible structure type, but rather the purpose.
Thanks for the response! I understand where you’re coming from.
For me, the existing 'Single Family Home' doesn’t feel like the right fit for cabins, since I associate 'Home' more with a primary residence. Cabins, on the other hand, are often seen as vacation retreats, seasonal properties, or cottages, which don’t quite align with the concept of a 'home.' I think having 'Cabin' as an option could better reflect this distinction, and especially that they have a different purpose; it's not about the structure type.
Having said that this was just something I thought of when I looked at the list of properties in the UI and both my house and cabin was categorized as the same thing, which just looked a bit weird to me since I consider them different entity types :)
I also want to add that I really appreciate how focused and streamlined Maybe is in general — it's a strength to avoid having too many unnecessary options. I completely understand the need to strike a balance between flexibility and simplicity!
@eithe would
second_homeorvacation_propertywork here?"Cabin" feels too specific to introduce, but I'd agree that we're missing a category for these "second home" type properties, which I'd assume is common enough for our users to consider. The way I'm categorizing in my head would be:
single_family- a primary residence, standalone propertyinvestment- a secondary residence that is primarily for incomevacation- a secondary residence that is primarily for leisureYes.
Open for votes, but "Second home" (
second_home) feels like it is the most general here and probably our best option.@@ -6,7 +6,8 @@ class Property < ApplicationRecord[ "Multi-Family Home", "multi_family_home" ],