Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About LeTroner

  • Rank
  1. Just an quick note... Building a web app using processwire as backend serving JSON via an API to VUE. Works very well... just wondering about performance compared to Laravel or something similar. But at this stage the knowledge I have of Processwire is such an advantage that allows me to work really fast. Would absolutely recommend using it for prototypes... you can always migrate later on to another backend and you can keep the front-end exactly as it is.
  2. Thank you all for your answers! Also interesting with URL segments and GraphQL. It seems it produces slightly slower requests, so I will test it for another project. Using a router solution like the one you pointed seems a bit overkill at this stage specially for my knowledge level. So far Vue and Processwire work very well together. I built some kind of REST api and the performance is very good both for read or to create pages. In some pages I am using regular forms to create posts, users... and in some others I am using vue. Vue of course offers much more potential to build complex, modern interfaces. Great that I can combine both methods. I think Processwire is flexible and powerful enough to build webapps with a smaller learning curve than a full fledged framework such as Laravel. It would be just perfect if creation of APIs for consumption by the front-end would be just a bit easier out of the box. (Is not that the hot keyword of the year? Headless CMS?).
  3. Hi! I am right now building a webapp based in Processwire and using Vue.js for the front-end in some of the pages. I followed some tutorials and used a REST class that was golden to be able to output JSON and build an API. (BTW Processwire should really do like Laravel and be able to output json out of the box). My question is regarding the structure of my files and templates. I have worked a bit with Laravel and I understand their MVC pattern, and was wondering how to do the same in Processwire or how to best organise things in a growing app. For the moment I have a cluster of pages handling the API requests under /api/... Then I have a cluster of pages handling the views such as /app/users /app/calendar ... Is there a smart way to organise this? Do you have any experience that can give some light? Thank you and sorry for the noob question!
  4. I think I tested valet with processwire a couple of years ago and i think I remember it working very well... except all things .htaccess which depends on the drivers. I did not really research it a lot.
  5. Thanks Szabesz. The JSON part is already controlled and working thanks to a good post another user made in the forum. It is the many to many relationships and, specially, how to handle the follower data and how to represent it in Processwire. A new page per follower? Field with a json value? Any hint is welcome!
  6. Hi! Thanks for your answer. Good point! What I intend to do is check if the user is following back those followers or viceversa. So basically I want to retrieve the user->followers and the user->isfollowing and compare between them. Usually each follower would have data such as ID, username, etc etc. Thanks!
  7. Hi! We are big fans of Processwire to build all websites for our customers. Coming from Wordpress and Drupal we appreciate the beautiful API and the total flexibility that this CMS offers. Now I want to take a step further. After learning a bit of Laravel and Vue.js I realised that Processwire is such a beauty to work with and that actually it would be so much easier to build MVP with it than with a full fledged php Framework. So as some other people I plan to build a JSON API with some methods I found in the forum. (Is there an alternative method to output things as JSON in the Core of Processwire?). Anyway, the app I am building connects itself to social networks API's and retrieves information about the followers of a certain user in that network. So if an user has a lot of followers I need to retrieve the list of all these followers. So the data is basically: User--->Followers--->(Follower1, Follower2, Follower3, Follower4...) I have been thinking and I am not sure I understand what is the best approach to represent the Follower data in Processwire. Would you create a page for each follower? Or how do you represent/store each follower for each user. Important to notice that Follower2 might be following 2 or more users. So how would you approach this kind of data in Processwire? Thank you in advance for your help!
  • Create New...