The Future of Processwire: The "module" approach

[jan]

Hi everybody,

and sorry for my bad english in advance…

I work often with ProcessWire, and I'd like to share my thoughts about some characteristics of ProcessWire that make work hard sometime.

My thoughts are mostly based on the idea of making ProcessWire more flexible, but preserving it's simplicity. I think everybody who's working on websites daily, will recognize the problems I describe here. (I think it's got to do a lot with that thing "responsive layout" )

So I made a short presentation, which should be seen as a first step. I'm really looking forward to your feedback, community.

(Presentation is attached as PDF at bottom of post).

If you have any questions, please ask me. I'm also happy about other ideas, how to solve the problems described. Thank you!

Presentation as PDF:

ProcesswireFuture.pdf

[LostKobrakai]

There where already lots of other topics about handling content-blocks. Also please have a look at PageTableExtended.

[diogo]

Tell me if I understood it all wrong, but what you are describing here is the pageTable field. Did you have a look at pageTable Extended? It comes even closer visualy to what you described. 

[mr-fan]

Like on many other things the "future" is a little bit hidden in the "past"....with processwire, too

some search on this topic gave me a really interesting reading of this kind of block/modules/contentpart topic...in this forum are some really cool treasures to dig...

threat: (the whole threat is worth reading linked to the interesting stuff)

https://processwire.com/talk/topic/4189-flexibility-in-page-design/page-3

module:

https://github.com/somatonic/BlocksContent

BUT the best post of this whole discussion comes from OWZIM:

https://processwire.com/talk/topic/4189-flexibility-in-page-design/page-4#entry63924

PageTable is the missing link and Extended is for better backendediting experience, too like diogo wrote.

Just pleased of the founded threat to read myself...so

best regards mr-fan