wbmnfktr

Just... ??

Thank you, @tooth-paste. The PagefieldPairs module keeps the mapping between tutor:instrument, tutor:ensemble and vice versa in sync. So editors can either add tutors to an instrument/ensemble or add instruments/ensembles to a tutor. This detail seems small at first but it's crucial. Keeping this in sync makes changes much easier and reduces the risk to miss a tutor/instrument/ensemble somewhere and it doesn't matter where this detail gets changed.

I could give it a try next week. Never used this or the version from Nico so we will see. Anything special I should look for?

Thank you very much @cstevensjr. I'll forward your compliment to the designer.

I'm proud to share this newly released custom-made website with you. Musikschule Neumünster https://www.musikschule-neumuenster.de/ Design details The design was built from ground up to give every aspect and every detail of the website its very own unique look. We faced the demand to create a visual experience that is up to date but kind of classic at the same time. A fact you can't describe but you will feel and see it when visiting the website. ? Technical details From top to bottom every detail can be managed in the backend - all instruments, tutors, events, and content pages. In order to make life easier some things are automated (for example: archiving older events or managing the relationship between tutor and instrument). Modules and time-savers ProCache Croppable Image 3 PagefieldPairs MarkupSitemap Hanna Code Jumplinks I hope you enjoy the result as much as we* do. * A little side note to reduce confusion: I'm partner and the developer of Muskaat (design and development bureau based in Neumünster, Germany).

Disclaimer: I'm not against beautiful crafted and designed themes for ProcessWire. Nor am I against an easy entry into the ProcessWire world. Users... who are these users? Is it the company owner that is in need of a one-pager/website to present his new start-up or product? Is it the company that wants to save money and wants to create something on their own? Is it the entrepreneur that needs a langing page builder to collect e-mail addresses in order to sell info products? Is it the photographer / film maker / author / designer that wants to share his/her work? Is it the young and new web developer that wants to know what he could achieve with ProcessWire? Is it the guy that is curious about all kinds of CMSs out there? Is it the long time full stack developer that needs a solid foundation for his ideas and projects? Is it the agency that wants to be flexible in order to create stunning web sites with ease? Is it the WP user you want to encourage to switch the CMS? Is it the user that wants everything just by clicking around? I think ProcessWire is right from the start way more for developers than end-users. Which is a good thing in my opinion. And for those developers we can find some really nice starting points already. Maybe there will be a company someday that wants to close that end-user-gap and pays a developer and designer full-time to create stunning themes/profiles.

Version 0.1.3 works. Now I'll have a closer look.

This looks so interesting that I had to install it but... I tried the latest version from Github and the one from module directory.

Good to know. So... that result is based on SublimePW? I guess more in the backend but that's totally ok. Glad it worked out so well.

Hope everything works now @neophron. Was away and haven't had a chance to respond in time.

So... when you are your client it's more than easy to evaluate the outcome. You can iterate all steps every single time to come to the best result. Maybe you want to outline the expected result on your own and want to discuss this here or you want to contact @ryan as a mastermind of ProcessWire to incorporate everything with him.

I totally agree with that but pages in pages under pages (repeaters) is something different. So plain pages are always more easily to control.

I'd say you or your client should outline the result and therefore you should team up with some advanced people here. Your project sounds really complicated at first but although it seems to be very forward in kind of business logic (what parts of items on each page etc.). Being clueless is totally fine. I don't know at which stage your project is, but it seems you still can control the outcome. I think there is no tutorial to show you the right way for your project right now but with more details about the outcome there might be more users that can help you with that. As always: clients WANT everything without knowing ANYTHING. So you have to define the way.

Can you define what's need to be accomplished?

?

Never ever give endusers too much options as in decisions. A lesson I learned way too early. Give them pre-defined options (for example: 2-columns, 3-columns, 4-columns, big jumbotron, small jumbrotron). Pre-defined sets of settings work much better than fully customizable parts - for my clients and for my cases.

Honestly... go with pages for each event. It's much easier to handle and much easier to [everything]. Repeaters are nice but events/dates/calendar entries are more than just an item in a page. If you used pages instead of repeaters you could use: <?php $eventsToday = $pages->find("template=event, date=today"); ?> Just create a root element, for example: page with template events, for all your events and place all evens underneath it.

I don't know if this will help you but in the last 2 years I/we created several sites and therefore used ProcessWire to manage all of their content. First of all we created plain HTML/CSS prototypes with almost every detail needed. Afterwards I/we created the logic in ProcessWire. Inspired by other page/article builders we created things in ProcessWire with Page Tables (extended) and the the ProField Repeater Matrix. Based on your knowledge in ProcessWire syntax, logic and modules your outcome may differ from simple site structures to absolute individual page/site constructs. You might want to look into the showcase section to find out what others build already. As a starter in ProcessWire you might also want to team up with one of the more advanced users to help you building sites.

Same here. ProCache ProFields FormBuilder Just perfect. Hope I ever told @ryan this. ?

If someone is interested in completing this list of Pro ProcessWire Arguments: https://github.com/webmanufaktur/pw-arguments Already added those from @dragan. Just collecting all arguments we can find. We can later on sort them by groups (for example: marketing, devs, users, clients, ...)

Glad it works this way. You might consider using PW ProCache. It does all this minifying and compiling stuff PLUS awesome and reliable caching. It's paid I know but it's worth every cent.

The problem is that the definitions of real data, studies and 3rd parties have a super broad range. I personally understand them like this: real data = comparable numbers or features studies = examples, references, sites built with ProcessWire 3rd parties = ProcessWire experts (long time ProcessWire users, integrators and developers) We are all 3rd parties (experts) that could create any kind of studies (show examples and projects) to show real data (used features, development time). The videos Jonathan created are a super nice look behind the scenes for someone who is already in web development and CMS-things. My clients aren't into this. They ask me to give advice. They trust me. They want me to tell them what they need. I am the 3rd party (expert) that knows about pitfalls. Let's turn things around. We shouldn't compare ProcessWire to another CMS. We should show and tell the benefits of ProcessWire. For example: ProcessWire is easy to extend. ProcessWire is easy to use. ProcessWire manages all kinds of data structures (books, movies, cars, clothing, what, ever, ...) right from the start. ProcessWire generates all kinds of data exchange formats (RSS, XML, JSON, CSV, ...). ProcessWire doesn't need a dedicated or specialized hosting to perform well. ProcessWire is highly customizable. ProcessWire delivers what is needed. [Your statement here] Just my two cents.

There could also be an issue with AIOM and PHP 7.x There are more threads with this issue - see below: I'd bet you find a solution in them for your problem.

Should be easy to fix.

It seems some resources were loaded non-secure over http:// Try this: https://www.whynopadlock.com/