Leaderboard

Just a quick little play around with returning results directly from the modules directory. It is pulling in from a cached JSON feed from the modules directory. Obviously we want browse/filtering by category functionality as well, rather than just searching like this, but I think this would also be very useful for those who already know what they want. EDIT: new version and further discussion here:

In this week’s post, we’ll take a look a look at the new website and focus on some parts of it and how they were built. Then we’ll dive into the latest version of ProcessWire on the dev branch, version 3.0.124— https://processwire.com/blog/posts/pw-3.0.124-and-new-site/

Hi all! Happy New Year ? I recently rebuilt the website for classroombookings - my open-source room booking system for schools - using PW ? classroombookings.com I started the project itself way back in about 2006, when I was working in a school and needed a solution. Over the years I haven't made that many changes to it - mostly due to lack of time - but it has a modest userbase. Fast-forward to late 2018 when it required a major update to support PHP 7, fix some issues, and I also launch a hosted service. The website serves marketing, documentation and download/release functions for the project and I think PW is ideal for it. In the spirit of open source, the code for the website is also available on GitHub for anyone who wants to poke around and see my approach to PW web builds. The site is pretty standard, the only 'custom' bit is the releases section, which it pulls from GitHub using their API and creates/updates pages (Releases module). The frontend uses the Spectre CSS framework, and this is the first site I've built using it. Modules: AdminTemplateColumns ProcessDateArchiver SettingsFactory TextformatterHannaCode

For what is worth... Here are my notes that I've gathered from the forums and other places. Maybe something like this can be used somewhere? from @kongondo and others **************************************** When coding inside of modules you cannot directly access the PW API variables like $pages, $session, $input etc.. Those are available at $this->pages or wire('pages'). If you have static method(s) in your modules then you need wire('pages') there - so if you want to play it safe always use that (it works on command line scripts also) **Outside a function and class. Ex. in templates $page; $pages; $sanitizer; $input; $modules; $templates; $fields; $user; $users; $log; $session; $config; __('Translate me baby'); **Inside a function or classes not extending WireData wire('page'); wire('pages'); wire('sanitizer'); wire('input'); wire('modules'); wire('templates'); wire('fields'); wire('user'); wire('users'); wire('log'); wire('session'); wire('config'); **Inside classes extending WireData $this->pages->find('something'); **Inside a class not extending WireData $this->wire('page');// also $this->page; $this->wire('pages');// -ditto- $this->wire('sanitizer');// -ditto- $this->wire('input');// -ditto- $this->wire('modules');// -ditto- $this->wire('templates');// -ditto- $this->wire('fields');// -ditto- $this->wire('user');// -ditto- $this->wire('users');// -ditto- $this->wire('log');// -ditto- $this->wire('session');// -ditto- $this->wire('config');// -ditto- $this->_('Your string to translate’); $title = wire()->fields('title'); // in a regular function outside of an object $title = $this->wire()->fields('title'); // in a Wire-derived object $title = $this->fields('title'); // in a Wire-derived object (alternate syntax) from here /** * Global function, therefore does work everywhere, * but will always refer to the first pw instance * in case of multi instance usage. * Because of that it's discouraged to use this in * modules. */ wire("apivar") /** * Safest way to get the api variable in wire derived * classes like modules. */ $this->wire("apivar") /** * Does work as well, but some (core) classes have that * type of access disabled. It also prevents you from * using a custom paramater $apivar in your class. */ $this->apivar From here In hooks use $event->wire() instead of wire() because it is multisite instance aware ****************************************

I end up interchanging $this->pages and wire('pages') in modules depending on my mood. I've never learned which one is better than the other which is my problem, but I think it needs to be explained up-front, and as I think others have said any examples on the website should use the most efficient (or readable, but make a choice of one or the other) versions for where they're used. If there's a little "did you know the difference between x, y and z" on the documentation page for all the $pages info then that would be handy and link to the same explainer on a different page so the explanation is always there but the documentation and code examples are consistent (not saying they're not, I've not had 5 minutes to look yet just want to make sure we're not confusing people too much :)). A module installer that would install Tracy from wihtin Tracy? ? I'm kidding ? What I meant was an overhaul to the core module installation area really. I vaguely remember even MODx had a way to browse modules from within the admin - it just saves time and it's not like there should be more bandwidth using a REST api than rendering the modules directory as you're not rendering all the assets at the same time. There may be more bandwidth if it results in a spike in usage, but that can only be a good thing. What I'd love to see eventually is, after the installer runs, it then suggests some things for you to install on a first-run splash screen, so setting up a new site is ticking some boxes and you're away. Even better (though harder to code) would be remotely logging into the PW site from your installation and getting a list of your personally-chosen regular-use modules so you can tick the ones you need for your new project and they all install in one go. Sure, that's the ultimate nice-to-have, but anything that speeds up initial setup helps I think, especially for newbies ?

Yes, you can duplicate your site on a new domain. There are modules that will help you do this but I'm a bit old school and prefer to do it manually when moving PW sites. Take a copy of the database, either with the ProcessWire module, DatabaseBackups or via PhpMyAdmin and download to your PC Download all your PW files to your PC, especially site/config In your new site, create a MySQL database and make a note of the db credentials Import your database sql file via PhpMyAdmin Upload your files to the new domain Edit your site/config.php file to include the new database credentials and the http hosts to the new domain name Clear your cache, especially ProCache if you use it Should then be all good to go PS: It's important to use your original site/config.php file as it contains the password salt for the original database

@ryan - just looking at: https://processwire.com/api/ref/wire-mail/ I feel like there needs to be some better explanation as to which can be used where. I know this is similar to the $pages / wire('pages') debate, but it's another example where a newbie might wonder why there are options and just assume PW is confusing for no good reason. Do others agree, or is it just me?

Apparently Ryan does that also, so don't feel bad, eg $this->modules vs $this->wire('modules') in his LoginRegister module: https://github.com/ryancramerdesign/LoginRegister/blob/7e6395393d46f9fba3a6769cc2ce85d4e495b8a4/LoginRegister.module#L492 https://github.com/ryancramerdesign/LoginRegister/blob/7e6395393d46f9fba3a6769cc2ce85d4e495b8a4/LoginRegister.module#L430 I completely agree that this belongs in the core modules installation area - I'd even be keen to work on it, and I love the idea of being able to favorite modules for easy access on other future installs. I was just starting to feel like a broken record on the $pages vs pages() etc stuff, that's all. I certainly won't keep quiet on other feedback I have!

It looks like that's the problem of pagefinder and not DynamicRoles. Please try reversing the selectors, first has_parent and then id (has_parent|id=1631).

<?php echo count( $page->dev_repeater->find('dev_repeater_exclude=0') ); ?> This should work. Did this with a RepeaterMatrix field a while back in this way.

Actually speaking of the cheatsheet - these days I just refer to the API Explorer panel in Tracy - it's all there and always up to date and I generally prefer it to the PW website docs for quickly finding stuff. That said, I still think there is a place for the cheatsheet for beginners because it lays out the most used stuff so well.

Maybe we could collaborate on that. The "favourites" idea was just something that popped into my head because I've been working on integrating the forum member bar into other parts of the site (and forum member auth into the Modules and other interactive aspects as well). My test member bar currently does an AJAX request once the page is loaded so we can keep ProCache running on all pages, so a similar method could be used to remotely authenticate a user against the central PW database and retrieve the user's favourite modules. I think that this could be extended to do all sorts of cool things really, but an revamped module installer first, maybe with user-defined favourites, would be a good starting point - even if we only get as far as a mock-up of the design to begin with and run it by Ryan before we get too far ahead of ourselves ? The layout of such a module installer should be pretty similar to this idea we've been discussing for a while for the main Modules forum here as well, so maybe we could kill two birds with one stone there with the layout and basic search functionality at least ?

As per my last post above, if there's no explanation then yes, it is adding confusion, especially for newcomers. Well, and me, because I never bothered to learn the difference as I'm always in a hurry to get stuff done - tricky few years personally so if something works well I do it and move on quickly, but I do come to docs and examples every now and then and for the sake of a quick explanation on the docs page that would make me think "aha!" I should use that way, it's a shame not to have that explanation. If we're giving examples though, as in the case of wireMail, it should surely just be ONE way to do it (the most efficient?) with the other ways stored somewhere further down the page maybe even at the bottom in this case. Like "alternative ways to get a WireMail instance" (but with better wording). The funny thing is, I used Option C from that page the most at the moment as I'm often using it in my own classes, outside of PW modules on a current long-running client project, so again I'm not able to see why that option isn't recommended or where I would go to find out why (I'd actually love to know if anyone has the answer? My classes do extend PW's core, so maybe I can get away with option B?). Flogging a dead horse by now, but yes, for that specific doc page just list option A as being for use in templates, option b for use in modules and explain option C somewhere else under a "did you know?" or "alternative methods" header or something. And yes, don't shut up Adrian, this is all good feedback ?

Please see the attached screenshot, Business to Consumer is written over the Blog. But not a big deal... There are still two prev posts in the footer (see attached screenshot from @gmclelland). We all agree on that. I think the examples on the site should have run button (like Codepen) so that users can run the examples and play with them, I think Tracy could fit here (I think Adrian already suggested something in that regard). @ryan While an example is good, for newbies this is odd. What is "output formating"??? I think we should use simple examples that just work. Mixing $pages and pages() is confusing too. Why don't we just stick to one notation, at least in examples, and have a special page where all these options are explained in details?

The old logo is back due to popular demand. I've never liked the way it looks next to the newer mark, but reducing the brightness of the word "Process" seems to help a bit, so I think it works for now. The issue with the overlapping dropdown should be fixed now, please let me know if anyone else is still seeing it. You might have to double-test in Incognito mode if you do, just in case something is stuck in the cache. I agree with Adrian's points on Tracy, and also I wouldn't know how to maintain it if he ever decided to go meditate in a cave in India for a year. But I also agree about how useful and important Tracy is and that we should give her first class treatment around here and make it as easy as possible for people to make it a part of their installation. Perhaps the core modules install screen has an "Install Tracy" button, or special site profile, or maybe PW's default error messages could suggest Tracy as an option for additional developer help, etc. I think the example is fine because it just depends if output formatting is on or off. And if it's on, it'll give you an error about what you need to do. The purpose of those examples on the homepage is not to provide a full start-to-finish API workflow, but it's to show some interesting snippets to what's possible in 1 line of code. This is more about marketing than it is about serving as documentation, though of course they are good examples too. Regarding use of $pages vs pages(), I had thought we had it enabled in all the site profiles by now, but it turns out it was in the newest one but not the older ones. I'm updating the older ones so that it is enabled by default. I'm also updating the error handler so that if it detects you are trying to use the functions API but the $config->useFunctionsAPI is false, it replaces the "undefined function" error message with a "you need to enable the functions API and here's how..." message. Tracy actually got me thinking of this because I mistyped something and its error said something along the lines of "did you mean [alternative-function]" (not sure of exact wording) and I found that incredibly helpful. It's showing up for me. It's just there's a lot of stuff with the word "find" in it, so you just have to click on the view-all link. This is actually how we make it possible for that footer to be always up-to-date with the forums, Twitter, etc., even if the rest of the page is on a 1-day (or 1-week) cache via ProCache. It uses Uikit's scrollspy to automatically load the footer via ajax from a separate page that is on a 60-second cache, but only if you actually scroll to it. In this manner, we're getting full cached delivery, and a fully up-to-date News/footer section when/if you scroll down to it.

As first discussed here: https://processwire.com/talk/topic/20596-new-post-new-pw-website-ready/?do=findComment&amp;comment=178781 Here is the next version of the searching interface. You can see how it automatically populates the module class name in the field from the matches based on what you have typed. This is basically ready to go if Ryan is willing to incorporate. Now we just need to figure out a browsing/filtering interface to make it easy to discover modules base on categories and keywords.

You got a small typo:

Thanks for sharing your opinion ? Thank you adrian ? He already knows about my module: https://processwire.com/talk/topic/18763-alpha-rockforms-flexible-fast-and-secure-frontendforms-for-processwire/?do=findComment&amp;comment=178767 and he also knows about FormBuilder (which would be a possibility for him to contribute to the project as it supports Ryan). I don't feel offended - I'm also happy to be here and thankful that I found PW (thx again @gebeer!) and that lots of people here are providing such valuable tools and helpful posts. Let's get back to topic...

the community here is second to none. Never experienced such a combination of Knowledge and Kindness.

I do think that is a little unfair - @bernhard's RockForms (https://processwire.com/talk/topic/18763-alpha-rockforms-flexible-fast-and-secure-frontendforms-for-processwire/) is actually really nice. There is also http://modules.processwire.com/modules/simple-contact-form/ Nothing is perfect and PW is no exception, so you have to figure out what option suits your needs and skills the best and I think PW is that product for me. Do I agree with how everything is done - no I don't, but for now the pros outweigh the cons for me which is why I am still here ? And the community is also a huge part of why I am here - never come across such a helpful group and that has stemmed from Ryan's communication style here in the early days (when he had more time).

@anderson What the amazingly talented PW dev @bernhard said is true, especially the bit about it being different to point-n-click website builders. Keep in mind that ProcessWire offers so much more on so many levels. Whether you want to get into module development or not is up to you. See the showcase for examples: 1. A landing page site of mine that used a number of custom & pro modules, including Repeater Matrix 2. A landing page site from another PW dev that used nothing but core modules

Hi @anderson I also started ProcessWire with this video. A must to do for a beginner. About the asset folder containing images, css and js, this folder come from the free theme that you have to downloaded there : https://templatemag.com/demo/Spot/ (this is the theme the author is using to build the final website). Once extracted, you can find the assets folder and it should be placed in the folder site/templates of your ProcessWire installation - along your templates - then you can continue to follow the tutorial. Do not mix this assets folder (which could be renamed of whatever you want, eg: mythemeassets) and the assets folder in site/assets which is a core "required" folder created by ProcessWire. Good luck, you are on the good road ! ? On the same road you can pick that :

Hi @anderson and welcome to ProcessWire In answer to your questions: 1. Short answer is yes, if you have 10 pages of which 2 have the same layout, then you will need 9 templates. HOWEVER, I recommend you read up on "Regions" and delayed output. You can have the _main.php template with all the common elements eg the header and footer, then you only need templates for the bits that are different, eg the page body. Alternatively, you can include files such as header.php and footer.php into each page template file. 2. Yes, Modules - Site (or other tabs on that page) 3. "PageTableExtended" is an Inputfield module. Create a new field and assign it as type PageTableExtended then add it to your template(s) 4. There is a core fieldtype called "Repeater". This is not installed by default. You can install it from Modules - Core. 'Repeater' is a prerequisite of the commercial module, "ProFields" https://processwire.com/store/pro-fields/ which includes a number of fieldtypes including 'Repeater Matrix'. 5. The '/site/assets' folder is automatically created on the web server when you install ProcessWire. It's used by PW for all sorts of stuff and you can add your own files/folders if you wish. Typically you would access it with FTP or similar. It's not visible in admin area by design and a good place to store files you don't want to change

It still confuses me sometimes... to be honest.

Sounds good!! I think it is especially confusing that you have: $page, but then pages() - that suggests to me that there is no $pages option. I still think all examples on the site should use one approach with a dedicated page that explains what can be used where and why. I provided more detailed thoughts about this here: https://processwire.com/talk/topic/20596-new-post-new-pw-website-ready/?do=findComment&amp;comment=178332 I think all the $this->wire('pages'), $wire->pages, $this->pages, $pages, pages() options are confusing to newbies to PW and OOP in general. But I won't mention it again if you think it's OK ?

Marketing sight: Absolutely true! User sight: G*d d*mn f*ck sh*t! It doesn't work. I was on the search for a new CMS (back in 2014) that could maintain hundreds and hundreds of custom fields. Some things I tried back then ended in an error but I stayed because I had someone that said "ProcessWire works!" Without that second voice I would have moved to something else. Working examples are more an argument PRO ProcessWire than examples you have to understand with basic knowledge of the system. I was able to type the characters shown in the tutorials but didn't know what was happening. That came with time and the more I worked with ProcessWire the more I started to love and believe in ProcessWire as my CMS of choice. But that's just my experience and sight on this.

I'm pretty sure it's about 80% done by now ?

I've not actually used Tracy yet... *everyone gasps* ...but I have often dreamed of a module installer that lets you browse via category from your PW installation itself. This way you get around the less intuitive copy-and-paste-the-module-name-to-install functionality as it exists today (it's not hard but other systems make it simpler) and it's also the ideal place to get "must-have" modules in front of people's eyes. For example, show a list of the categories on one side of the page, and on the other side have a list of the top-10 modules most people use, or maybe suggestions for different types of website even ("Top modules for starting your blog/news/magazine site", "top modules for starting your company website" etc etc and clicking on each shows you the list. I'd also suggest some of the Pro modules would make the list as well as several of them are must-haves for me. Edit: forgot to say that this is the way around it - making things like Tracy one click away after installing ProcessWire, and also getting the obligatory "use third-party modules at your own risk" warning in there whilst also not adding much more to the core.

Thx! I guess for little adjustments hooks would be the way to go. If it is more then it might be better to create a custom theme. The goal of my module / workflow is really just to "skin" the current backend a little to feel more familiar for my clients.

Don't be done, please. We need your valuable opinions.

@adrian Thank you for your concern. All five points are valid arguments, I support them all. And thank you even more for your steady effort to improve this valuable tool!

That's not a bad idea, I love writing tutorial and that thought has always been there, maybe it is something I can look at except that payment issues is one that discourages me from sure since my country has so many restrictions, but it is something that is due. A book someone can follow from scratch to finish. Good idea

Hi @Jonathan Lahijani, Thanks for work on this! I know your previous work and you make some great videos. I'd like to venture a few opinions if I may? For this sort of video, I think what would work best is an explainer video. Basically, a 'selling points' or 'attention grabber' sort of video. The segment should be between 40 seconds to 1 minute, tops! This is the sort of video you would make using Powtoon, Biteable or Spark. In other words, why should I use ProcessWire or what's unique about ProcessWire? This, IMHO, should be about the top-level /overarching selling points and not about the details. I think we should stick to 3, maximum 4 top selling points about ProcessWire. These can include: Easy-to-use and powerful API OR maybe consistent and powerful API? Security/Secure Custom fields Modularity Free and open source(?) > this maybe can be added as a one liner, even at the end of the video (and it's not really a unique selling point per se) An explainer video does not need to show off the full range of the power of ProcessWire. It just needs to grab the attention of the curious developer, to get a foot in the door, so to speak. Hence, the specific details, e.g. Matrix Fieldtype, procache, formbuilder, Github, etc, are for other (more) videos and are not ideal for 'an intro to ProcessWire' sort of video. In addition, ‘the going through the backend’, IMHO, should not be the focus of this video. These are for a ‘tour of the backend’ sort of video, which an explainer video, due to its length, cannot adequately cover since it will feel rushed and crammed. Ideally, the explainer video should be geared towards our target audience (which seems to be web developers), but this may be difficult to pull off. It’s best to try to fit text into one liners, rather than wrap-around texts, if possible. If the final website is going to change, and this video will show the website, you might want to hold off until then? Finally, I am not saying that it should be an animated video. I think the most important thing is that it should be simple, concise and clear but most of all, really 'sell me' to the idea of ProcessWire. Thanks.

Thx. One more: I was happy to see the https://processwire.com/newsite/about/wordpress-vs-processwire/ section, but I still think this could be greatly improved. What about Joomla? What about Typo3? What about Drupal? I think there are a lot of people looking for alternatives and nowadays it's popular to just google "drupal alternative". It's a great user experience to get a tailored answer to that question. That's also true for the WortPress comparison page. I see https://runcloud.io/alternative/serverpilot-alternative.html as a very good example how those kind of pages could be done. Maybe with a "get more details" link on the end of that page for useres that are even more interested...

I've played a bit with the homepage, trying to adjust what is off IMHO. I've changed the font with Open Sans, improved padding and spacing, changed the main background color with the one we have right now in the header of the backend. Replaced the logo with the "old" one (I really love the color combination and fonts pairing). Moreover I've quickly swapped the iMac with a flat browser with a (really rough) image of the backend. Of course the double icons you see scattered here and there are not intended to exist (they appeared when I've saved the html, dunno why).

Great website update. Even if it's not 100% finished, it's miles better than the current website. Plus you got a lot of helpful criticism from many talented people already, which will definitely help improve it further. I feel like 2019 is going to be a really interesting year for ProcessWire. Keep up the amazing work. Edit: It's been said in different topics already, but not really highlighted that much here. Like Bernhard, I think "headless" is a powerful marketing buzzword these days that could be used on the homepage. ?

First of all: Congrats to the new site, it's a huge improvement! I also second almost all comments, but want to comment a few: Hey Pete, good to hear that :) Maybe NOLT could be a helpful tool for this purpose: It's dead simple and free: https://53261ae5.nolt.io/ +1 +1 @Jonathan Lahijani did you see my comment here? ?

I am in the process of putting together a questionnaire which will ask questions like "what features do you think are missing form the core" (not the actual wording, but you get the idea) so hopefully that will be ready soon and I'll be collating answers. I think with so many great ideas discussed daily over the forums, Ryan almost certainly doesn't see every last one, so hopefully with a questionnaire to kick off 2019 if there are common requests from PW users that can help focus attention in certain areas.

I think Tracy is great, but it is not part of the core. So when users decided and finally download PW, then Tracy is missing. However, it would be good as a playground like Codepen where you can directly test API snippets. But please also think about, what destructive commands could mean. They could destroy the whole demo site. Don't know, what is possible when demo mode is enabled in PW config. I strongly believe, that Tracy should be part of the core, as it is simplifies development and debugging very much. How can we convince Ryan to integrate it into the core? Maybe this another thread because it is off-topic here.

love it and think most little bits have been picked up. On the design side if possible restricting wide text sections like quotes on the homepage to a restricted width so that word count on each line is between 10-16 words will help people read it without getting lost on the jump to a new line. This both helps people read and looks nicer as it adds white space on wider screens breaking up the sections.

Nice work ! What a refresh ! ? As two-cents frontend dev, I think that the Download and Demo buttons on the start page could deserve a "better" ghost-button. Additionally, on the "Demo" button, I would see a 'bolt' icon more than a 'map-marker' (the 'rocket' icon should be perfect but not integrated in the UIKit framework I think). This ! Those last years, despite every module being a gift for the community, Tracy has become THE tool to build those gifts. It is also THE tool for peoples who like to offer support for free to the community. And without speaking about support or modules dev. but globally, the experienced or newbies developers, once they get their hand on Tracy, they speed up their development workflow. Just to say that @adrian made a crazy job with Tracy and it give to ProcessWire more strength (than it already have), so yes, definitively yes ☝️

@Pete In my eyes, this would be the perfect solution

Quick one on the blog comments - it is technically possible to have the forums automatically create a new topic in this forum when a blog post is published, show comments from that topic below the blog post, but also allow you to sign in on the website at the location of the comments form itself and comment there as normal. Would that be preferable to keep all comments in the forums from what people are saying? If you're logged in on the forums already there would be no requirement to login from the blog post again - it would know you're logged in. The form itself would likely be more basic there as I've found embedding the full-featured forum editor tricky in the past, but think this solution might be the best of both worlds to keep the conversation happening here in the community forums if that's what people would prefer?

Well I couldn't get sitemod.io working (at least not the way I wanted) so I built my own version - using PW of course ? https://sitemod.robin.nz/ This lets you render any site with a custom CSS file and/or a custom JS file added. Links on the site are rewritten so you can browse around the site and keep your custom CSS/JS. Not much testing done yet so expect some bugs. Here is the new PW site with a max-width applied and the font switched for Work Sans. As I've said elsewhere, I'm really not a fan of the current font and I think this looks much more professional. https://sitemod.robin.nz/render/?url=https%3A%2F%2Fprocesswire.com%2Fnewsite%2F&amp;css=https%3A%2F%2Fsitemod.robin.nz%2Fnew-pw%2Fmod-1.css

If you’d like my unadulterated perspective: I think the way PW is communicated is too verbose and complicated. The concept of Pages doesn’t make this any easier. It’s almost like that term has outlived what the product has become known for: power a website or something altogether different. Just look at the Pages overview and you see how it could be totally perplexing to a newbie. Words have meaning and sometimes wisdom requires rethinking how we communicate. Despite being new—having built three or four websites with it—I love this product and hope more people come to appreciate what Ryan has built.

Hi Ryan, Not exactly sure how this would look or work at the moment, but what do you think about having the Tracy Console panel available on the demo site so that users can play around with the API. I am thinking of having some snippets in the snippet sidebar already saved so that they can load those as starting points / examples. Some examples would show using d() calls to return objects, but we could also have some with echo outputting actual HTML with PW variables embedded. Think of this as ProcessWire codepen / fiddle type feature. Obviously save operations etc would have to be prevented so they can't damage the demo site. On another note, maybe down the road users could have access to their own demo site like Wagtail does (https://control.divio.com/demo/get-new/wagtail/) where the user can actually edit page content and see the changes on the frontend - a little like the old lightning.pw Anyway, let me know what you think about the Tracy Console idea.

Working on this, which I hope to finish off at some point in a couple weeks after the main site launch: It will be 2 minutes and 11 seconds long, which is the length of the audio (full audio here). I will try to make it show off the power of ProcessWire as much as possible (tree, fields, matrix, front-end editing, api, docs, formbuilder, procache, github activity). I may need to extend the music a bit for it all to fit. Anyway, this is happening!

A few more thoughts: I feel like the Selectors page (http://processwire.com/newsite/docs/selectors/) needs to be more prominent. To me, this is more useful than the current "Getting Started" and "Tutorials" pages. Or at least, it should be a page that is listed on the Getting Started page. Speaking of the tutorials page, I don't like that most of these are external links - even though they are great resources, I'd rather have users see a centralized source of the best tutorials on the PW site itself. I don't like the pages that put the title next to the PW logo in the header, especially given that not all pages do this - I know it depends on what level page you are on (although not entirely), but I still find it a little confusing. I also don't think that the "Community" top level link should go anywhere. On the variables page, you have: "page() accessing as a function can be very convenient, when available." - how or why wouldn't it be available? I know, but new users won't. This one: $pages->wire('page') is actually quite confusing - again, I get it, but certainly never thought to use it like this and I think it would be really weird to do something like: $pages->wire('fields') I would say this option should not be shown. I also am not sure about showing: $this->page when on the very next line you state that: $this->wire('page') is more efficient - why would anyone want to user the former? Sorry for all the negative, but you know how feedback often is ?

Anyone interested in the module with added region option and with added o:deliverytime option can use my fork at https://github.com/gebeer/WireMailMailgun