Leaderboard

My interest in using Uikit for this particular site is largely for the collaborative aspect. Having a common, already-known, well documented and tested framework for the front-end just seems better for collaboration here. I know a lot of people here are already familiar with it as well. There's also the aspect of being able to develop the site without necessarily knowing the final look of it. Uikit is designed for this kind of prototyping and gives us a result that can be tailored using already known/documented means (collaboration again). That there's a lot of crossover between Uikit's components and what we will need for this site is also helpful, and will no doubt save time. The current site was also a collaborative one, but it didn't use a framework. Instead it used various strategies that may be quite good and efficient, but I've never understood as well as I would have liked. So when it comes to making updates on the code side, I feel like I'm working around things rather than with them. Since I've got to ultimately maintain the site for the long term, I like having the familiarity and consistency of an established and documented framework behind it. In the context of the ProcessWire site, these aspects are more important to me than size of the eventual css files. If I was developing a different site the considerations might be different—I might still use Uikit, or I might go a different route, or go sans framework, all depending on the context and needs of the site. So I'm not suggesting that everyone should be using Uikit, just suggesting it seems like a good fit for this particular project, as it has been for some others.

First of all I want to say that learning PHP is crucial to get going with ProcessWire. You should understand the basic syntax and concepts and how to iterate over items. Please also read http://processwire.com/docs/tutorials/but-what-if-i-dont-know-how-to-code/ However, you should create a template file "authordetails.php" in site/templates/ directory, then in ProcessWire admin also create a template with the same name (but without the .php suffix). Then assign this template to each author and editor. In the authordetails.php file enter the following code to get all publications for this author/editor: $publications = $pages->find("template=publication, authors|editors={$page->id}"); Please note the double-quotes, that are required for {$page->id} to work!!! If you are using a more recent version (3.0.107) of ProcessWire you could instead use $publications = $page->references(); please read http://processwire.com/blog/posts/processwire-3.0.107-core-updates/#page-gt-references about this. Then iterate over the publications foreach ($publications as $publication){ echo $publication->title; } All this is completely untested and comes directly from my brain, so I hope everything works.

Yeah, I usually just copy the code over the CSS just for that utility then customise it to how I want it to look. It also means I only get the CSS for the utilities I'm using. Very few utilities actually require CSS. Things like masonry grid, grid filtering and parallax don't require UIKits CSS. You can get to the CSS of just a component on GitHub: https://github.com/uikit/uikit/blob/develop/src/less/components/slider.less

This post contains an introduction to our plans for rebuilding the ProcessWire.com website. In part one, we take a look at the initial strategy, framework, and concept for the new site, primarily from the development side: https://processwire.com/blog/posts/rebuilding-the-processwire.com-website--part-1-/

Please take a look at the thread and also https://publicwww.com/websites/"X-Powered-By%3A+ProcessWire"/ but it tells only a part of the story, as it can not list all sites, because some sites turn off the x-powered-by header.

Well, I use personally use UIkit 3 + TailwindCSS. Tailwind you are going to hear a whole lot more about in the upcoming months. I know you are talking about file size and this is exactly why UIkit + Tailwind is great! I don't really use UIkit's CSS at all. I just use the JavaScript because the amount of utilities they have manage to pack into 130kb (less than most images) is amazing. I'm talking Parallax, Sliders, Lazy Loading Images, Srcset utilities, placeholder generators, scrollspy, sticky. Most of which can be and usually is utilised in any project. I challenge you to get all of that under 130kb. Also it doesn't have any dependencies. Tailwind you can get down to about 3KB per website using Purge and Gulp/Webpack. It truly is amazing and Utility first CSS is such a refreshing way to work with CSS. I know all the arguments, and I'm a minimalist. I don't like all the classes too. But Tailwind's benifits out weigh the cost. 1. You don't have to struggle with inherited styles, or coming up with class names to define each section, some of which may look the same but be very different in content. 2. Consistency, it puts pressure on you to keep things consistent. So you hardly stray to loads of different type sizes and colours. 3. With Purge, you can have an entire website styles in ~3kb. I believe Ryan chose UIkit 3 because he has learnt the classes and is confident with the framework, and is impressed with the JavaScript utilities. And because you can build website much quicker using it. I see it as a hybrid between utility and a standard framework. It offers many utility classes. You could also Purge UIkit's CSS and get it around 160KB. I don't believe that this isn't a good fit for ProcessWire as you have previously mentioned. Many who use ProcessWire love UIkit. It follows the same philosophy: A powerful framework, that is easy to understand and learn to get things done quicker. Just like ProcessWire gives developers confidence in that they can do challenging bits of functionality easily with the power of ProcessWire's amazing API (like seriously, I built a real estate system using ProcessWire, something I wouldn't have dreamed of doing on any other platform). Well UIkit also gives that confidence to the front-end. But if I was to choose for myself, I much prefer pairing Tailwind for the CSS and UIkit for the JavaScript. That ~140KB (Tailwind + UIkit) covers me for most websites I build.

Hi @mke Thanks for the clarification and example. That fits into the planned separate pro frontend module. As stated, those who want to build custom frontend will have the full API at their disposal. Something like this (pseudo code, although some API is ready) // assuming user is logged in, they are redirected to My Account area $out = "<span>$user->name</span>"; // your Orders Table [orders API in the works] $orders = $pages->find("template=orders,order.customer_id=$user->id,limit=10"); foreach($orders as $o) { $order = $o->order; /* Date: $order->date; Status: $order->status; etc... */ } // Addresses [customer API 95% done] $customer = $user->customer; /* First Name: $customer->firstName; Last Name: $customer->lastName; Email: $user->email; Address: $customer->address; City: $customer->city; Postal/Zip Code: $customer->code; Region: $customer->region; Country: $customer->country; Phone: $customer->phone; // etc...including if customer is tax exemp and whethey they accept marketing. // Any custom properties added are also available, e.g. $customer->company, etc. */

@pwired I don't wanted to start a discussion about frameworks here. I just wanted to point out that UIkit is a good choice for a framework to rebuild the new ProcessWire website and comparing it to a grid system are two different things. The UIkit framework is (as most frameworks are) modular. So if you want to use only the grid system, you can include only the grid system in your stylesheets and it should have around the same size. I don't know how much exactly because I have never just compiled the grid system and I don't count bytes, because in my opinion the size of your stylesheets are the least thing to worry about. No, I think most of the people don't use the whole 100% of a framework. Personally I use probably around 40% and include the whole framework anyway, because I like to have a good set of components available. It lets me focus more on the content and design while developing a website and I don't have to reinvent everything (grid, utility classes, slideshow etc.) from scratch. But as mentioned, if you only want to use a part of a framework, you can simply don't include the rest. ? That is the same approach as using a framework. Except when using different libs from different developers with different support and compatibility, you use components from one developer that are always compatible with each other. Before using framework I also used one lib for a slideshow, one for filterable grid, one for lazy loading images etc. With UIkit I only need one framework or if some lib does something better, I use this lib instead. That is true under the assumption when leaving the framework untouched and using it plain. The part of a good designer/web developer is to build styles on top of a framework and make it look different. In my opinion a framework should not be used plain and is just a foundation for an individual design. Of course everything I say is my opinion only and everyone is free to choose whatever suits your projects the best. Using a framework is not always the best choice and for designs that are different, I also don't use a framework. But for a large project like rebuilding the ProcessWire website it can help a lot to have a good foundation and the UIkit framework is this. If you want't to discuss further @pwired, you can create a topic, invite me to an existing one or send me a PM. ? Yes, the current search function is not really good, especially when you have build better search functions with ProcessWire. ? In my opinion it should be able to search the whole website (blog posts, modules, docs, API, etc.) and have autocomplete suggestions. A service like Algolia may be not necessary and this could be probably achieved by ProcessWire alone, but I had to work with a similar CMS for a while which uses Algolia on its website and it was a breeze to have a good search function for learning a new CMS. Of course the CMS is not as powerful as ProcessWire and you can remove the link if this is advertising. Regards, Andreas

I finally solved the problem by setting PHP 7.0 from 'development' to 'production', it had nothing to do with my Mac.

Excited about the new processwire.com! I agree that the search could be better - especially if processwire.com is to be advertised as powered by ProcessWire. I get why the forum search might be poor because that is not powered by PW, but it has long puzzled me why the Modules Directory search is so poor seeing as that is PW-powered. An example: right now in the "Latest Additions" section we can see a module from netcarver titled "Street Address". So how come when I enter the exact words "Street Address" in the search box that module doesn't appear as the first result, and even doesn't appear on the first page? https://modules.processwire.com/search/?q=Street+Address

Hi, After testing with different version of the core. I found that the creation of page in page field function normally up to 3.0.110. It doesn't work anymore from 3.0.111. I will file a bug report to github. Gideon

Happy to hear that the website will be finally rebuild. I hope a modern design will attract more potential users. With UIkit you have made an excellent choice for a framework. I would wish for a better search function, maybe powered by a service like Algolia. ? Having worked with UIkit for two years now, I am obviously biased, but in my opinion it is the best framework at the moment. It is far more complete as Bootstrap with more components and more active development. Gridlex is a grid system, not a framework. The grid component in the UIkit framework is maybe 5% of the whole framework. So the UIkit framework can do 95% more than Gridlex. ?

UIkit3 is a bit more of a utility class oriented CSS framework. The benefits of utility based CSS are excellently summarized in this article, which I side with given my own evolution with CSS: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ Gridlex is just a grid system from what I can tell. If you need all the usual components (accordions, tabs, etc.), UIkit3 has it covered extremely well, especially compared to the other big CSS frameworks. Many great options. I rarely pull in other libraries since UIkit has it covered, and since it's all under one roof, it's very consistent and doesn't lead to conflicts.