• Content count

  • Joined

  • Last visited

  • Days Won


Sephiroth last won the day on June 8 2015

Sephiroth had the most liked content!

Community Reputation

192 Excellent

About Sephiroth

  • Rank
    Sr. Member
  • Birthday 02/19/1986

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
  • Interests
    Mostly Programming and reading about Emulating game consoles in C++, watching movies that mess my mind and spending hours playing my favorite game "Skyrim" am an Anime/Final Fantasy Fan and yes Sephiroth is my fav character

Recent Profile Visitors

3,480 profile views
  1. Yeah I use it at work, created this with it It feels lighter to me than Ionic and faster, and yes it can be built with other frameworks. But TypeScript and NG2 isn't bad though
  2. Not a sitemap, I meant all posts on a site, WordPress doesn't have the concept of Post having another post as a child compared to WordPress. But now that i think of it, I don't think i could write a sitemap in WP
  3. Damn yeah $pages->get("/") fetches a page while the children method from it is the PageArray. thanks I will update
  4. Lol sorry wrong choice of words, I mean a list of all pages on your site, didn't think that statement through when i was writing
  5. "And the world shall know Pain" ~ Nagato

  6. Note: 100% Honesty no Bias I would say it takes much more to develop in WordPress than in Processwire, I will backup my claim with code examples and also various scenarios, before I came into Processwire, I was developing WordPress and really with minimal code , you can do alot in Processwire. Let's look at this now Scenario 1 Fetch Images for a specific Post This is how to do this in WordPress $thumb_ID = get_post_thumbnail_id( $post->ID ); if ( $images = get_posts(array( 'post_parent' => $post->ID, 'post_type' => 'attachment', 'numberposts' => -1, 'orderby' => 'title', 'order' => 'ASC', 'post_mime_type' => 'image', 'exclude' => $thumb_ID, ))) { foreach( $images as $image ) { and this is the equivalent in Processwire foreach($page->images as $image){ } You see the concept in Processwire is that everything is a page, so when you are in a Page, you get the neccessary information required for that page, However WordPress has a "Post Concept" and images are tied to the Media Library which is why you have to supply a post to fetch images. Scenario 2 List all Pages on the Site Now imagine you are looking to create a list of all your pages, this is what you will do in WordPress <?php /*pass your search string here example like this ( 's'=>'test' ) */ $args=array('s'=>'test','order'=> 'DESC', 'posts_per_page'=>get_option('posts_per_page')); $query=new WP_Query($args); if( $query->have_posts()): while( $query->have_posts()): $query->the_post(); { echo $post->post_title; echo $post->post_content; } endwhile; else: endif; ?> Now this is the same result in Processwire $pagesList= $pages->get("/"); foreach($pagesList as $page){ } Minimal PHP Knowledge and beautiful design, I can guarantee you within a week's practice you will be able to deliver something quicker, however some tasks might require additional time, but Processwire has been carefully designed to appeal to people, at a point I wasn't happy when it wasn't adopting Advanced concepts (FIG,PSR) but as I evolved i realized there's more to coding and that user adoption is important. Now let's forget the code let's look at Content management Now you want to create Website and let's assume in your case, it's a website about selling Boats (sorry that's what to mind), Out of the box for WordPress, unless you are creating a custom type, you can't fit that logic into WordPress as it's built around Posts and taxonomy, so you have to create a custom type and this involves codes, or install a plugin, whereas in Processwire you simply create a Page which holds Boat informations and create fields to accept relevant information. This is much more intuitive than WordPress, because in WordPress you might have to add it as a custom field which obviously involves coding again, or as usual checking to see if such a plugin exists, or the last option is to pray that someone builds a theme that involves selling of boats. Now this is the custom field in WordPress, however by default most of the custom fields in WordPress are Text input, during my previous experience creating a custom field other than text involves coding and obviously you know what comes next; installing a plugin again for another need. WordPress takes a lot of time, money and also very nerve wrecking, updating WordPress or the plugin is like russian roulette to me, I have to backup, and pray for the best, It's moments like this that I become very religious. And if something breaks I either have to fix the issue or revert, and sometimes the reason you are updating is because of security issues, so it's either breaking the site or getting hacked. Which means additional money for consultancy and it gets messier from there. I've been there and done that and I simply decided to migrate to another platform as WP wasn't worth my sanity. Processwire is good and the modules built are easy to use and configure, my favourite is the DatabaseBackUp without thinking too much you can easily understand your way around. In conclusion Processwire is good and easy to grasp, it might not be perfect and that's a good thing because it means there's room for improvement, and we are even lucky to have you around, as you can share how we can make Processwire more user centric and easy to use and also features can be created in modules to make PW a more robust system. I will link @Joss article TLDR: Processwire is easy to learn.
  7. How do you achieve this in Processwire. the sidebar preview i mean ?
  8. Your know your topic had me thinking, can a non-coder use Processwire and actually setup a lot of things on the go, I had to think deeply about this, because I'm highly technical and know my way around, but to be honest It would take some effort compared to WordPress (in terms of adding additional features), I don't think you can *easily* do that with Processwire, and this is where 3rd Party Modules Developers come in, Modules have to developed with user in focus so that users can easily configure and tweak settings without needing to touch the code, which is always what WordPress has going, it's why users find WP a haven and not developers, Processwire has a developer-esque to it in some ways. I would because Processwire is a CMF which is why, the developer presence might feel strong but unlike other CMS (Bolt,Backbee CMS, ImpressPages , Silverstripe, Concrete 5 and October CMS) I would say this is the most friendliest you can feel comfortable with, a basic knowledge of PHP is all that is required. WordPress is just.................................. don't even want to talk about it, I am currently handling a WordPress project, and am this close to picking diving in front of a bus than working on the project
  9. Giving it a try
  10. This is a really BIG Project you should write an article around this especially a case study
  11. Any update on this ? is this still in motion ?
  12. These days it's mostly Rap and New Age i listen mostly Kendrick Lamar
  13. Thanks I didn't even see this comment, I had plains of re-writing, I think i went too far going with something too complex without best practice so working to change the tutorial to start with something small like fetching API from Reddit to build a widget.
  14. it looks like "PN" I like the current logo though reminds me of the up-side down beats
  15. Hi I am going to be honest I have used both but not as extensive as you have, If you are going to use VueJS via SPA, then it won't matter whether you use Processwire as you would simply be concerned about your JSON Data, which any API/Service can equally play that role. As for your webpack-dev-server i don't think it matters as SPA is only concerned about the data, meaning Express, Golang,Spring can easily serve the JSON and it won't make any difference, as for SSR am gonna be honest am still not sure what SSR really is, Maybe i should read more detailed articles on it. all the best, I would simply advise to using VueJS as components for your pages. But it depends on your aim though