Leaderboard

For the last couple months, I've been working on a module that does exactly this. It's not a site profile, it's not a theme. I don't know what term would accurately describe it, but its a ProcessWire module that's an opinionated, update-able starting point, oriented towards developers, and brings in a bunch of boilerplate like: an installer that will create fields, templates, pages, hannacodes; it runs through a thorough check before doing anything that may result in an error (module installation errors are aggravating; i'm testing it very thoroughly) the installer will rename your 'templates' dir to something temporary, and then copy a starting 'templates' folder that's prepped for the module (you should only do this on dev) if you try to add it to an existing site with a bunch of data, it will work as long as there are not collisions in some fields and templates; if there are, the module won't install and tell you what you need to change around to allow it to install establishes some new $config variables ('env', 'disableTemplateCache', a few others) built with UIkit 3 in mind, but not hardcoded to it a menu builder based on Repeaters with its own Process Module has its own seo+og+twitter+sitemap metadata fields and uses Profields FieldGroup since that is the best module for handling such a grouping has it's own templates inside the module which can be used, or overridden in /site/templates/; this includes blog sitemap.xml maintenance search in addition to template files being able to be overridden, partial files can be overridden too! some module configuration fields (site_name, maintenance, etc.) the module has documentation and other statistics built into it for easy reference takes full advantage of setting() and markup regions; applies attributes like UIkit 'uk-grid' and other data attributes without "touching" the html; keeps the module flexible and easily allows you to rip out UIkit and swap it for another CSS framework (Bootstrap 4); you'll never need to touch edit the _main.php file because of how regions has been set up has it's on RepeaterMatrix fields with boilerplate matrix-types (headline, text, slideshow, etc. etc.); if the user makes new custom matrix types and a later version of my module brings in a new matrix-type, it will update the RepeaterMatrix field and merge it correctly (tricky to do!); the matrix types use many of the same base fields, thereby allowing you to switch from one matrix type to another without data being destroyed (this was only possible as of 2 weeks ago with the new matrix update) to avoid creating a bunch of 1-off fields for the matrix field for block configuration, it uses the new and quite amazing Mystique fieldtype in a unique way (this was tricky to do); this module is critical to establishing a page-builder that is clean (this was only possible as of April 2019 since the module is brand new) brings in PW's debugger to the frontend (brings in jQuery UI); can be disabled all field and template names don't use any prefixes; this would allow you to dump the module one day in the future if you don't like it, without having a bunch of field and template names that sound too specific to the module Laravel Mix based asset compiler pre-configured with UIkit works with FormBuilder and other modules I often use; works and may require certain Pro modules; eliminates the need for any modules that do blogging, menu building, sitemap, maintenance or seo since this module does it using native ProcessWire login/logout/account/register templates it may include a 'collection' generator for common things like events, products, people, properties, along with some templates for those. don't like the templates my module provides? then just create your own template file in /site/templates/the-template-file.php which will override /site/modules/my-module-name/templates/the-template-file.php Right now I just started building a few sites with it (spent the last 2 months developing it) which will hammer it out further. I will release it late summer, early fall.

It will be free, open-source, like other starter tools out there.

Regarding Site Profiles: what is really missing is a system which turns one into an updatable "theme". Especially when targeting beginners, it would be preferable to provide a way to keep those profiles updated via the admin, like Ryan's module updater. Also, using UIkit 3 as the bases of it would be appealing to beginners and also some experienced devs, for the usual reasons: a popular and documented css "framework" is easy to use, extend and update. The site profile could provide "hooks" so that it can be modified and extended without changing the "core theme". Sure, I did not provide any new ideas at all, it is just a quick summary of what have been sought after dozens and dozens of times here, in the forums. @bernhard might even be working on something like this maybe? ?

To make a long story short... the last few weeks I asked myself... "What kinds of ProcessWire Profiles are missing or could be interesting for new/existing users?" The answers were... feature rich - with the full glory/monty of ProcessWire's features basic default profiles - Agency, Portfolio, CV, kind-of-niche (Photographers, Musicians, ...) verbose and detailed for starters Premium Theme - kind of... like WordPress has So I wanted to ask you... what could be interesting for you and maybe others out there. I already created Sublime (theme based), pwRecipes (super basic starter) and PWBrecipes (advanced starter based on pwRecipes) but still... I want to create and offer more options for new and existing users of ProcessWire. I teamed up with my colleague and friend from Muskaat to create a nice multi-purpose theme/design to provide a nice entry-point for everyone in regards of ProcessWire but this will take time as it will be highly customized and art-directed. There is a side-project of mine (some of you may know about it) where I want to provide all kinds of ProcessWire Barebones like an Agency-Theme-themed starter profile and such. But... to be honest... right now I'm a bit lost. I don't know what could be interesting or what might be needed. And yes... I don't know where to start. ? Is there anything YOU wanted to have being around as a site profile or theme or anything like this? Every answer, idea and recommendation is highly appreciated.

Hi @Jonathan Lahijani, this sounds really great! I'm in for collaboration on this ? @wbmnfktr the problem that I have with site profiles is that they never work the way I want them to work. The setup is usually different to how I develop pw websites on the frontend. I tried to build a frontend theme module once last autumn, but it got complicated quite quickly. So to use such a module it would be quite some effort to get started (same problems as with site profiles). Nevertheless I think that it would be great to have some kind of frontend framework. Something similar to what we already have for the backend. That makes standard tasks easier (think of $config->styles->add(...) ) and - well - more standardized (meaning reusable/shareable). I thought of developing a module for that that would basically just bring in some helper functions (like rendering style and script tags) and that can be extended via sub-modules for CSS frameworks that hold custom methods (like rendering an uikit menu, uikit slider etc). I have not started with that one, but the benefit of such a module would be that we could start with a very simple module that everybody could easily use and it could very easily be extended via pull requests (add uikit slider render method, add uikit modal method etc). And this setup would be 1-click updateable via the PW modules screen. Some kind of migrations module could do the setup of necessary fields. Site profiles don't offer this flexibility! But it sounds like Jonathan is coming up with something great here...

I can only speak for myself. But I feel the same way. I bought the Media Manager, but never used it. Once I used it in a customer project, I had feedback from the customers that the visualization and usability was not good for them. Personally, I'm also a little bothered by that. Why have I never submitted this as a suggestion for improvement? You know: laziness. I always had the hope that others would do it and that there would be an update at some point. ?

I hope you don't mind me giving a little constructive feedback, it's going to be a bit critical but it's just an aspect that I think is being overlooked in an otherwise excellent module. I think one thing that is holding me back from embracing this media manager (actually, we bought this in the past and then never used it -- and this is because there's no demo available) is that it really needs a little love in the styling department. Nothing fancy, but -- if we look at the screenshot above we can see just general CSS issues, alignment of the filter label top right, checkbox and sort icons are too close to the sort options, a lot of negative space between the filters and the nav, image count is too big and not aligned with pagination opposite. The spacing also between the types of media along the top is also not right when compared to how the CMS typically spaces out horizontal navigation. This is just in one screenshot, but these issues persist throughout in various places, such as notifications, upload boxes etc. Considering we have the UIKit CMS theme to base everything off, this kind of thing means that the media manager feels out of place in an otherwise quite neatly organised CMS. Now, people using this media manager for their personal projects will not care about these things, they will roll their eyes and say "why should we care, it's the back-end of the site, only functionality matters" (and in this, I must reiterate, you have done an outstanding job), however if I am building a CMS and handing it over to someone else, I need all aspects to have a consistency in quality because that is reassuring to clients.

@Jonathan Lahijani This all sounds awesome ? Are you going to release it as a free module for community based further development or as a paid module? I think as a community effort it could really take off.

If you follow high-end, professional grade hardware like I do, then this announcement today by Apple will blow your socks off: https://www.apple.com/mac-pro/ Hopefully Nvidia graphics cards will be supported in the near future.

so it seems that modules that send email should always have a way of specifying which WireMail module to use. In other words, Formbuilder should have a setting which scans the installed WireMail modules, and allows the user to select which one to use for FB mails sent; Same for something like ProMailer. The behind-the-scenes selection of which mail module gets used seems to be causing confusion among users, hence the questions on this thread and the issue #733. It also seems possible to have multiple WireMail modules installed which would not conflict with each other, if you always specifically called the module you want to send with, instead of Option A, B or C. I have not tested this theory, but i guess at some point soon there should be some codification of the whole thing...

I made a quick test to try the different options to get an instance of WireMail. Like https://processwire.com/api/ref/wire-mail/ tells us, there are three options: $m = $mail->new(); // option A $m = wireMail(); // option B $m = new WireMail(); // option C With WireMailMailGun installed, option A and B are going out with WireMailMailGun. Option C uses the native WireMail. So for anyone using WireMailMailGun and wanting to send mails outside of MailGun, new WireMail() is the way to go.

I've had to correct myself we didn't even hook, but use the "What roles can view and/or edit this field?" checkboxes and the Access Toggle "Show field in page editor if viewable but not editable (user can see but not change)". We've created a process module which listed all the fields and the corresponding settings to keep an overview on all the settings of the fields. Also we made it easy to bulk edit these field settings/permissions. That being said I doubt if I understand your question right since we already have view/not-edit. We only used hooks to change the output of the fields. Apologies, these kind of requirements can be hard to understand. I think I'm understanding your need since to want view not edit permission on a page level? So to summarise: we didn't need that kind of permission, but rather a per field permissions which is already available.

more info here :

It's pricy sure, but I don't think it's more pricy than other mac hardware given what you actually get. If you really need that kind of hardware it'll cost you a few thousand bucks elsewhere as well.

I have no idea. I never asked. I could try and find out.

Anyone would love to work on such a beast, the issue is – as you pointed out – that it is extremely overpriced so only a few will. I'm on a 2105 MacBook Pro, which was pretty snappy with Sierra and now a little bit slowed down by Mojave but still perfectly usable for web development and graphic design. If I stick to HD only resolution (which I do...) then it is even ok for video editing and occasional 3D rendering works.

Subscriptions (update + VIP support) are valid for 1 year. After that you can renew for a fraction of the original price. Otherwise, I don't send out update reminders but post here in the forums. If you have a valid subscription, you can use the resend download links form to get an email with the download link to the latest version (or use the link in the original email you received after purchase). For renewals, please use the renewal form. Any problems, please PM or send me an email.

$config->urls->templates $config->paths->templates in your config.php can do that.

Hi @Schwab - I'm not sure how this can be done, although given that there are a number of WireMail extension modules out there, I'm sure it must be possible and discussed previously. Might be worth having a look through the threads for WireMail SMTP etc to see if there is any info there. I'm assuming this is @Macrura's version on the module repo - these methods came from the original "plauclair" version. I removed them entirely from my version as they were unnecessary, and didn't look like they would work anyway, given that trackClicks and trackOpens should be booleans (technically integers, but evaluate as either true or false). I updated chriswthomson/WireMailMailgun last week with fallbacks etc, tested on 2.7.2 and above. Ended up moving straight onto another task and completely forgot to post!

I always have those same conflicts when I do a project in which the main language is another and English is secondary. Otherwise it works perfectly. It seems to be a conceptual issue that has not yet been resolved for a while. I think it would be useful during the installation of PW to be able to indicate the default language for the Front-End, to get "www.domain.com/" in that language. The Back-End language could be set or change in the admin as needed.