Jump to content


  • Content Count

  • Joined

  • Days Won


Everything posted by wbmnfktr

  1. Just to let you know: Server directory option includes the ready.php here on my setup.
  2. Ok, this is a very good detail. I always use ZIPs as I push them - as they are - to the new system. I will try the Server Directory tomorrow and let you (all) know if this makes a difference here on my side.
  3. Can't confirm this. Just moved 2 sites/profiles from local to another instance. Neither of them had ready.php, init.php or finished.php in the created profile ZIPs.
  4. After a quick look into some projects I took more care about files: assets (/site/templates/assets) brand brand-company-logo.ext brand-company-og-image.ext favicon.ico (just a backup - the .ico always sits in the document root) favicon.png ... fonts plex proxima icons* (icons often end in my .css files - a ProCache option, therefore names don't matter here) whatever-123123.svg the-file-912321.svg was-named-or-4572.svg helps-me-to.svg find-the-icon.svg i-need.svg vendor jquery jquery-3.x.x.js slick z (storing things I don't need anymore without deleting them - just in case) * icons are in 99% of all cases just decoration elements so I use them very often as backgrounds and not as images. Every image that's not content on its own or part of the content will not end in an <img .../> tag. In case of gallery arrows I try to use text links/span-elements and re-style them with CSS. The icon itself will be in my CSS most of the time.
  5. After my post yesterday I realized that there is actually more I do. At first I thought I don't think that much about naming but then I looked into a recent project and found several patterns that seem to be part of my workflow for a while now but I never saw that as a naming convention to be honest. It's more my laziness. I hate searching around so I group templates and fields in some cases to make things easier for me - I guess. Templates for data that will never result in a viewable URL/page get the prefix data, for example: dataPerson dataWebsite dataProject dataProduct Then there are templates that result in real pages/URLs which get the prefix content, for example: contentPage contentPost contentEvent contentGallery Then there are templates for pages that result in real pages/URLs but don't contain real content on their own which get the prefix list, for example: listBlog listMovies listRecipes listTeams There are some more templates types but I'll skip them here as they are too much based on my workflow and projects - sometimes. "Yeah... but what do you do if a data template needs to be changed and a page should become viewable?" Well... I rename it, create or rename the .php file, do the things that are necessary to get the task done and I'm ready to go. While developing a project this can happen - but not that often actually. It's more often the case later on when the website owner decides to push more content into Google's index. As it is a client request I'm totally happy with it and can invoice my work. In terms of field names I go the way @teppo already mentioned but with a little twist at the end. I name the fields depending on their purpose. headline subline summary excerpt intro bodycopy images heroImage heroVideo videoYoutube videoVimeo urlFacebook urlTwitter urlLinkedin nameFirst nameLast nameFull You can see that I try to group fields by their name structure. Instead of firstName and lastName I reverse the order and these fields stay together in my list of fields. That makes life much easier in case I need to look up something or want to find out if there is already a field I can use. But... is this really a naming convention? I don't think so.
  6. My experience with this in the past: The more I thought about naming conventions the less files I created - therefore didn't get anything done. Cleaning up afterwards was sometimes a mess but at least I had something to clean up. If you are working in a team, talk about it and think about it together. If you work alone you will find your way somewhere in the future.
  7. Additional side note: It seems my post confused a few of us. Therefore a few more details about my workflow. Clarification The above mentioned workflow does not involve ProcessWire. This workflow applies only to the part of creating HTML, CSS and JS for a project in its static version. You can call it a prototype, a template library, a loose collection of web-related documents, or however. This step is done way before I fire up ProcessWire (or give the files to another developer in case of Typo3, the CMS we don't name here or whatever). Each time I start a new client project for a website I already have in some kind a full-featured, defined and approved design - either made in Adobe PS, IS, XD, Sketch, Figma or any tool you can imagine - most of the time it's not my part to be honest. I can then work out each and every detail, plan out the things that were needed, look for repetitive elements and their modifications and states. The result of that (my work) needs to get an approval by the designer and the client - afterwards I create a new ProcessWire instance and migrate everything in template files and smaller bits I will need later on. With this overall approach I have had enough time to know how to structure the data and content in ProcessWire which makes things in it super easy and super fast most of the time. Hope this helps.
  8. I wouldn't call it a manifesto but anyway... let's talk about my workflow. TL;DR I build 90% from scratch. Every time. Each and every project. I don't use frameworks of any flavour.* * except from some JS stuff - see below Long version My boilerplate for new projects: SCSS Skeleton (my personal collection of SCSS Magic) JS Skeleton (my personal collection of JS Magic) HTML/Kit files depending on templates and elements the project needs (inspired by http://bradfrost.com/blog/post/atomic-web-design/) just an empty folder would work totally fine as well Tools I use and need: git Prepros/CodeKit (or ProCache 😎) Tools that may be added later (if absolutely necessary): Lazysizes SVGinline jQuery for Slider scripts (slick, OwlCarousel) MixItUp Tools I never use (because I'm too old for that - I guess) Grunt, Gulp, Bower, Webpack, Parcel, ... you get the idea Benefits Projects are portable Projects run everywhere Every part of project can be changed without affecting other things (most of the time) No need for a special setup (at least for the compiled files) Small(est) file sizes and therefore fast websites (in most cases) Downsides Working with others means I have to trust them and their capability to write good CSS/SCSS You have to think at least twice for each step, every time It takes much more time to build everything from scratch It's much more expensive at first Clients often don't understand the benefits and sometimes WANT a Bootstrap website 😱 FAQ What if you work with others? As mentioned before I have to trust others that they are capable of writing good CSS/SCSS and therefore I tend to work only with very good people I really trust. Is it worth it? Yes! Why? When stuff breaks or needs to be changed, I know where to look, what to change and can do my stuff without the need to take care of any version upgrades, incompatibilities in or with newer version, I don't need a special setup or whatever. AND... if I want to I can still add whatever is needed. Try it the other way around. That's much harder. Are there exceptions? Of course. Backend stuff, admin interfaces and things like - ProcessWire admin is the perfect example. I wouldn't build something like that from scratch. I guess that's my manifesto.
  9. That's Brutalism, right? Well... the design is a challenge but the estimated traffic and SEO coverage is quite nice or almost impressive to be honest.
  10. A few months back I gave Linux another chance. I was looking for something that could improve my workflow in some kind or the other and yes... I'm still on Linux. Tried a lot of distros and windows managers since then - right now I'm super happy with Manjaro and the i3 (i3-gaps) window manager. Works pretty pretty well so far.
  11. Affinity used it in a clever way. I like(d) their software.
  12. d0h... I'll be in Hamburg that day but please have a beer "auf meinen Deckel"! @marcus is there a https://www.buymeacoffee.com/ or beer button we can join in for the meetup?
  13. First off all... I stumbled across this by accident and didn't follow the whole conversation... more or less... but as far as I understand the Adminbar (module) is only available to those who are logged in. So why bother with any libraries, browser extensions and such that (in most cases) only apply to those who aren't logged in? There are many modules that behave differently when compared to logged in users and guests. Sorry if I miss an important point here!
  14. Jamie... put it on the screen!
  15. I really hate dealing with comments - due to GDPR and such - but maybe I should give it a try. (Kind of) Glad you pushed me into this direction with your question.
  16. A Ferrari 360 is way more elegant than a VW Golf V but still... you can't move more than 4 boxes (4x 12 bottles) of beer with it. So... if you feel fancy, you can pay for it - as in hosting prices. Actually Python is supported pretty good in most of the hosting environments I know. And compared to cars it's kind of a Porsche Cayenne and you can move 10 boxes of beer with it and still can go 230km/h if you wanted to.
  17. And that shows the highest rated comments? N-e-v-e-r used them actually. But still interesting to know for an upcoming idea.
  18. Those are independet fields - at least by default, even though there are some connections between textareas and image fields. Since I started using ProcessWire, back in 2014/2015, I never had this kind of need/request. I guess the project you are working on is kind of automated or at least kind auto-optimized - a larger blog or something. Am I right with this?
  19. Never tried it actually... @louisstephens but still consider using it. The Surface/pencil combo is - especially after some updates in the past - pretty perfect. The "open txt-file for notes"-workflow is awesome since ever. I do this every day and move my notes once in a while to whatever tool I use in that moment. In VS code it's perfect as you don't have to save to keep changes. In VIM - which I try right now - I enabled autosave for .md files and that works pretty good as well.
  20. @louisstephens Notion is the new and better Evernote, right? Just realized how awesome my Surface with a pencil works as a "note taking app".
  21. I stumbled across Zettlr a few days ago. https://itsfoss.com/zettlr-markdown-editor/ https://www.zettlr.com/ Update: At the end I started playing around with Emacs orgmode. But I guess you will need a solution right away.
  22. Well... as @dragan has no access to any of your template files and doesn't know anything about the whole setup of your site it's actually everything he or anyone else can tell right now. Who maintained the site before? A co-worker or an agency? Someone built that site and that someone can or at least should be able to provide you more details.
  23. Had two calls last week from people who wanted to know if I can help re-animate their dead sites. They had issues with plugins during an update in their WP sites which locked them in a maintenance mode or something. Still weird but at least it was kind of easy to fix. So this seems to be a real issue in some circumstances. But back to the topic... As @szabesz and @elabx already mentioned... the workflow can quite easily be implemented. Maybe you just setup a small site and test the user and publishing workflow. In terms of upgrade issues and performance ProcessWire is way ahead and the better choice - in everything else as well.
  24. You could also use either of these methods/modules: Module Menu Builder - create custom menus, including external links. You decide what will be in it. Module Jumplinks - just create the pages you want and create redirects within Jumplinks (/old/path -> https://wherever.test/). It's easier and it handles more than redirects - like 404s and counts every click on your redirects.
  25. I kind of like it as we set things up there. A few years ago I didn't like the global use of page for absolute everything and the menu label setup... but nowadays it feels weird to have a global settings page/area as in WordPress or things like posts and pages. Maybe you can add your SnipWire (page) into the navigation bar next to setup somehow. And as far as I know is your module quite huge and almost a standalone version of ProcessWire... it would make perfectly sense to add it to the top bar. Disclaimer: yes... I'm sometimes weird, confused and do things differently.
  • Create New...