wbmnfktr

No. Not right now. Everything works but that part is missing.

More than a year ago I said I would try TailwindCSS... now it finally happened and... and the result is disastrous! Well... disastrous for my opinion back then and my thoughts about it until a few weeks back. I am quite surprised and happy with the result, to be honest. I did a rebuild of an ongoing side-project, with a full rebuild of the whole site structure all the way through to any breakpoints (CSS only, HTML was kept except additional classes). Yet some parts are still outside of TailwindCSS as those are really custom and are way better placed in an additional CSS file. Even though you can customize TailwindCSS to almost all of your needs but I didn't want to bother with it for now. The change in file size is quite dramatic... or even super awesome. However you want to see it. I went from... 59kb (the whole project) down to 17kb (structure - based on TailwindCSS CLI generated .css file) PLUS 5kb custom CSS for colors, custom properties PLUS 10kb custom CSS for icons, backgrounds, and fonts PLUS unknown size of additional kb within HTML due to those TailwindCSS classes Ignore those other files as those are helpers or part of other instances within that setup. Which is in total: 32kb for the full project, all pages, all icons, all fonts. Yet... the whole setup isn't ready for production right now as my setup only really works with 11ty as a middle-man for now and not within my PW workflows... but that's another story. There are probably even more things I could optimise in terms of fonts, icons and custom classes for colors. But for now... WOW... I always was against those utility frameworks and didn't like them at all. I am and always was a VanillaCSS Purist... didn't ever really like Bootstrap, UIKIT or anything like that, but TailwindCSS could and might have changed my mind. From now on... I might have to think and work different for some or another reason. Right now my test was built on a project I really knew in and out with all its details. Let's see how it works out in a real and new project. Results based on: TailwindCSS 3.1.2 (latest - as of now, 2022-06-14. all file sizes unzipped, without plugins like Typography)

My latest and most recent experience with JS was AlpineJS. Never heard of Yoast JS so far and asking Google doesn't help that much for now.

This would be awesome!

Excellent!

Well... yes. It does exactly that. If I understand your statement correct. Changing things in the backend and viewing all those changes happening in realtime in the frontend. That works perfectly fine. At least for content. I use this in a side project and each and every editor is super happy. In terms of code changes (templates)... it wouldn't do the trick.

The backend really looks amazing! Really a nice job. Yet... I somehow experienced a quite slow experience on-site. And I doublechecked. Somehow the site underperforms in terms of PW. For whatever reason. web.dev/measure and ScreamingFrog result in a ... not so great experience but I can't point my finger on it. Some routes seem unnecessary for me but those are some-what understandable. Is the hosting in one way or another maybe not that perfect?

So... maybe ask them what they would like to use or recommend in first place and go from there. Depending on the setup you could also look into environment variables which sit in places far away from any web root. Another thing could be a mail account which is only used for that website. Or you use something like Mailgun, Mailjet or similar which is a 3rd party service and therefore all details sit on yet another server. I personally use Mailjet which is configured in a way that only my website can send mails through that account, still everything via SMTP. So... even if someone can get a copy of my credentials they still would need access to the server or the Mailjet account to do anything with it.

Something like this?

Same for Outlook, Yandex, Zoho and everything that needs either an "App password" or 2FA (2 Factor Auth). Another thing: sometimes it's necessary to use different ports (for whatever reason) so it's either 465, 587, or even 2525. Just double-check here.

Super OT: When I started using ProcessWire I only knew the templating syntax of Textpattern and was fine with it as it handled everything I ever needed. (I loved it! Really.) All I was able to do in PHP was a Hello World!. Within a day or two I moved my personal site from TXP to PW, launched a side project within the first week, did a rebuild of other side projects in the first few weeks and a real-life-project shortly after that run for about 5 years. Best learning experience ever! So yes... you can even learn the basics of PHP while using ProcessWire and go from there. Maybe PHP-Dev-Starters should use ProcessWire as a starting point - yes, that's my real and honest opinion. The tutorials and (later on) the docs can do that!

Sorry for the delay... I was outside (as in outdoors, enjoying the offline time) and took a while off from the desk. There is so much great feedback and yes... maybe I was wrong about the 7G firewall solution. Still can't find what I was thinking about. Nonetheless... the task was postponed a bit so I can dig a little deeper in all your comments and maybe give this a try. Thanks you so much @horst and @FireWire!

Oh my... that Heise comment-thread developed to a gold mine. Thanks to all of you that posted there. That was such a nice read! Looking around I think I found about 2 of the 3 commentators. Great job!

Can't read it due to heise+, yet interesting to see it there. Posted yesterday... I wish we knew if the author Daniel Berger is around here somewhere. The comment section is Gold as always. Maybe we should comment there as well. https://www.heise.de/forum/heise-online/Kommentare/WordPress-Alternative-Websites-flexibel-gestalten-und-verwalten-mit-ProcessWire/Bitte-nicht/posting-40820682/show/ Use Google Translate to read the whole comment - you will enjoy it. Don't really know what the comment author is talking about. It's at least not about the ProcessWire I know.

Actually didn't even think about those until know. Some parts in it could work out pretty well, like request URLs. That's a good tip! Someone told me about it a while back and it doesn't work that well (if at all) with ProCache as PHP is involved if I remember correctly. Still... will look into it again.

To make it really short: There is a project of mine that gets about 5.000 to close to x.000 requests each day to common standard folders (WP, PHPMyAdmin, Backups, Gallery Scripts, and everything that has been on a 0day-list in the last 10 years) in addition to the regular site requests/traffic. I will and need to to bypass 404s similar like @ryan wrote in this tutorial. I disabled 404-monitoring in Jumplinks a while back as the database grew each minute and wasn't "maintainable" anymore - due to auto backups each day. https://processwire.com/blog/posts/optimizing-404s-in-processwire/ Has anyone additional tips in regards to this guide from Ryan? Something to consider? Something that needs special attention? Something that didn't or doesn't work anymore? Or should I already block all this requests in the CDN somehow? Feedback welcome. I will start this little project next weekend. So... don't worry with feedback. And if you ask... I actually prefer adding those block rules to the CDN somehow.

Are there markup-regions involved in your setup that maybe interfere here? Which version of ProcessWire are you using and which profile is installed?

There are always the description and noted fields in each and every field you offer to editors. Therefore you could add a lot of details and descriptions on how to edit, change, fill or work with a field.

You won't believe it but this is really a big issue in some kind. Not really in terms of ProcessWire but in terms of devs. I recently got part of a team to manage existing ProcessWire websites and... yes... no $sanitizers were involved at all. Can't and won't blame anyone for this. Ok... sure... I could but I won't. My 2ct-opinion on this: That's why I call this the most awesome community ever! (This is a USP, take a note!) We could blame each other in some kind or lay open things that don't match/work at all, yet... after some rumbling everything most of the time turns to the better. And to be fair... I have never ever encountered anyone assaulting anyone here. Rough wordings, maybe. Yet... being direct is needed sometimes. Thank you @MoritzLost for the insights and even for starting this discussion in some way here. (yes... that's my personal opinion!)

Another 2 cents for the "not an essentiall comment"-jar. 1) WHAT A GREAT PLACE!! (by @bernhard) Indeed. This is one of the most friendly, most awesome and most advanced communities around. Hands down. This is almost a bit like "family" - at least for me. Thank you! Therefore... 2) Discussions like this are needed. Really! They are... hard to digest. Unfair. Emotional. Yet worth it at the end. I think ... first of all there are two people here that might want to "enjoy" a 1:1 discussion to clarify things. As both have very good and honest arguments here. This "clash" could and will be good. I personally think that there was only a slight offset in communication and perception - to be honest. Both aren't far away from each other. I personally hate/love those discussion in projects because they become super emotional right from the start and it takes way too long to calm each and everyone down to a common ground afterwards. Especially when there is a large team around that fires up the situation. Oh. But most of the time the project benefits from it. Therefore my idea of a 1:1 here. I personally enjoy giving harsh feedback. While I hate receiving harsh feedback. But that's life... I guess. We grow with it. It's sad that all comments "against" ProcessWire CMS/processwire.com end at one point aka @ryan. I don't know Ryan in person but still a bit through various discussions in various boards, threads and messages and really enjoy all of his insights, feedbacks and even more for what he has built and builds here - with ProcessWire. Has anyone ever noticed that he dedicates his sundays for this community? So much love for this! That's why I fully understand and support Ryan's post and feedback. Even though while Moritz has some good points as well. I understand Moritz's points here in some kind. I have my very own personal issues with ProcessWire CMS - some days more, some day less but most of the time I praise ProcessWire as the best solution ever. As it is for me and my projects. 3) Takeaways so far - for me (you are free to argue against my perception) This thread was and is some kind of bumpy but as Ryan, ProcessWire, and this community are... this is just another challenge we will laugh about in 12 months and enjoy what happened in the meantime all together. 4) Future outlook Maybe we as a community, devs, friends, however you want to call it should start outlining things WE could do. Not only demanding things and asking for whatever. Maybe we could offer solutions instead. Designers could create a new visual look. Marketers could offer USPs and target-group analysis. SEOs could work with that and look up whats interesting compared to other CMSs. AND. SO. ON. I can offer the SEO aspect in this, maybe frontend templates for very fast loading and awesome Google Insight numbers. Count me in on this! Ok. Ok. I put 2 dollars in the jar.

I'm not sure about how or if PageHitCounter tracks URL-segments. A wild guess would be it doesn't. I almost never use them and therefore don't have a testing setup with it right now.

Oh...kay... now I get it. Sure this could happen in some way in or with Composer as well. The r/thread is a nice read. This whole scenario was always the reason why I rarely used and use NPM or Composer - it's so often a big blackbox.

I don't get what you are asking. Could be that's because I don't know that much about composer.

Is your user role excluded from tracking? Is the JS in your site present? Are there errors in the console? Is your HTML valid aka are there ending </body> and </html> tags?

So... just a short heads-up... a node.js module that's widely used - even in vue.js and well known software - was compromised by its developer. It seems that the repository was already cleaned-up again, yet in case you installed the module itself or something with it the last couple of days. Take a closer look, clean it up, fork a clean version whatsoever. https://snyk.io/blog/peacenotwar-malicious-npm-node-ipc-package-vulnerability/ node-ipc-dependencies-list https://github.com/zlw9991/node-ipc-dependencies-list Video with some more details about the whole issue.