Jump to content

Search the Community

Showing results for tags 'modularity'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hello, I am using PW for some time and I am thinking a lot about modularity in ProcessWire. In a German CMS called Redaxo, everything consists of blocks. A page has many blocks and every block has an input and output. It is pretty simple for the user to stack blocks per page to build content for a site. So I can define a "media gallery" block, a "Q & A" block and the user can stack them like he want's. And every block is a file so it can simply reused for the next project. How can I achieve this in ProcessWire and: Is this a good practice in regards of PW's structure? Let's start a discussion about it! I really like PW but I can not really get the gist of modular behavior in PW. I am also searching for some good practices. I currently try to achieve this kind of behaviour by using PageTable and creating templates for each block/component (prefixed with "c-")... Thanks for you answers in advance!
×
×
  • Create New...