Jump to content

pwired

Members
  • Posts

    2,318
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by pwired

  1. Quote

    And I have had such a great idea yesterday, I almost can't believe it myself ? It solves all those weird scaling issues and makes it possible to scale any css rule that has a numeric value, like font-size, border, padding/margin, border-radius etc...

    Hi,

    Will the scaling also work for images and html5 videos ? Hope to see more of this $rockfrontend growMin .... growMax ....

  2. Quote

    I get the impression that we're missing a "proper" tutorial here. In my opinion, what we have here are bits and bytes that are out of date. It would be nice to have a "complete" and updated tutorial on how to build a "real" website. What are your opinions?

    There are dozens of quality tutorials and Processwire strategies explained under the Processwire Docs and then there are dozens of more very good tutorials on the internet. So either you are disconnected from Processwire reality or don't know how to use Google. But usually the real issue is that Processwire has unlimited power and freedom under the hood, confusing old habits of making websites. Dive in the Processwire api and make websites with it and many of the questions will melt away. We are here to help you go along.

  3. I don't really bother because I use the pocketgrid css, which works with free to choose unlimited columns and free to choose unlimited breakpoints and blocks. I resize a website from wide screen to mobile screen and simply set breakpoints only where they are needed to resize a font, picture, margin, padding, etc, etc to make it look good. Contrary to something like Bootstrap would be very difficult because Bootstrap and the likes work with a limited set predefined breakpoints.

    • Like 1
  4. For a long time I dived directly in templates and code to build a website.
    I changed that old workflow and use prototyping and wireframing a website
    first in Lunacy and Pencil. Only after that I port it to processwire code.

    • Like 3
  5. In general:
    Apache servers are case sensitive. A request for /directory/file will be treated as a request for a different file
    than one for /Directory/File.

    Search engine’s are case sensitive. They’re going to view /directory/file and /Directory/File as the locations
    of two different documents

    In processwire:
    https://processwire.com/talk/topic/23223-allow-upper-case-in-url/
    https://processwire.com/blog/posts/page-name-charset-utf8/

     

    • Like 4
  6. It is no secret that Wordpress attracs a lot of no-coders and low-coders because of it's available template market. The no-coder buys a template on envato, themeforest, templatemonster, etc. and sells it as a website to the client. Most of the clients don't even know they bought an envato template website because they have no time and no website experience. By the time the client needs to have something changed, the wordpress template limitations won't allow for it and the no-coder is long gone selling a template somewhere else. Sooner a later the client is forced to call for a real coder for the needed level of support. Pagebuilders will attract even more no-coders and low coders. Having followed the Pagebuilder scene in Wordpress with Beaver, Bakery, Brizy, VisualComposer, Elementor, Genesis, Gutenberg, Themify, Divi, Oxygen, GeneratePress .... the list goes on and on. There is almost every month a new Wordpress Pagebuilder on the block. Why spend time in learning the Pagebuilder of the day if you could spend that same time in learning html, js, css and php and never need a Pagebuilder in the first place and give the Client a website that he really deserves: without Template limitations, unused theme functions and without all the Pagebuilder bloated code. Coming to my point: I hope that what is happening in the Wordpress Pagebuilder scene will never happen with future Processwire Pagebuilders.

    • Like 6
  7. examples
    <a href="<?php echo $pages->get('/products/')->url; ?>">Products</a>
    <a href="<?php echo $pages->get('/about/')->url; ?>">About</a>
    <a href="<?php echo $pages->get('/contact/')->url; ?>">Contact</a>

    api
    https://processwire.com/api/ref/pages/get/
    https://processwire.com/api/ref/functions/pages/

    info
    https://processwire.com/talk/topic/4909-site-url/

    module
    https://processwire.com/modules/process-menu-builder/

     

     

    • Like 2
  8. Yes .... 1) It is very hard to compare PW with other cms systems and 2) It takes a lot of PW use to begin to see the appliance potential of it ..... and 3) because most reviewers simply do not spend time with 1) and 2) their reviews are based on habitual thinking they have grown with other cms systems ....

    • Like 1
  9. Yes I understand what you are saying there but setting images to be a single-file field is only a pre-option that you can choose to set before starting to use images. Why not just leave images as an array and use the api and/or php to do whatever you need from it to get whatever you want from it.

  10. Quote

    Is it workaroundable?

    Why would that need to be "workaroundable" ? Pages in Processwire that are associated with Pages that show up on the Front as website Pages work with a Template that has a Template File. Pages in Processwire that are associated with the Backend as Functional Pages (data - sitewide media - configurations - etc.) can work with Templates without a Template File. That all makes sense as it should be so I don't understand your question.

  11. Quote

    ..... and seeing how things are done in ProcessWire makes me think in different ways when I am using other tools .....

    Although I only asked for some coding examples your reply about Processwire in general is very welcome.
    Ryan is a very clever coder and this forum is full of very clever coders with a lot of experience.
    If I was a very clever coder too then I would never post my comments from which I know some find them irritating.
    As as solution I am building my own personal database where I can store, evaluate, sort out and apply the weekly
    new added coding options. With it I already could apply new coding options to expand on the delayed output strategy
    that I am using all the time.

  12. Quote

      I've found a nice solution using PageTableNext.
    - I can define different section(block/paragraph...) types with appropriate fields, e.g. hero, text with image on right, ... I can create templates for all these.
    - I can add/delete/reorder/edit etc. these to a page and see previews in-editor.

    Hi at artfulrobot,

    That sounds very interesting, Besides from Teppo, do you have some code examples ?

  13. Quote

    for me it helps me with both. How about you?

    You forgot to mention in what way it helps you with both ... any examples ?


    After so many weekly updates already with new xyz coding options added ... To be honest, I simply cannot keep track of them anymore ...
    But maybe you can ...

    After a while ... who is still going to remember all of them ?
    How many are really going to use them ?
    Being productive has my focus ... not getting fragmented in weekly new added xyz coding options

     

     

  14. Hello at MaccGreen, consider your self so lucky that you have found the Processwire cms/cmf

    Please introduce your self a bit and tell us something about your web road ...

×
×
  • Create New...