Jump to content

Thinking about building an "easy" site profile


statestreet
 Share

Recommended Posts

Edited title to change "template" to "profile"

Over the weekend, a friend showed me a temp site he'd set up for an academic project. He had spent all afternoon wrestling with Drupal to get a few pages up, and while I was quick to suggest that next time he try a more appropriate CMS for a five-page site, I wondered what the best suggestion would be.

I suggested GetSimple because it's the simplest I've used, but that got me thinking about my favorite CMS: ProcessWire doesn't really have a true default template like you get with GetSimple, WordPress or Drupal, only an example site. It makes sense, as PW isn't really geared toward projects that would use a default site theme, but I wonder if there might be some benefit to having an "easy" site template that would let someone start a simple site with PW but grow into something much bigger if they ever needed to.

I'm thinking I'd probably build the template with some hidden pages to configure parts of the template that are hard-coded in normal bespoke templates, such as the site title (or maybe an image upload) in the header, footer info, and so on. Does this sound like a good idea? Any suggestions?

[edit] I really shouldn't be calling this a "template" because that term in PW refers to the individual page templates, and not the set of them. It's not really a theme, either, because it's also page content in the admin. Is this technically a site "profile" that I'm describing here?

Link to comment
Share on other sites

You're right. What you are describing is a profile.

I was also thinking that it would be nice if there was some profiles to share in PW website. But even better would be to create a PW community driven profile, maybe a blog, or a tumbleblog with everything that could make it very simple to use and really great (posting by email or bookmarklet, user being able to change background color, image header, logo, text typeface, simple widgets, etc etc etc). Would be great publicity for PW, and encourage non developers to also try it.

Link to comment
Share on other sites

Interesting. How do you import or export profiles?

Encouraging your average WordPress user to try ProcessWire for their next site is definitely one of the potential benefits of this idea. I wonder, though... If PW attained a certain level of popularity, would the profile format work as an off-the-shelf setup in the ThemeForest vein? Or is it too bespoke-oriented? Are the people who need a quick website and buy from ThemeForest better served by WordPress anyway?

PW is such a powerful system that it feels like it's way more than your average quickie site admin needs, and yet it's almost easier to create a new page in PW than it is in WP (and honestly much easier than in Drupal). So it seems like there really is room to grow into the less-technical user market, at least from my perspective.

Link to comment
Share on other sites

You can export profiles using the ProfileExport module, and then import them using the PW installer. I've been using it for site migrations lately and it works well.

I think it's not a bad idea to have a profile like you mentioned. Though I think PW's appeal is really to the designer/developer audience that can appreciate what ProcessWire does (relative to something like WordPress). But I'm all for expanding the audience. If having such a profile broadens our appeal, seems like a good thing.

Link to comment
Share on other sites

I tend not to like the idea of having too many profiles or templates as a product becomes more and more popular (and I think PW will), it makes people not able to distinguish between what well done and very badly done. Same thing goes for plugins. That's why a very well done community driven profile would be a good start. Something that could be proudly presented in the homepage as an example of what can be achieved with PW, and at the same time, something that would call the attention of a different kind of users. I also think we shouldn't be in the middle with this. If PW is directed at Designers/Developers, than this profile could be directed at those that wouldn't even touch the template files.

Link to comment
Share on other sites

Exactly. I think there's room for a profile that presents an elegant and usable site format for non-technical users, that people would want to use as-is, kind of like the classic Kubrick theme in WordPress. Maybe offer just enough customization to reduce the temptation to mangle it one way or another. :)

I actually started on this this afternoon as I had some free time at work, and quickly realized I need to learn more about the admin system. Currently, I have fields for site name, tagline, and footer content. Originally, I had intended to just drop these fields into a page and set it to hidden, but—d'oh—of course, I could just create a new page in the admin. So I did that, but I'm not sure what to do with it next: do I need to select a process for it? How do I get those fields onto this new admin page?

Link to comment
Share on other sites

For using the admin template you would have to create a process module, and then choose it from the select process field. Maybe it would easier to build the settings form as you where planning. But it would be very nice to have a module that simply places an admin link to a specific page edit, wouldn't it? :)

Link to comment
Share on other sites

As always seems to be the case when I use ProcessWire, this is going faster than I thought it would. :)

I'm hoping to have an alpha version ready in the next few days, but here's a preview:

tE3Sx.png

The goal here is a versatile, one-stop theme that looks good enough right out of the box that people would be proud to use it as-is for their site (like some of the great premium WordPress themes like Khoi Vinh's Basic Maths or iA Japan's iA3, only free ;) ), but also a site profile that does two things: Has a few "advanced features" that aren't so effortless with other popular CMSs such as footer pages and switchable image slots, and demonstrates that these features are built using nothing more than PW's field system and a few lines of PHP.

Link to comment
Share on other sites

Good work statestreet - that looks great!

I think you're definitely right about the goals of such a profile - showing off enough to entice someone to learn more, wonder how it can be this easy, and actually be able to use it as their site (or rapid prototyping for a project or whatever they want :)).

Link to comment
Share on other sites

This is a great idea. The more examples that are available of how to get started, the better.

Even though I think I have got over the earliest teething troubles of using ProcessWire, I look forward to downloading this profile when it is released. I am sure I will learn loads more from it!

Link to comment
Share on other sites

This is a great initiative and a good way of showcasing PW's capabilities to users more familier with WordPress or Drupal. Profiles also seem like a great way to rapidly prototype websites.

Are you thinking of including a blog section statestreet? A blog with categories is a bit more time consuming to build and probably a bit confusing for your average user starting out with PW - at least that was certainly the case for me. Once you get the page based paradigm in PW it's a breeze and showing this in profile should really help.

Great work so far!!!

Link to comment
Share on other sites

Looking great. What do you guys think of the profile supporting mobile devices? Perhaps responsively. Also wondering if there might be value in building the profile from a framework like HTML Kickstart?

  • Like 1
Link to comment
Share on other sites

I don't know what @statestreet thinks of this, but I think the conditions are gathered to build an official (not a replacement for the default) first PW profile. A beautiful and flexible theme with everything done right. I would prefer responsive instead of mobile version.

Link to comment
Share on other sites

I agree, responsive sounds great. As far as I know, Kickstart is not responsive (or at least not built in)? Outside of that desire, it seems pretty fantastic... I'm going to be experimenting with it here on another project.

Link to comment
Share on other sites

Sorry I haven't shared this yet—I want to put this up on GitHub but I'm fairly new to Git in general, so it's taking me a bit longer than I anticipated.

I think responsive could work for this. The only thing I don't like so much about responsive is handling images: I'd much prefer using PW's nice image rendering to crank out appropriately-sized versions instead of loading the whole thing and scaling it down in CSS, but maybe there's a way to do both, calling $image->size() twice and hiding/showing the appropriate one based on the viewport size.

Link to comment
Share on other sites

In this case wouldn't be a big problem, If you keep the content block with small width differences, and play with 1 sidebar, 2 sidebar or no sidebar depending on the screensize, the only image that would need more thinking is the big one in the header.

Link to comment
Share on other sites

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...