diogo

I guess this is why I have an ongoing philosophical problem with frameworks... the basic aspects of responsive design are really not that difficult to understand, but by using frameworks, people are just bypassing that essencial understanding and accepting some limitations that are imposed to them. In essence, making a website responsive is not much more difficult than rearranging a bunch of photos in different physical formats (with the advantage that you can also change their size) and registering the movements that are needed from one form to the other. Only thing to keep in mind is: with CSS you can change the horizontal order of elements with floatings, but not the vertical order -> that's actually the only limitation. Ok, I'm drifting away from the thread theme, I'll stop here and focus on that Oh, @muzzer your sites don't seem to be working right now, getting a 502 on all of them.

I'm in the middle of something, and was hoping that someone would complete my suggestion. Thanks @LostKobrakai

This would be easier if you would use classic pages and the pageFieldType instead of repeaters.

I don't like purifier missions...

The module works by creating a page with only json content that you can get via URL either by JS or PHP (or whatever you want). It allows you complete control over the data that gets passed to json, so you don't have to have any problems with sensitive data being exposed. If you get the json from another site with PHP in your templates, there's no way Google will know where it came from.

I'm on mobile and can't help more than this, but did you notice that your first js line is commented out?

As horst said, the service-pages module would be a perfect fit for this. Although I don't understand why you have to keep the sites in separate servers from a SEO perspective... couldn't you just have different domains?

Moved this thread to Dev Talk, since it's not PW related.

You're in the right place then! Now, go study

We all have days like this

Image fields work fine, just not very practical to display on the table if you have multiple images. In that case it's better just remove them from the list.

I really liked Uniform when I had to use Windows, but I guess not fair to expect a smaller project to have a great support and community (PW is an exception). I know you're not asking for alternatives, but AMMPS seems to have a great development and responsive support. Edit: AND it's cross platform.

Yes, I saw the video and was also impressed Just want to make sure that a youtube nonstop current of videos doesn't start Or at least that it has it's own place, like the programming (and not only) music thread.

@pwired, I know this is the Pub forum... but the PW forums is a cozy place where I really enjoy being away from the wild internet.

For now, maybe the best way would be to change the class and files names and install as a new module.

No. I can only answer to that one

You don't need to unless you want to apply to win a Chromebook, and unfortunately they might convince a lot of people to do blind voting. The eager to get more and more people to vote might lead to less accurate result in the end. I also didn't like the "keyboard friendly" form. And I think and I think that, joining to the Chromebook problem that I referred, the result will be: 1. A. CMS with great chances B. CMS with no chance C. CMS with little chances 2. A. CMS with great chances B. CMS with no chance C. CMS with little chances 3. A. CMS with great chances B. CMS with no chance C. CMS with little chances and so on... I don't remember how PW was positioned, so I don't know what are the chances we have

You can now try the font directly from Open Font Library just by adding this to your document: <link rel="stylesheet" media="screen" href="http://openfontlibrary.org/face/grupo3" rel="stylesheet" type="text/css"/> p { font-family: 'GRUPO3'; font-weight: normal; font-style: normal; }

@Mike, sound ok, thanks! I reduced the amount of pictures in the slideshow on the homepage to make those times a bit better

Thanks Mike! I had forgotten that SiNNuT referred the grey background, and didn't take care of it. I added the !important and according to BrowserStack the problem seems to be solved! We added the strike-out to the active link after our first very professional usability test (with my sister ). We chose the strike-out after trying changing the color to green, but that didn't go well since in our system the color represents the links, and this link is deactivated. The strike-out besides being a very clear visual differentiation, also tells you that you can't press that link. --- I did some —well, a lot— optimisations on the website concerning speed. Would be great if you guys could tell me how the site feels like now, especially those on the other side of the ocean

I moved this thread from "case studies" to "showcase"

Hi David! Any thoughts on changing the compression library yet? I'm getting this suggestion from google page speed insights:

Yes. If you added the field to the homepage, spitting the first 3 pages on the home is as easy as: foreach ($page->pageField->find('limit=3') as $pt) { echo $pt->title; echo $pt->featured-image; echo $pt->featured-summary; } If you want to do the same in any other page use instead: $pages->get(1)->pageField->find('limit=3')

No, this suggestion is just the one that I consider really simple, but it's less flexible for sure. If you want the client to be able to reorder them, use my second suggestion instead. Oh, you will This is one of the most important fields in PW. ProFields are great, but they are for sure no replacement to the page field. And since you haven't seen this kind of field before I strongly suggest that you read this tutorial by Kongondo https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/

my favourite 2 ways are by no specific order: 1. Add a "featured" checkbox to each page and show the last 3: $pages->find('featured=1, sort=-date, limit=3'); 2. Add a page field in the homepage where your client can add pages, and show the top 3 from that field.