Fay's Joint - My first ProcessWire website.

[fay]

Hi

I recently finished my first ProcessWire website, and it's a gallery of black and white vintage erotica. Here's what I used:

• Default ProcessWire Installation.
• Bootstrap, jQuery (for the bootstrap carousel and MediaElement.js), MediaElement.js and Glyphicons (they come with Bootstrap.)

Photos are sharing two templates (one is for single photo entries, and the other is for multiple photo entries and it uses Bootstrap's carousel.), Featurettes have their own template and there is only one. I also have a simple tagging system.

It didn't really take me a while to figure ProcessWire out, it really was a piece of cake for someone without a lot of PHP knowledge. I had way more trouble getting a hang of WordPress than ProcessWire. It's a great piece of software.

Before I forget, http://faysjoint.com

Fay

[DaveP]

Loving both the site and the subject. Looking good on mobile.

[pwired]

uhm

[fay]

Loving both the site and the subject. Looking good on mobile.

Thanks!

My website works on all resolutions thanks to Bootstrap.

uhm

??

[MatthewSchenker]

Greetings,

Nice work. Thanks for exposing us to your site!

Matthew

[diogo]

Works well on mobile, I only had a little trouble with the clicking area on the navigation links. on small screens they are a bit to close from each other and from the title and the search.

Please excuse Dr Spock, sometimes he is not very clear here in the forum

[fay]

What resolution? I checked on http://responsinator.com/?url=faysjoint.com and it seems to work on all smaller resolutions, even 240px. Do you think I should add some padding between the links anyway?

[pwired]

Please excuse Dr Spock, sometimes he is not very clear here in the forum

all right, all right, translation uhm => front end use in processwire, or should i say up front

[diogo]

320 x 480, but I'm looking at it in a big screen now and i still feel that the header needs some breathing space in general. Some padding should solve I guess.

[fay]

all right, all right, translation uhm => front end use in processwire, or should i say up front

I still don't really understand what is it you meant with it though.

320 x 480, but I'm looking at it in a big screen now and i still feel that the header needs some breathing space in general. Some padding should solve I guess.

Any better now?

[MatthewSchenker]

Greetings,

It seems improved. I just viewed it to on the iPad and iPhone (Safari). See attached screen shots.

Thanks,

Matthew

[MatthewSchenker]

all right, all right, translation uhm => front end use in processwire, or should i say up front

I think perhaps he is wondering what the back-end looks like.

Thanks,

Matthew

[pwired]

[fay]

I think perhaps he is wondering what the back-end looks like.

Thanks,

Matthew

Oh, right. I didn't begin with customization of the back-end yet.

Here are some screenshots:

http://faysjoint.com/admin_1.png

http://faysjoint.com/admin_2.png

http://faysjoint.com/admin_3.png

http://faysjoint.com/admin_4.png

http://faysjoint.com/admin_5.png

[ryan]

Fay, I noticed your last two screenshots contain a plain HTML field with raw visible HTML tags. Is that what you intended, or is this supposed to be a rich text field? I ask because it's a little unusual to edit raw HTML like that (that's what TinyMCE and CKEditor are great for, or an LML like Markdown or Textile). Always respect for editing raw HTML, but it's not something I see very often, so just wanted to make sure there's not some JS error or something blocking the rich text editor.  

[fay]

Nice catch! Yes, it's intentional. I'm not against rich text editors per se (I use TinyMCE on Legal Statements & Contact) but I just find this approach easier, because I'd have an extra step to add the class for the description text itself on TinyMCE.