wbmnfktr

This little helper does an amazing job!

In ProcessWire itself I've never used custom fonts. For projects I do it the exact same way as @horst does. As I use .less for CSS I create a _fonts.less import with everything I need. One exception is Typekit. That always gets included with JS.

Maybe... <?php if(count($pages->find("template=template-2, pageField=$page"))) { // do this } else { // or that }; ?>

A super nice and interesting read and website. Just out of curiosity: do you (@jmartsch and all others) ask your clients for permission to create write-ups, case studies or any kind of their-website-related-development things? It might be my 15-years-of-B2B-NDA-history that's amazed about things like that.

First thought: Maybe you should talk with your client and ask him to re-think/re-create his product images. I don't know what kind of products will be shown but a consitent look & feel should be in his interest too. Second thought: You could create an image-canvas and place the product image itself in the background. All products would have the exact same image-area no matter what size the products images have.

I use (and love) background images a lot on all kinds of whatever... even in :pseudo elements like :empty, :before/:after. Combined with things like aspect-ratio you can do some really nice things there. Yet another thing to mention: Multiple background images More about aspect ratio boxes: https://css-tricks.com/aspect-ratio-boxes/

Sorry, Boss! It's not what you think. I'm on the site for the source code only, not for the girls. Honestly!

Did your router get and auto-update or something like that? Maybe one of the following settings is mis-configured. Safe-surf (child protection, adult filter) White-/Blacklist misconfiguration Are all devices in your network affected?

Who will use these data entries? What will happen with all these data entries? How many data entries will there be each minute/hour/day/week? How long will they be stored? Will they be archived/deleted? Will someone create charts from it? Will they be exported to another programm/system? Will there be JSON/XML/RSS exports/strems/feeds or even an API? Will ProcessWire provide those access details for each dongle/user/door? There are so many best ways to go depending these paramters and variables.

I'm using this on 3 sites and by now there weren't any glitches, errors or strange things happening on the frontend. All sites are PW 3.x (mostly the latest Master or Dev releases).

Recently discovered: Layout Land by Jen Simmons on YouTube. https://www.youtube.com/channel/UC7TizprGknbDalbHplROtag

Just two words: Awesome & Insane A really nice and different design combined with such a nice animation-builder-toolkit. Great Work. Love it.

I personally would always create pages instead of repeater items. Pages can become almost everything later on as repeaters are more or less part of a page and a little more difficult to handle. A while back I created something to manage course bookings. Every booking ended as a single page in the backend. From there on the client was able to generate confirmation-, contract- and invoice-PDFs. Doing that with repeaters in a page might work in some kind but will end in way more work/hassle. Creating log entries is always a good idea as well. Kind of fallback.

I made it work with PHP 5.x just by changing one line. SubscribeToMailchimp.module - Line 23 - before: public function subscribe(string $email, array $data = [], string $list = "") { SubscribeToMailchimp.module - Line 23 - after: public function subscribe( $email, $data = [], $list = "") { This works without any problems so far.

My config.php file says:

Ok, that is GDPR-related but in another field. At least it's nothing I came across in the last couple of years. So I don't care much about this part. But to be honest... regulation of this exact type of irresponsible behaviour and reckless data-sharing is absolutely necessary. GDPR isn't that new and data privacy is a main topic for almost a decade here in Germany. Let's face the truth... companies like the one in your example are the reason for things like GDPR.

I'm not talking about all kinds of third party software. Just a few. We may have to stop ourselves and our clients from using third party things like: Google Analytics Google Adsense Google Fonts Typekit and similar services Ad networks Facebook Pixel Hotjar Hubspot Social Widgets Free CDNs ... and so on At least as we used it in the past. There are GDPR compliant ways of using Analytics, Retargeting, Monetizing and whatever. But it's work now.

Making sites GDPR compliant... this is a thing I'm careful with. Knowing what to for each client because of an audit or a lawyer who looked into it will work. No doubt. You do what a professional and reliable source said to make a site compliant. But I personally have not and will not tell a client what to do or what not to do. I know some things (probably more than any client and some "experts" out there) but stating and offering GDPR compliant sites can get me into trouble. I'm not a lawyer I can't offer legal advise at all. The without warranty-thing that eRecht24 does is fine. They offer generators and therefore legal texts based on your input. Asking a lawyer (or better lawyers) to check and create everything for you will cost you a lot of money but then you will get a warranty too. Providing design works, logic and functionality will almost stay the same. Being GDPR compliant from start can and will be tricky. At some point someone has to ask a lawyer. At some point you have to stop implementing third parties. At some point other GDPR-related things kick in (like the Datenschutzbeauftragter) and the developer isn't the right person for that detail anymore. As developers we can't handle every aspect of the GDPR and things that will come. But yes... getting our hands dirty will come and it's necessary. Necessary for good and trusted developers.

Building a website is not the problem. Running a business with it can become the problem. Collecting e-mail addresses, tracking visitors and monitoring visitor-behaviour, combining it with 3rd parties like Facebook and ad networks will be a much bigger thing now. Cookie permissions here, double-opt-in there, and so on... it will be much more challenging than before. Don't know anything special about sources in Spain, UK, US but here in Germany there are some lawyers offering (free and paid) help for all kinds of businesses. Just to name two I prefer: https://www.e-recht24.de/ and https://drschwenke.de/ And as always with legal stuff: lawyers are my one and only trusted source. Not other companies (like the one above) that offer checklists, guides and tutorials.

@ryan provides exactly this kind of TOC/jumplinks as an example for the Hanna Code module. Take a look at the end of the page: http://modules.processwire.com/modules/process-hanna-code/ So you could use Hanna Code inside your pages or create something new from that example. Here is the code: <?php // $for defines the headlines you want to take care of. // i.e.: h2, h3, h4 $for = str_replace(',', ' ', $for); $for = explode(' ', $for); foreach($for as $k => $v) $for[$k] = trim($v); $for = implode('|', $for); $anchors = array(); $value = $hanna->value; if(preg_match_all('{<(' . $for . ')[^>]*>(.+?)</\1>}i', $value, $matches)) { foreach($matches[1] as $key => $tag) { $text = $matches[2][$key]; $anchor = $sanitizer->pageName($text, true); $anchors[$anchor] = $text; $full = $matches[0][$key]; $value = str_replace($full, "<a name='$anchor' href='#'></a>$full", $value); } $hanna->value = $value; } if(count($anchors)) { echo "<ul class='jumplinks'>"; foreach($anchors as $anchor => $text) { echo "<li><a href='$page->url#$anchor'>$text</a></li>"; } echo "</ul>"; } else { echo ''; } For better understanding you might want to install Hanna Code and or want to customize this for your needs.

First idea: Mailchimp RSS campaign More details: https://mailchimp.com/features/rss-to-email/

Would you mind to share your White Paper with us? Non-public or with a NDA (kind of)? It sounds interesting as a 10-pager should/might be very promising. I'd like to share my insights and arguments as well - if someone is interested.

Tweak the backend with your client's brand colors, their logo and a nice favicon. BOOM... they will feel like home.

That makes life a bit easier as it doesn't necessarily need critical business logic as validation, calculation, payments or whatever. Data structure My personal preference would be a data structure that consists of branches for countries, regions, years and other repetitive data that will later be referenced in each wine. And a branch with all wines. Combined with modules like PageFieldPairs or Connect Page Fields you could easily sync those datasets and references from one page to another. But every other structure might work here as well. It's a personal preference thing here. Update: You should use a more unique ID for each wine than the PW page ID. The SKU or EAN or whatever the data source can deliver. This can make updates easier in the future. Data sync This depends. How often new wines will arrive? How often a wine needs to be removed? How often details will change? What will change? Do details need attention (for example: price formatting)? A manual CSV update might work well, but JSON makes things easier sometimes. Maybe I can find something about structure and sync in my files and projects that I can post here.

Before going deeper into possible ways and solutions on data-handling... What else is needed or planned for this? Will the final result be an online shop (with all kinds of shop functionality) or just a catalogue for potential buyers?