Leaderboard

First of all, hats off to everyone involved in the redesign! I can only imagine the countless hours that must have gone into this project – really impressive work. Of course, a redesign will always divide opinions. Some will love it, some won’t – that’s the nature of design (a bit like beer: there’s no accounting for taste). But let me share a perspective from my three decades of experience working with clients: 99% of paying clients couldn’t care less about what CMS powers their site. What matters to them is that the website looks good and feels professional. The ones we really need to convince are the second tier of decision-makers: the people who will actually use the system day-to-day. These users are rarely designers. They don’t care much about animations or typographic finesse – what matters to them is clarity, ease of use, and a sense that the CMS won’t get in their way. That’s why, in practice, we almost never show clients a backend during the decision-making phase. Instead, we show them beautiful, carefully crafted frontends, and sometimes highlight the inline editing capabilities. That sells. Clients are impressed when they see polished websites that “might be running on ProcessWire” (since, let’s be honest, you can’t tell a CMS from the frontend anyway). How this focus on real-world client priorities could be reflected more strongly in the redesigned ProcessWire website is something I’d love to explore further. Cheers, Mike

Hi all! Just wanted to say hi and comment that I truly love the new website, it looks and feels great, both mobile and on desktop. It also has its own unique look instead of general day-to-day trends we so often see. Great work @diogo @jploch and @ryan! While we don't use ProcessWire at my current job, I still maintain few PW sites and I love the experience. Miss the community a lot, stay health and happy everyone!

Nothing that can't be handled by your module but I'm planning to add some extra details outside of table data like total counters of specific users etc. and some filters too.

Thanks for the info but I ended up creating my own custom modules specifically for a project for displaying lists like users, transactions etc. It was about time to learn about MarkupAdminDataTable and it was easy 😎 thanks to the explantion of @bernhard guide.

ProcessWire can never be WordPress with its famous fast install, precisely because of ProcessWire's flexibility. The appeal has to be to developers, or designers who know a little code, but don't want to have to get stuck into learning a lot of code. I think with more site profiles, using popular CSS frameworks to enable easy customisation, ProcessWire could maybe grab some of those WordPress users, as the installation process is quick and easy, it's just the customisation that takes time, and if there's a profile that meets your needs, it's as quick to get a site up as WordPress. It's when you need anything else WordPress is horrible. Maybe there needs to be an option for paid site profiles? One of the issues with profiles is that they're applicable at install time only, but via something like RockMigrations it would be possible to have a profile like a blog profile, but then multiple migration files that can theme the same data differently. I wonder whether rather than calling things site profiles, calling them ProcessWire apps might better convey what they are - or not? I think the key message I'd be wanting conveyed to other developers and potential clients is 'build anything - fast'. Much as I dislike Wordpress, it's claim to fame, 'build a blog - fast' it actually can deliver on pretty well. It's when you try to build anything else with it that it starts getting horrible. Incidentally, I just took a look at wordpress.org, and if I didn't know any better, visually comparing that to ProcessWire, I'd choose WordPress. It starts off quickly summarising what it does, then with a bit of scrolling gives a bunch of screenshots of the diversity of things people have build with it. The only call to action on the ProccessWire site is 'download', and mostly impersonal, whereas wordpress.org is full of personal calls to action: 'Get', 'Meet', 'Discover', 'Explore' ... The site uses some similar large fonts and a lot of visuals, but the above the fold content gets to the point quickly. The big stuff comes after scrolling. Since I'm being critical, I'm happy to write something and send it through for evaluation, as I have benefited from the ProcessWire community. I'm not a designer, or probably even really a marketer, but I I do have a bit of interest in language, and I think the text could be significantly improved to be more compelling. Here are a couple of examples of how I'd rewrite things: Save time and work your way with ProcessWire, a free content management system (CMS) and framework (CMF). Enjoy all custom fields, a secure foundation, proven scalability and performance. Take control over the design You can define and edit all fields in ProcessWire easily in the admin. You can create as many of them as you want, and of any type. You can even bundle them in repeatable groups called Repeater fields. You control all of the markup, not ProcessWire. If I want to sell end users on ProcessWire I want to show them it can be as pretty as WordPress and more capable. Luckily here in NZ I can just refer them to the portfolio site of @Robin S as he's done a number of high profile sites that are well known nationwide, and I can say 'built using the same system', and also reassure them that I'm not the only ProcessWire developer out there. (It helps that I'm a regular visitor to several of the sites he's built too.)

Hi, @PWaddict, here is how to make use of the permission: Create the permission data-table-view and add a distinct description to it. Create a role (lets say its called „data-viewer“) and add the permission data-table-view: Make sure the template datatable has granted view access to that role: Make sure the template admin has granted view access to that role: Then all of your existing DataTable pages should show view access for that role:

Thanks for the findings, @PWaddict. We fixed these issues in version 2.4.5. Please upgrade 😉