Leaderboard

As first discussed here: https://processwire.com/talk/topic/20596-new-post-new-pw-website-ready/?do=findComment&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.

First work in progress version ? Built with vue.js for fast DOM updates. Needs to be AJAXified and more details. So maybe wait a little bit with feedback. I know there is lots of information missing. OK, now I go to sleep, because it's 4:30 am and I am invited to a birthday today.

@ryan, the new site search is great - such an improvement over the previous version. After searching I find myself trying to use the keyboard (arrow keys, enter) to highlight and select results, like I can in the PW admin search. Would it be possible to add this feature to the processwire.com search?

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/

Well, the improved module manager/installler shows which modules you have installed and which can be installed or upgraded with one click (ok actually it's 2 clicks). Why should you leave your PW installation to go to the ProcessWire modules website, of which you have to be aware of, search for a module, copy or remember the module name, go back to your ProcessWire installation, paste the module name, click on "get module info" and finally install the module? Make it easy for everybody! Lower the barrier for new users, and make it easier for existing users to find an install modules. That is one thing, that many other frameworks/CMS's have by default. Like ModX, WordPress or PrestaShop. Right now I am making good progress with the development of the module. I will post an updated screenshot a little bit later or tomorrow. Please note, that this is actually working, it is not only a mockup. Data is fetched and cached and then being used to display the modules with all information: Here are some more features I am planning to integrate: Live-Search/Filtering Quick uninstallation/disabling of a module Top modules label, so users can see modules that are being used the most (based on the likes, sadly we have no module installation counter) I will put it up on Github, as soon as it is in a presentable state, and you guys can improve it further. You can also write your thoughts and wishes here.

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

Checked the first ~100 300 SERP Links from site:processwire.com in Google and almost all links redirect (301) or are still correct/corrected. Only 4 9 ended on a 404 page: https://processwire.com/videos/lister/ https://processwire.com/api/what/ https://processwire.com/api/types/nullpage/ https://processwire.com/about/chat/ https://processwire.com/videos/managing-portfolio-site/ https://processwire.com/api/selectors/inputfield-dependencies/ https://processwire.com/docs/tutorials/troubleshooting-guide/ https://processwire.com/api/ref/inputfield-wrapper/ https://processwire.com/videos/page-fieldtype/

@adrian I am developing it as a module for now, but at a later point will replace ProcessModule with my code. For getting the JSON data I used code from Somas Module Manager, which seems to get only the 350 items you mentioned ? We have to think of a way, to get them in batches, or @ryan has to change the limit. I did not thought about the complications yet when the limit is higher. I got filtering working, but not in the way I want. Some things turn out to be more complicated than I thought. Anyways, here's a lil teaser for you guys ?

Hi @ryan, Could we get the current version numbers back on the master/dev download buttons?

Just wanted to share the simplest language switcher possible if you only have two languages: <a href="<?= $page->localUrl($languages->findOther()->first()) ?>">DE/EN</a> 😎🤘

I hope to come up with a mockup/prototype the next few days/weeks. Here are my thoughts: We can use @Soma Module Manager as a starting base for getting information about the modules overview and each individual module. There is an API for getting information about modules available at http://modules.processwire.com/export-json/ or for a specific module like TracyDebugger http://modules.processwire.com/export-json/tracy-debugger/?apikey=pw223 sadly, we can't get the install instructions or readme via this API. Maybe we can use something in addition to get more detailed information. Of course this information should be cached, and there should be an option to force reload the information. My approach would be a nice looking filterable overview, which also can be sorted like on the modules directory Each module should have an "Install" button and a detail button which opens a panel/popup that shows extended information about this module (for example the readme) Filtering could be very simple but I am in love with filtering like isotope or mixitup. Luckily Uikit also comes with a component for similar filtering: https://getuikit.com/docs/filter We also should stick to default AdminThemeUikit styling, so it integrates nicely into PW and maybe one day replaces the old (actual) installer.

Yep, I've got profilerpro monitoring them and if any url gets more than a couple hits then I add a redirect. It looks like there were a few I missed but slowly accounting for them as they pop up.

Thanks for all your work on this @jmartsch - are you planning this as a third party module? I assumed we were trying to integrate these changes into the core modules installer interface, at least that's what I have done with the above autocomplete interface. I think it would also make sense this way because then we can both share the cached modue data json. On that note, are you getting the data in batches? I ask because the json feed is limited to 350 modules and we have more than that.

Adding pagination to your category template should be quite straight forward. There are step-by-step instructions and examples at https://processwire.com/docs/front-end/markup-pager-nav/

The reason for "rebuilding" the categories layout into the module (though it's not a hard build to be honest) is that it lowers the barrier to entry further. It's just a convenience thing, but also a way to prevent new users having to go back and forth straight after installation. It's also how some other CMS's do it so it would also be intuitive for those users and just a nice bonus for the rest of us. I guess they will need to go to the PW site anyway for things like docs, but I think installation and setup should be made as simple as possible ideally. Nothing about the current setup is hard of course, but less clicks and easier/quicker module discovery would be a nice bonus - I'm a PW veteran and I honestly don't scour the modules directory for new modules often, but if there were a feed of recommended or new modules within PW itself that would help lazy people like me to not overlook things like Tracy ?

Does anyone know if all the old URLs that Google had indexed have been updated to the new URLs? If not, there'll be a pretty big dive in SEO rankings. As an example, I was searching for some API info and was brought to this page https://www.google.com/search?q=processwire+selector+limit&amp;rlz=1C5CHFA_enIE731IE731&amp;oq=processwire+selector+limit&amp;aqs=chrome..69i57j0.6332j1j7&amp;sourceid=chrome&amp;ie=UTF-8 If you click on the search result, you'll be taken to a 404 page etc.

Hehe so much for not having much time ? Since you guys are a million miles faster than I am what I'll try to do today and tomorrow is an interface mockup for how I think it could look with categories and thus favourites idea so we've got a few ideas to pull from. In terms of instructions for modules - they're hit and miss as to whether they're on a GitHub readme.md file or entered into the Modules directory itself, but I think the code on the Modules directory can easily be tweaked to pull from either source. I also don't think that there are so many modules that if we thought there was some other essential functionality that was required (like something that HAD to be read before install) that there could easily be an extra field added to the DB to flag that up in a consistent manner. Sure there are a lot of modules, but for better or worse there are a lot of ways to store the config info too so maybe the Modules database itself is the only consistent way around that if we need to? Will post more later. Got to paint a kitchen first (yay ??)

@ryan - I feel like on the API ref main page the classes should be below the variables, or at least the variables should be on the left, but I prefer the former with two columns still, but with Primary left, Input & Output right, Users & Access left, etc .... My reason being that for the most part variables are the main thing that is used in template files - these are what beginners need to know about. The classes themselves are generally a step removed from the code we are writing. The main exception is probably pagefiles/pageimages. The rest are used much less frequently. Interestingly when you are viewing an individual variable or class and the left sidebar is showing, the variables are on top.

@adrian It would also be nice if we could install multiple modules at once like you do with your https://github.com/adrianbj/ProcessModuleToolkit So we have to be able to select multiple modules, then click install, and magic happens ?

Nothing ? I fixed this. Update to 1.0.9

This is a cool idea. I will start creating a course, but it has no the contents, but in the following weeks I will start uploading videos.

I guess nvim is earning money in other ways... Still can't understand why nothing is done...

It didn't this morning when I first checked after @Peter Knight's post so I'd say Ryan has added a redirect.

Redirects me to: https://processwire.com/docs/selectors/

Wouldn't it be a lot more efficient and easy to serve one json file with all modules? At the moment we have around 25x23 modules in the directory, that's 575. For example displaying those with RockGrid would be easy and fast and filters would already be there. Not saying RockGrid is the best solution, just throwing in a concept for discussion you might not have thought of yet (meaning doing the work on the client side and not on the server). And this JSON could be served via procache, so it would need very little resources.

Maybe Ryan can introduce pagination in the public API ? E.g.: ../exportjson?limit=10&start=350 This is not uncommon in high-traffic public APIs.

There is an option to hide certain categories from listing, this could also be made configurable via module settings, but this is not my priority right now.

Thank You very much! Great answers! Have a great weekend.

@kuba2 1. yes 2. yes, after you've uploaded all the PW files to the new domain name folder When the new website URL/domain name is on the same server/web hosting account and has access to the same database, all you need to change is the site/config.php https hosts array to accept the new URL(s). Easy, peasy, lemon squeezy ? PS: either put the new URL(s) at the start of the $config->httpHosts array to give them priority or remove the old ones to prevent PW confusion

Thanks for your input - I totally agree that we need a browsable / filterable interface as well. Let's start discussing this more over here:

You must have edited the wrong file then ?. That's exactly where it is.

Hey @adrian and @Pete I think a revamped module installer would be great. Adrian's AJAX approach is a nice addition for devs who know what they are looking for. But for all others we need a browsable experience. We should open another forum topic for this. I might come up with an initial mockup as a starting point in the next weeks, but as always my time is limited. First I have to update the german language files for the new PW dev version.

Just a thought but instead of diving in headfirst, maybe those interested in creating content whether articles or video should create a content outline. - Purpose of said educational piece - Overview of what students will be learning - Framework requirements (version of PW; any modules required, etc.) - Section overviews (think of this as chapter titles in a book and brief description of what’s covered) - Paid or free Those are a few thoughts. Although I am not a programmer, from a brand standpoint, I’ve watched Laravel develop from its inception. It’s been a beautiful process to watch. And it’s been successful for being opinionated and rigorous in documentation, besides paying attention to the craft of good design.

You have to change .gridImage:hover .gridImage__inner { background: ...; } The original file seems to be @ wire/modules/Inputfield/InputfieldImage/InputfieldImage.css

<?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.

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

I played around a little and came up with this dark theme: All you have to change are these colors: // ############################################ // ########## main color definitions ########## // ############################################ @tm-primary-color: #52227a; @tm-secondary-color: #22b7c7; @tm-text-color: #313131; @tm-muted: #e7e7e7; // ############################################ // ############################################ // ############################################ All reno variable definitions could be moved into a separate file (like dark.less), but for testing it's nicer to have colorization support in my IDE. Totally different look&feel of the admin with no effort: ? Also on small screens: I tried to use neutral grey colors wherever possible, so changing only the main color should be enough to get a totally different and still good looking optic: Nice, hm? ? Does anybody know how to change this color? Somehow I was not able to find the correct file where this is specified...

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:

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.

@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?

Yes it is possible but it depends on your needs. I also built several software with ProcessWire as a base. But you have to tweak the backend to your likings (which requires much hooks), or create an own backend instead of the default one.

I've just updated the PW search function in the PW Info panel to use the new website's search functionality for all sections, except the forum (where I still use Google) and of course the Github repo. Hopefully you'll find this is nice shortcut to the new PW site search which is really great!

Just committed a nice little enhancement to the Adminer panel - it now loads the panel with the relevant table or row based on the current context. So if you are editing a page, it will load the row for that page. If you are editing a file, template, or viewing a module's config settings, it will do the same. If you viewing the main page list tree or the main templates/files/modules pages, these tables will be opened in browse mode. Probably not something you'll use that often, but because the Adminer panel doesn't load anything until you open it, I like leaving it activated as one of my default panels so I always have really quick access to view whatever is in the DB for what I am currently working on. Anyway, hope you all find it useful on occasion.

I use these settings 'rgba(68, 100, 221, 0.98)' But the issue looks like this (render) rgba(234, 25, 25, 0,93) but I need it so rgba(234, 25, 25, 0.93) what am I doing wrong