Thanks for the positive feedback, and yeah, development has been slow for a while. Sorry about that.
About a year ago my small little business went from being a two person business to one person… coupled with me having some time away travelling has resulted in non-paying work like PushType dropping down the priority ladder a few levels.
We’ve got several active clients depending on PushType so it’s definitely not abandoned, but over the last year+ I’ve just had to limit my work on PushType to just keeping it updated with new Rails releases.
In response to your suggestions:
YES! That is on the roadmap above, and honestly the only reason it hasn’t been worked on yet is because I haven’t fully wrapped my head around how you correctly index a Postgres JSONB field to ensure a flexible and performant search feature, and how we’d expose database indexing to site developers so they can easily enable search on their content, without having to know their B-trees from their GiSTs.
This is an important feature and honestly I felt like I needed some help on it, so if this is something you wanted to contribute I’d be more than happy for you to work on it.
I currently implement hidden fields by manually adding store accessors to the internal json field, eg:
store_accessor :field_store, :my_hidden_field
The above is pretty easy, but I agree there would be some value to create a dedicated field type so developers can use the syntax they expect.
field :my_hidden_field, :hidden
Polymorphic relation fields
Can definitely see the use case though, so would be happy to see this.
PushType already has a concept of unexposed nodes, which hides the content from the front end, but the nodes can still be managed in the CMS. But I think you mean records that would even be hidden from the CMS?
One of the principles I’ve tried to stick to is that PushType should be your CMS and then get out of your way. We shouldn’t recreate stuff Rails already excels at for instance. In this case I think using a standard model is the way to go. I also quite like the notion that PushType could be a way for new developers to build simple sites in Rails with minimal effort, and then introduce them to the framework underneath. Seems a better way than some CMS’s that end up trying to be the framework.