Jump to content

wbmnfktr

Members
  • Posts

    1,904
  • Joined

  • Last visited

  • Days Won

    44

Everything posted by wbmnfktr

  1. Just another way to migrate a full install... either via exporting the site profile or while using Duplicator. Maybe you should try that instead. Those manual migrations... I did this for a very long time, yet I always missed something and had to look for the issue for quite some time.
  2. Wasn't that the goal? I'm confused right now. Or maybe worked too little with frontend editing.
  3. Does pasting it with Option + Cmd + Shift + V (Mac) / Ctrl + Shift + V (Windows) helps here?
  4. wbmnfktr

    Appreciation

    The big yellow one? Oh yeah!
  5. wbmnfktr

    Appreciation

    I loved Textpattern so much!
  6. So... I use Devicon for quite a few things across projects and today I looked up ProcessWire... without success. Yes, I was suprised in some kind. See here: https://devicon.dev/ It's possible to request an icon to be added - see here: https://github.com/devicons/devicon/wiki/Requesting-an-Icon (Issues: https://github.com/devicons/devicon/issues/new/choose) Who is able to offer, provide, and/or upload the official files with the correct colors and settings? The whole topic isn't super critical for me, but it would be another way to show ProcessWire is serious.
  7. No judgement in regards to WordPress, just an interesting article. https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/
  8. Actually found the time to use a VPN to inspect that site (ProtonVPN, and TunnelBear VPN work great) now, and... I already have a complaint to file. While the site overall seems perfectly fine, the header slider is super bad in my opinion. Those topics seem quite important to possible website visitors, maybe even the only reason to look that site up, and those topics are somewhat hidden, while they could be a major navigational point/entry on the homepage or maybe even every page. I'm not sure if this is the case but they sound quite important to me, and shouldn't be hidden in an element that doesn't even indicate it's a multi-topic/multi-element slider. On the other hand it does seem to be super straight forward to get the things done. I'm not sure what's exactly happening at each and every part of that site but compared to our german sites... few steps ahead. At least compared my village (yes, only ~280 people around here) we still can't do things online. Besides complaining online forms don't work. Jokes aside. I am not a designer and therefore really enjoy a functional website that does what it should. Therefore great work in most parts. At least for what I can tell.
  9. I don't want to hijack this topic too much, yet I have to ask. Is unpoly worth the ~50kb? Even combined are AlpineJS and HTMX less than that. And there would still be a place for BarbaJS. I use AlpineJS in bigger projects that have quite some heavy lifting in terms of JS-needs and are more than just a simple website. HTMX looks pretty fantastic, yet I didn't build more than a few simple proof-of-concept projects with it for now. Which is sad. Smaller projects get the VanillaJS-treatment and JS is down to less than 5kb. unpoly looks super interesting but the ~50kb are such a bummer. That's more than the average page size without images.
  10. That's why Softaculous announced a new version in their installer. Until this moment I thought they'd support the DEV versions now and was totally thrilled... but ok. I'm totally for it. That signals ProcessWire is alive and well (see the Softaculous post above) and people can see it. To be honest here: we all should push way more details about your and the overall work on and the features of ProcessWire to the outside world. But that's another topic for another day. Have a great weekend, @ryan!
  11. Wow... that's fascinating in some way as I just made my move back to good old ProcessWire with some nice additional extras. Like TailwindCSS and AlpineJS - HTMX is on the list - but that's it. So, yeah... still some Node.js and build scripts involved but that's fine for me. I even moved some small sideprojects from 11ty and Astro back to ProcessWire just because it's way more solid, real, or something like that. Can't describe it. Weird I enjoy ProcessWire right now way more than 12 months ago just by using totally different tools for a few months.
  12. I have had the very exact thoughts about this for quite some time. What are your reasons here, beside super heavy JS-frontends (React, Preact, Nuxt, Next,...)?
  13. I played around and worked a lot with Astro in the last few months, and one thing I really liked was working with <Components />. Right now I try to move my experience from it towards my PW/Twig/Latte setup. Some parts work pretty well, while some things don't work out as expected. Splitting parts isn't that easy in PW, when using PW and Tailwind. Due to the missing build-step. But ok. I can live with it. When using plain CSS, this could be a totally different thing. Yet the CSS and JS isn't scoped. Boooh! I didn't use plain CSS for about 18 months now - which is wild, as I was a plain-CSS-advocate since always. But I am working on it again, which feels super awkward on its own right now, as PW is totally different compared to Astro or the tools I used in the last months. I could imagine using <Components /> in one way or another using Twig/Latte and some ProCache-magic... I could minimize CSS way more, yet I don't know if all that is really necessary. For what I can tell right now... each release with PW and JS/CSS is way bigger than in Astro, as PW has no real page-based build-step. That's fine for me, as most of my projects are super minimal right from the start and get 4x 100 in Google Pagespeed. To be really honest... I am at a point right now in which I really don't care about the last 100-500ms in a pagespeed tool anymore when I at leat get the 94 scores for each step. Addional note: Right now I work on a 11ty/Astro setup that loads all data, pages, and structure from PW in JSON-format. Loading all data (from https://www.restaurants-neumuenster.de/) takes about 1-2 seconds in total while building all pages, data entries, and everything else takes another 3-5 seconds. It works, yet I don't like the result somehow. There are things I really don't like and have to fix in JS/Nunjucks/Liquid or some other parts of the setup. Right now: I focus really on optimized PW Twig/Latte workflows and for minimals sites using JSON using 11ty/Astro as frontend layer.
  14. So much fun stuff to play with...
  15. So... Randy just announced a new VS Code extension to manage DDEV instances. https://marketplace.visualstudio.com/items?itemName=biati.ddev-manager
  16. Please check that you have all the basic HTML tags, including closing tags. Most of the time this kind of issue appears when there are missing </body> or </html> tags. ProCache looks for some pointers in your pages to find the start and end of a page to know which parts it needs to handle in which way. So make sure all basic HTML tags from opening to closing tags exist in your template. html head body If that doesn't help and as you can't share the site itself, maybe you could copy the source code of one of those pages, clean it up, and make it available for us to take a look.
  17. Nice presentation here. As always. I was kind of suprised to see so little feedback or knowledge about DDEV, MAMP, and Laragon. What were they using? Real servers in a local network? Either way... The interview was a great surprise. He seems to be a great guy with lots of knowledge in every space someone could imagine.
  18. Ok. Now this makes kind of sense to me. It's not about the composer packages in ProcessWire I deal with once in a while in a project, but with those I (never will) develop for later use. This seems to be quite a lot of work for, what I would call it, a simple task like that. But ok, I don't know anything about developing composer packages - that has to be said. Thanks for that detailed answer and background on this. At least I can relax now and know I didn't break a few projects because I used composer packages in a wrong way or something.
  19. Woah... (positive and surprised emphasis here) The graph I posted above made it super easy for me to understand differences in loading JS while the one you mentioned... did the absolute opposite. It did almost nothing for me on first look to understand anything. I have to read, have to compare, this, and that... which isn't that of a problem but for a quick first look while trying to understand. NOPE. Sure, the one from your example explains a lot more (which is great), talks about differences, and you learn way more yet ... just looking at it doesn't work for me, what the other one does. Sometimes I just need a good visual hint that explains a more or less complex situation, which mine did (for me at least). That was the reason I posted it here. So we are quite different in consuming such information, and that's super interesting.
  20. @elabx what's the reason behind the setup you describe here? I probably missed a lot or just don't understand it what's in previous parts of this discussion. You mentioned this: So... as far as I can understand this - combined with the rest - it's something more or less outside of the usual ProcessWire realm aka developing/working on a composer package. Am I right with this? I am just wondering if I missed something in regards of handling composer packages in ProcessWire and DDEV while working on a project.
  21. He has different formats, but yes... "reaction" videos are special. Still I really enjoyed this one (and the original video).
  22. Markup regions are a super interesting concept but I never really used them. It always felt a bit weird. So can't say that much about that concept in everyday use. I prefer using Direct Output. There is absolutely nothing wrong with it. I'd go so far and say it's the perfect way to start playing with ProcessWire. All you really need are some echo and foreach statements to start. That's the code I needed to start exploring the base concepts of ProcessWire. echo $page->yourTextField; foreach($page->yourRepeaterField as $repeaterItem) { echo $repeaterItem; } You will see results pretty fast and will see how some field types differ or behave in one situation or another. Create a few demo projects, break them, try to fix them, install them again and start over. The moment you know how templating / output strategies work in ProcessWire look into something like TWIG or LATTE. To use these you should know a bit more about how ProcessWire, fields, templates, output strategies, etc. work. Start here: https://processwire.com/docs/tutorials/ Even though this video is quite old and the backend looks outdated 99% of this is still true and works in the same way:
  23. The people around might enjoy and maybe even love ProcessWire. As it is free, as in beer and in freedom. At least outside the ProModules and some other third-party modules. Yet, with that background, you probably could make bonus points in one way or another. The ProcessWire docs are probably one of the best, the API is easy to understand even for beginners, and the community is unmatched, absolutely awesome! Probably one of the best around. Another great option for you with ProcessWire could be: ProcessWire is probably the best CMS to run a data-driven website. But back to your questions, and a very warm welcome. Most clients who used and knew about WordPress just knew the name and were told it was awesome. Almost all were annoyed by those upgrades each and every day and that things broke once in a while that resulted in another invoice to fix those issues. So... no, most of my or our clients looked for something that caused less stress and minor headaches. We market our websites as helpers, that do most of the jobs and take care of some parts of the site and even remind editors to do their job. But that's another story. Those who wanted to keep WordPress didn't become clients and were directed to other agencies that knew WordPress. That easy. Some plugins, aka modules, from WordPress would be nice-to-have, yet we have absolutely everything around in one way or another. ProcessWire can do things just with its core capabilities that WordPress needs at least one, two, or even more plugins for. For example: ACF, CustomPostType, Caching. It's all there—maybe no batteries included, but you could just add those/whatever you need, especially in terms of ACF and CustomPostTypes. Caching is a bit more tricky, yet even for beginners, it is quite easy to handle (just like me, years ago, in 2016 or so without almost no knowledge about PHP or ProcessWire). I'd go this far and say ProcessWire is a great way to start a PHP-Dev journey. RockFrontend has an easy built-in page reload on file changes. It's probably my most-needed feature ever. Besides that, I use Rockfrontend or TemplateEngineFactory to enable TWIG support (others enjoy LATTE more, but ok). While it seems that almost 95% of us here use TracyDebugger, I am not using it for the following reasons: I am not a programmer or developer. I do way more frontend, concepts, and SEO so I enjoy things that make my life easier, like LazyCron, ProCache*, FormBuilder*, ProFields*, and some additional 3rd-party modules to fix and boost SEO, like SEOMaestro, or automate things, with LazyCron, Hooks in ready.php, and maybe even some small custom modules. The real kicker is probably: Custom Modules and/or Custom Page Classes My preferred CMS before ProcessWire was Textpattern which was totally different, yet minimal and easy to use. It took me about a week to feel home in ProcessWire, built my first client project the same year, and never left ProcessWire - since 2014/2015. I built almost everything from simple landing pages to full-fledged projects. See those Site of the Week entries here: https://weekly.pw/issue/221/ https://weekly.pw/issue/371/ https://weekly.pw/issue/374/
  24. I use AlpineJS all the time in ProcessWire. See the package.json here. In terms of AlpineJS it's almost a one-time-build unless you place all logic in an external file. That takes minimal more effort to make it work. This is how I use it: package.json "scripts": { "watch": "npm-run-all --parallel watch:*", "build": "npm-run-all build:*", "watch:alpinejs": "npx esbuild site/templates/src/alpinejs.js --bundle --target=es2018 --watch --outfile=site/templates/js/alpine.dist.js", "build:alpinejs": "npx esbuild site/templates/src/alpinejs.js --bundle --target=es2018 --minify --outfile=site/templates/js/alpine.dist.js", "watch:appjs": "npx esbuild site/templates/src/app.js --target=es2018 --watch --outfile=site/templates/js/app.js", "build:appjs": "npx esbuild site/templates/src/app.js --target=es2018 --minify --outfile=site/templates/js/app.js" }, src/alpinejs.js import Alpine from "alpinejs"; // import mask from "@alpinejs/mask"; // import intersect from "@alpinejs/intersect"; import persist from "@alpinejs/persist"; // import focus from "@alpinejs/focus"; // import collapse from "@alpinejs/collapse"; // import morph from "@alpinejs/morph"; // Alpine.plugin(mask); // Alpine.plugin(intersect); Alpine.plugin(persist); // Alpine.plugin(focus); // Alpine.plugin(collapse); // Alpine.plugin(morph); window.Alpine = Alpine; Alpine.start(); src/app.js document.addEventListener("alpine:init", () => { Alpine.store("myStore", { list: Alpine.$persist({ listDaysDefault: 1, revision: 0.1, startDate: "", endDate: "", items: [], }).as("localStorageMyStore"), // disable scroll on body scrollLocked: false, toggleScrollLocked() { // if either or overlay or category menu is active if (this.showOverlayMenu || this.showCategoryMenu) { // console.log("true"); this.scrollLocked = true; } else { // console.log("false"); this.scrollLocked = false; } }, // Getter, Setter, Functions // https://alpinejs.dev/directives/data#methods // funFunction() { // return value; // }, }); }); // we check for updates on local storage and reload all browser showing this website // enable when necessary // window.addEventListener("storage", () => { // location.reload(); // }); _main.php <script defer src="/site/templates/js/alpine.dist.js?=<?php echo time(); ?>"></script> <script src="/site/templates/js/app.js?=<?php echo time(); ?>"></script> Let me know where it breaks your boilerplate setup.
  25. JavaScript Tag Loading Visualized by Wes Bos See here for more/discussion:
×
×
  • Create New...