Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/02/2012 in all areas

  1. Of course I recommend Processwire. Best CMS/framework I have ever used. Ever. Thanks Ryan and everyone for Proccesswire. Processwire literally changed the way I do everything. So awesome!
    2 points
  2. I was just reading this post on how to make breadcrumbs in ExpressionEngine (http://bit.ly/hello_crumbly) and how you basically have to resort to a plugin to do it for you. It reminded me of some of the problems I had with EE when I was trying to use it and develop in it awhile back. One being that URLs aren't a primary/unique key to a page, natively in the system. Imagine ProcessWire with only it's root level pages and url segments, and that gives you an approximation of what you have to deal with in EE. I'm not saying it's wrong, but it's a different approach, and one that I found frustrating to work with. The post also made me realize I didn't have anything on the site demonstrating how you might make a breadcrumb trail (other than in the default site profile). It's really a simple thing (at least, relative to EE), so figured I'd post here. : <?php foreach($page->parents() as $parent) { echo "<a href='{$parent->url}'>{$parent->title}</a> "; } You may want to output those as list items or add some >> signs between items, but as far as code goes, the above is all there is to it. What it's doing is just cycling through the current page's parents till it reaches the homepage. Lets say that you also wanted to include the current page in your breadcrumb trail (which is probably redundant, but some sites do it). What you'd do is just append it to the list of parents that gets cycled through: <?php foreach($page->parents()->append($page) as $parent) { echo "<a href='{$parent->url}'>{$parent->title}</a> "; } The reason this is so simple is because every page is anchored to a specific URL and those URLs are representative of the site's actual structure. Pages in PW are actually uniform resource locators (URLs) whether on the front end or the back end. Because of that, there's no guesswork or interpretation to be done. In EE and Drupal (as examples) that data does not natively live at a specific URL. Instead that data is off in a separate container and the ultimate URL (or URLs plural) where it lives–and will be presented by default–are not as cut and dry. Yes, you can install plugins or go through strange taxonomic/channelistic/cryptic trials to approximate the behavior in other systems. And yes you can use url segments and pull/render any other pages you want in ProcessWire according to your own needs. But I'm talking about the fundamental and core system differences. This difference goes far beyond simplicity of generating breadcrumbs–it is a factor that translates to simplicity throughout the API.
    1 point
  3. Hi all, I just launched our agency's web site redesign, done with ProcessWire. This was my first site - I'm working on another one at the moment as well. This one features a single page design, while maintaining good SEO practices. It turned out to be easier than I thought, especially the caching setup, which I'm using to offset the fact that I'm essentially loading all of the site's content at once. If anyone is interested, I'm happy to chat about how it was done. http://www.agencypja.com Cheers.
    1 point
  4. Hi all, I have just 'finished' (well, to the extent that I can pretty much call it 'done' for now) my portfolio website. There are still a few issues with it - I have yet to make it fully responsive for mobile, I need to work on the footer area and I haven't uploaded all of my work samples yet. The brief I gave myself for this site was to come away from the usual 960, centered grid into something a little more fluid - breaking the usual mould for rigid layouts. I also wanted something very simple that hopefully allows the work samples to become prominent. I am SO PLEASED working with ProcessWire for this site!!! It has been an absolute pleasure and just before I came across PW I had a version on my localhost developed with Drupal. It was slow and cumbersome! I was so sick of Drupal and it's horrendous default markup that PW seemed a dream to work with in comparison. I am already working on another website with PW and I see this trend continuing with every website I do. Thanks for the great CMS! www.ray-dale.com
    1 point
  5. This is a particular interest of mine - you can do something quite useful with mySQL's 'sounds like' comparison and then maybe sort your results using PHP's levenshtein function. It's an approach I've used in the past and works quite well.
    1 point
  6. I've used Twitter Bootstrap for one live site, one that's in development and an extranet also in development, and it is truly awesome in its comprehensiveness. And just a couple of hours before reading this thread, I had decided to use HTML KickStart for another project that is (hopefully) due in soon! It seems to me that one of the great advantages of ProcessWire is that any of these kind of design frameworks can be employed to streamline front end development, giving us the very best of both worlds. Especially those of us whose design skills are less than optimal.
    1 point
  7. Thanks DaveP-- Glad that you got up and running and are enjoying using ProcessWire! Your compliments made my day, especially what you said about "looking for complexity that wasn't there". I think we're all conditioned to look for complexity in CMSs because most of them are pretty darn complicated once you get beyond doing basic things. If a CMS were a car, you'd have to know how to tune the engine, bleed the brakes and adjust the spark plugs before you could drive it. With ProcessWire we're trying to put you in the drivers seat rather than under the hood. Take development tasks that would be complex and make them a lot easier. If you saw how many iterations all of this stuff has been through, you might say I'm a bit slow. Part of the reason ProcessWire is here is because I wasn't smart enough to be able to figure out how to get things done with the other CMSs.
    1 point
  8. Great feedback, thanks Maruchan! It's interesting to see that ready-to-go site profiles and training materials are your top two. Both of these appeal to me a lot, definitely something to think about more. I might have to test the waters with a ready-to-go site profile to gauge interest. Beyond those that you mentioned, are there any other ready-to-go site profiles that you think there would be good demand for? With regard to books, I'd love to have two "abookapart" sized/styled ProcessWire books: one for developers, and one as a user guide that we can provide to our clients after building a site for them. Though even if not full-blown references manuals, such books would take serious time and resources to create. But I've got two things working for me on that front: my brother designs books and my dad owns a book publishing company. I'm going to have a little chat with them this weekend. However, with family in the book publishing industry, I'm well aware that one does it for the love and not the money... most books lose money. Still, I think ProcessWire book(s) might do well, so I'm going to find out how much it'll cost for the production.
    1 point
  9. I think we're best focusing our efforts elsewhere. It's not a level playing field over there. I don't think the people running it are dishonest by any means, but they've got a real problem they have to deal with before I'd want PW to be listed there again. The site's rating system is being controlled by hackers to boost the ratings of CMSs that can't compete on their own. The back door to the ratings system is obvious to anyone that experiments with it for 5 minutes … one uses a hidden iframe to start a session, and an <img> tag to complete the vote, and every visitor to your site unknowingly votes your will at opensourcecms.com. It would be easy for us to play the game and boost ourselves to first and slap Joomla to 1 star, but why play that game? That's stooping pretty low. It's taking advantage of innocent users and opensourcecms.com. Though I do think that that opensourcecms.com is at fault too–leaving a backdoor open like that is asking for trouble. While I feel bad for the folks running opensourcecms and those that have to cheat in order to compete, I think we should be genuinely honored to be considered such a threat. We got nearly 2,000 1-star votes yesterday by someone that was apparently very scared by ProcessWire. Surely that must be a record at opensourcecms. It definitely gives me a lot of energy and enthusiasm for our project.
    1 point
  10. He's not only quick to answer, he is also clear, didactic and informative. I don't have time to play with PW currently, but I'm always reading new posts just because the answers are always interesting.
    1 point
×
×
  • Create New...