diogo

To make a site with ProcessWire you will have to do work a bit more than that. The documentation is there, and it's very complete, but it won't teach you sokething that specific. You will have to join the pieces of the puzzle yourself. It's totally worth it though, once you learned by yourself how to list your articles with the thumbnails, you wil know how to do anything you want. And I mean anything! No code examples as I'm on mobile, sorry.

Actually, in this case it was us who decided the design, and we assume it completely as our style, even if a bit more corporate than what we usually do. The client was great and liked immediately what we showed them.

Thanks Charles! I forgot to refer an important detail. All the tables from the products are using the Table ProField. This field makes it incredibly easy for the editors to fill the tables and they are really happy with how it works in the backend. Here is an example for editing this product http://fiberprofil.com/produtos/gradil/gradil-moldado/ra-iso25m3838/ Those dropdowns are page selectors. the editor can add new properties by themselves as pages in the tree:

Hey guys, another website we want to share with you! http://fiberprofil.com/ This is a website that we released a few months ago for a Spanish company specialised in pultruded fiber products. There is still some content missing in the English version, so you may want to see it in the other languages. The structure of the website is quite complex, and to make it easier and less repetitive for the editors, we implemented a system of fields inheritance, so the images and information can be inherited from the parents when missing. This is useful when products share common properties with it's siblings. For every product there is the possibility to download a dynamically generated PDF. We did it with the pages2-pdf module. The logo and graphic design are also from us. Edit: see my next post for a nice detail

Not yet on real projects, but I won't wait much longer. By the way, this is a great way of learning how to use flexbox http://flexboxfroggy.com/

You could start with the beginner's tutorials in the docs, they are very clear and helpful: take Joss's "But what if I don't know how to code?" series, or Ryan's "Hello worlds" tutorial for starting. Anyway, all that you need is here https://processwire.com/docs/

I didn't test the theme thoroughly but I spotted some bugs, so, here's a quick feedback: The color background color doesn't change, and the info in the footer needs more space: Also, there is a flick when I go to another page. For a fraction of time the background is white and the elements are positioned differently.

This looks great!

Good suggestions, by using Pia, you won't have to touch the slick code. If you would decide to convert some images to vertical, you would have some big headaches to change the css that you already defined for slick. If you do decide to go with vertical images, I would advise you to use the images as background of an empty element instead to make them responsive and avoid strange distortions. You can keep the proportions of an empty element with this very interesting but simple trick http://stackoverflow.com/questions/1495407/maintain-the-aspect-ratio-of-a-div-with-css, and then set the images as background with cover and contain sizes.

Slick slider doesn't enforce any markup on you (that's why it's my favorite slider), so, we really need to know more about your markup to be able to help. Is there an page where we can have a look?

Check also if the limitation is not on the FB API side. I remember that I had to do the same with youtube, but YT allowed me to call a limited amount of videos on the same request.

Your German is very clear to me, I think your screencasts will be useful for some language learning

Oh, of course. When using this kind of foreach structure you have to reopen PHP to echo your object properties. You can open it with <?php or echo them with the shorter version <?= <?php foreach ( $pages->find('template=single, limit=5') as $single ):?> <div class='post'> <div class='content'> <a href='<?=$single->url?>'><h3><?=$single->title?></h3> </a> </div> </div> <? endforeach; ?> You can also use the most common PHP structure, where you don't go in and out of php. Your choice. Anyway, I think you would benefit a lot from studying the basics of PHP while using ProcessWire.It's not hard at all and will making everything more clear for you.

First of all, welcome to the forums! Hm, you have more than one problem in this line <?php foreach $pages->('template= home-single, limit=5'); ?> Try this instead: <?php foreach ( $pages->find('template=home-single, limit=5') as $single ); ?>

And css animations. I simplified their code to demonstrate: div { animation-name: enter_animation; animation-duration: 6s; animation-timing-function: ease; -webkit-animation-fill-mode: forwards; opacity: 0; } #first { animation-delay: 0; } #second { animation-delay: 4s; } #third { animation-delay: 8s; } @keyframes enter_animation { 0% { opacity: 0; } 100% { opacity: 1; } } http://codepen.io/diogo-ed/pen/pywjxN

Welcome to the forum Atif, thanks for the guideline and thanks again for the nice interview with Ryan.

Because the markup is so simple, and the sections have all the same structure, I'm actually not using the render() function, so the children template simply doesn't have a template file. But if you are using the render() there are still some possibilities: — The most immediate is to set those pages to hidden; — Another option is to check if the page is being called by the render() function, you can do this by checking for the presence of the $options array if( isset( $options ) { // spit the content } else { // redirect to home or throw a 404 }

Hi all! Here is a very small website that we made for this event promoted by two landscape architects. This is a one day event where private gardens in Freiburg are open to the public. There are also some planned workshops and other activities. http://freiburger-gaerten.de/ This is one of the simplest websites we did. A one pager with smooth scrolling based on anchor links. The PW part was very easy, the content of each section is in a children of home, so on the home template we simply have to iterate all the children and render them.

Christophe trust me, it's my language, I know what I'm doing

Well spotted Willy! Cintia, before translating from portuguese to english, make sure you don't have mistakes on the portuguese words because it messes up the translation even more than usually. For instance, you missed the R in "Brasileia" and the G on "seuinte", and there are more. edit: Duh, you won't understand this probably , here you go: Cintia, antes de traduzires para inglês verifica que não tens erros no português. Isso vai tornar a tradução ainda mais caótica do que já fica normalmente. Por exemplo, falta o R em "Brasileia" e o G em "seuinte", e há mais assim.

Not knowing exactly what you want to do it's difficult to help, but it seems to me that it would be better to use "limit" on the selector and do whatever you have to do in chunks. Honestly I don't see how an array of 10000 IDs could be useful.

The idea of the process that I described is exactly to avoid locking the live site. That's why doing all the nondestructive changes on the live site and avoiding any DB changes on the local copy.

It's an old problem, and no, there isn't a simple solution. I think the most commonly adopted solution is still this one, back from 2011 http://ben.kulbertis.org/2011/10/synchronizing-a-mysql-database-with-git-and-git-hooks/

The system that's proven more effective for me is: 1 — do all the non destructive database changes on the live site (adding fields and adding them to templates, creating new templates and so on) 2 — import the database to the development server and do the templates changes 3 — pull the new files to the live site without touching the database 4 — do some cleaning on the live database if needed (remove fields, templates and so on) Another tip, although this one doesn't really answer your question, just because I think it can be useful One system that I already used effectively was to create another install of PW (a copy of the other) in the live server (on a subdirectory or subdomain) that connects to the same database, and develop all the changes on the template files right there, using real and up-to-date content. Then I simply replace the template folder by the new one.

A very honest write up by our very own André (@onjegolders) http://milktop.co.uk/articles/picking-the-right-cms-for-the-job I already told him about the built-in frontend editing on 3.0 and the Pro Drafts live editing