Jump to content

Search the Community

Showing results for tags 'processwire api drupal'.

  • 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

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. Hi all This is curious. After spending quite a lot of time using, learning and advocating Drupal as an API interface rather than template builder, I come here and find Processwire seemingly having been doing this all along. I often thought Drupal became heavy and bloated from a page loading point of view, with so many users using modules (Views, Panels, themes with sub themes, etc) that control layout. So I thought, hang on, shouldn't we be making the template statically and adding the bits we want to it? Followed that route for a few sites, but found little interest in the idea from others. So here I am, experimenting with Processwire and it seems the whole ethos is that approach. Or I am a lot less smart than I thought and completely misunderstand this system.....
×
×
  • Create New...