rick

It is interesting that you say that. What I like about ProcessWire is what I like about my choice in OS. This opinion is based solely on my developer-centric view, and not from the view of my clients. ProcessWire to me is akin to the *NIX of operating systems. Other so called CMSs, especially the more popular ones (wordpress, drupal, et al.), are the windows wrapper versions, whereas the MVCs (and Smartys/Twigs impementations) are the mutated CP/Ms. Everyone believes they have a better mouse-trap. And Yes. You can use their self-proclaimed turbo-charged, lemon-fresh, automatic-transmission mouse trap to kill a mouse, but at exorbitant cost for the supporting systems and learning curves of the end-user. ProcessWire is well architected, particularly so for us 'geeks', as is Unix. And that is where the trumpeted "User Friendly" rears it's ugly head. I'm not knocking the opinion of others. This is, after all, only my opinion. I don't mind so much the Gnome [x-windows, etc.] attempts to make *nix more user-friendly, but please, please, don't bastardize ProcessWire into Windows98.

Yes Sir. I have used quite a few of them for small-ish projects over the years, and wrote a few plug-ins along the way. I must say that I am more impressed with processwire than I thought I would be considering all I had for a reference was those 'other' apps. I can see PW being my goto tool for all of the "greater than one-page site" projects. That in itself is exciting.

I don't consider myself an advanced programmer, neither am I a beginner. As I said in <a href="https://processwire.com/talk/topic/2311-processwire-on-the-web/page-17#entry99587">this</a> post, I balked at PW at first. The first articles I read referred to 'templates'. I wasn't looking for another app with a template engine, so I passed on digging deeper, and continued on with my search. It was the term 'template' that initially turned me away. After looking at all the cms and framework files, I thought, "Great, another idea for a better mouse trap. ...Again." Each and every one of those cms and framewoork apps do not come anywhere close to processwire. Don't get me wrong, I've been using many of them for years, and I am not putting them down. They serve a purpose -- Just not my purpose. From what I have been reading on this forum over the past few days, there is a great group ready and willing to help, and the development is heading in a direction that will support us newer members becoming a more integral part in the future. I don't see PW living between casual and advanced users at all. I see PW as it being what you need it to be. If you need casual, it fits. If you need advanced, it fits. </ .02

Thanks for the tip, jlahijani. That's the one place I haven't read, yet. I am running the dev version, so I will start reading up.

How to you apply styling to form fields created by the API? For example, when using either a bootstrap css framework, or when using a custom css file. I apologize if I have just overlooked the correct search results. If someone could point me in the right direction, I would appreciate it. Thanks!

Thanks everyone for the welcome. I've been reading through many of the posts in getting started, api/module, etc., and the only question I have at the moment is in regard to the documentation and cheat sheet. I think I read that the cheat sheet is being updated, and the wiki is going away. Being the newbie, I like to try and find out the answers before coming here and wasting y'alls time with a rookie question. So, my question is, how up-to-date, or sync'd, are the reference materials in relation to the production releases?

@Soma: I've been trying to remember the specific issue I was researching -- Happens a lot when I walk into the kitchen too. I will post it when I eventually think of it, though.

I am new to ProcessWire. I am not new, however, to programming (started with assembly back in the '70s). I'm not writing a marketing speel here -- I simply want you (the developers and community) to know how I arrived at ProcessWire as my solution. I have specific requirements for a numer of projects that I will be starting (hopefully) in the next few days, and had been researching various CMSs and frameworks the past few weeks to find a 'one-size-fits-all' toolbox. I have currently forty-four cms installs (from academic to zikula) and thirteen different frameworks ( from akelos to zoop). They all have their merits, and are fine solutions for many users and developers. ProcessWire is one of the original 44 installs, but at first 'glance' didn't seem to fit what I was looking for. Later, after searching the web for a solution to one particular issue, a link back to a PW solution emerged. I clicked the link, and low and behold, ProcessWire *was* what I had been searching for all this time. On a related note, google has sent me a nasty-gram about the reactor they had to fire up because of my queries. The primary strength of ProcessWire that I have discovered so far, is that I (as a developer) am not limited in the tools I can use, or the tools I can create. ProcessWire is sleek and efficient. It is a toolbox full of tools that allow me to build a fine watch, a multi-story office complex, or a fishing pole. The other applications suffer from either bloatware or limited tool availability, or worse, both. I could very well accomplish my project goals using any of these other applications but with much head-banging, hair-pulling, and cosumption of scotch. The biggest 'selling' factor to me for ProcessWire, however, was it's efficient engieering in the construction of built-in tools I will require now, and the ability to create my own tools for use in the future.

Hello all! I'm not sure if this is the correct forum to post an introduction, but I didn't want to clutter a specific topic elsewhere. I've been reading various forum topics, wiki, and docs, for the past twenty or so hours and decided to sign up last night. I just want to say that I am impressed with Processwire itself, as well as the community's eagerness to assist us newbies. I'll most likely have a number of questions later. As of now, I suffer from information overload due to the amount of reasearch over the past few weeks. I'm sure some of you old-timers, like myself, are familiar with *Tilt*, which is currently emblazoned on the back of my eyeballs. I look forward to learning and working with PW on a number of up-coming projects, and eventually become a contributing member of this community. Thanks for having me. Best regards, Rick