I'd like to set up a site that showcases projects built with ProcessWire. As an full-time independent developer, I'm hoping a site like this will promote ProcessWire and help persuade clients into using ProcessWire for future projects. My current favorite inspirational showcase site is http://www.siteinspire.com/
With that being said, I have a few questions for the ProcessWire community:
1. Is this a good or bad idea? Has anyone already started something similar?
2. Does this step on Ryan's or the official ProcessWire site's toes?
3. Would you submit your projects to a site that isn't officially maintained by Ryan?
4. I've purchased several possible domains. Is there one you prefer more than the others?
5. If you think this is a good idea, what features would you like to see on the site?
Does ProcessWire have include the ability to automatically send a welcome message to new users when their account is created? I'd like to send new users their login information, as well as some helpful links related to ProcessWire and their project. Ideally, I'd like to be able to edit the message.
Currently, I have the following set up in TextExpander. The capitalized words are changed using TextExpander's fill-in functionality.
Your new site has been successfully set up at:
You'll use ProcessWire to manage your site's content. You can log into your administrator account with the following information:
Password: PASSWORD (case-sensitive)
Need to reset your password? Click on the 'Forgot your password?' link on the login page:
Learn how to create a strong and secure password:
What makes ProcessWire so great? Learn about the set of features designed to make working with your content easy and enjoyable:
Find out what makes ProcessWire unique from other content management systems:
We hope you enjoy your new site!
Is the following concept possible using ProcessWire?
1. The mobile version of a site would reside at m.exampledomain.com and the desktop version at exampledomain.com
2. The mobile version would use responsive web design, and the desktop version would not.
3. The mobile version would have a limited experience, displaying less content and functionality than the desktop version of the site.
4. Both sites would use a single database, maintained using only one ProcessWire Admin. There wouldn't be a set of separate fields for each site; instead both sites would use the same set of fields from the same single database.
5. Each site would use a different set of ProcessWire templates.
The concept here is that the client maintains the desktop version and the content is used in two sets of templates (mobile and desktop). This is different than using responsive web design and presenting the same set of templates differently for both mobile and desktop.