Textpattern CMS support forum

You are not logged in. Register | Login | Help

#21 2017-12-08 19:14:19

bici
Member
From: vancouver
Registered: 2004-02-24
Posts: 1,242
Website

Re: TXP Themes

Bloke wrote #308183:

Honestly, I think you’ll like it.

ok. perhaps this old dog can still muster to learn a few new tricks
taking off his old codger hat


…. texted postive

Offline

#22 2017-12-08 21:17:58

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,310
Website

Re: TXP Themes

Chris H wrote #308188:

What I did? [snip]

Sounds like you took the right approach. I tend to look around the web for sites I like, steal pay homage to the template via the View Source link and then rip out the static bits and replace them with my own. Tweak the Stylesheet. Job done. Lots of stuff on html5up.net for inspiration that I’ve borrowed for sites.

Now after learning as much as I have, I get to start all over?! ;)

Hehe, hopefully it’s building on concepts already present. Once you get the basics down and tinker with some things, it does start to click. And using XML-style tags to drop in dynamic content in a sea of static HTML is a world away from having to learn PHP to do it.

the show stopper has always been, branding. My sites should be mine. They should
all reflect their intent; both visually as well as the content within. I should not have to look like a Textpattern website clone. But I have always found that arranging, and styling that arrangement in Textpattern to be too prohibitive for my circumstances.

I hear ya. The out-of-the-box template is just that: a template. Phil has gone to great lengths to document the default Pages and Forms with inline comments to help you see what each tag or segment does. That should allow you to start experimenting with tags and attributes. And if anything’s unclear based on feedback we get, we change it or streamline it. The template’s on GitHub (like it or not! I do have a GitLab account actually, just not used it in anger yet).

The proof that you can do striking sites that don’t look Textpatterny is all over the place, a few robbed from our home page or other places I know:

It just takes a bit of craft to get over the learning hump. And that’s where we come in here, or on TxpTips. Search the forum, ask questions, find out tips ‘n trick, then tinker. We’re here to help.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#23 2017-12-08 22:25:02

jakob
Moderator
From: Germany
Registered: 2005-01-20
Posts: 2,926
Website

Re: TXP Themes

You sound like you know your way around web things, so textpattern should be a doddle for you ;-)

Oh great. Now after learning as much as I have, I get to start all over?! ;)

;-) Actually, there’s nothing to worry about. The basic principles of page templates, forms and txp:tags are the same as they have always been. It’s only the way of packaging them in themes that is new, and that is pretty much a direct reflection of the pattern you see on the Presentation tab, except as files and folders.

But the show stopper has always been branding. My sites should be mine. They should all reflect their intent; both visually as well as the content within. I should not have to look like a Textpattern website clone.

I’d say that’s pretty much what textpattern can do. As much as I admire the simplicity of Phil’s starting template, I always start from scratch. You can craft your page HTML almost exactly how you want it, which means you can produce almost any layout you want.

I have over 80 domains — sites … That’s a lot of work. I’ve already created the layout, and style. As well as graphics.

If your sites are on the same server and follow similar patterns, you may find the multisite option very useful. It’s existed for a long time, but has recently been reworked for the upcoming 4.7 (this branch). I’ve been using this in an earlier iteration for a while now for a few sites run by the same organisation that share similar elements. In combination with working on the templates as flat files e.g. with oui_flat rather than through the admin interface (and site specific repos if you want to, too, in my case on gitlab like you mention), you can share some common resources across multiple sites. Example directory setup:


/libs
  /sass
  /css
  /scripts
  /vendors
/sites
  /site-a
  /site-b
  /site-c
  /site-d
/textpattern

Each site has its own front end and admin area, and each site can have its own templates and styling, but you only have one installation of textpattern for them all. You only need base stuff on the common bits you want. It works nicely if you have a collection of base sass files you use as a library of styled components, and have your site-specific styling on top of that. If you find you need to update a styled component (e.g. maybe remove some no longer needed browser prefix, or to update normalize.css), or update a javascript file (e.g. a slider) across all the sites, or you want to update textpattern for all your sites, you just need to update the respective item and recompile your css files.

That said …

github, sass …

… you don’t need github at all for textpattern, likewise sass, node, grunt, npm or any of those helpers. You can still write good old HTML and CSS, break your page down into sensible chunks and sew them together with txp tags.


TXP Builders – finely-crafted code, design and txp

Offline

#24 2017-12-09 01:30:07

Chris H
New Member
From: In front of my monitor
Registered: 2017-11-20
Posts: 8

Re: TXP Themes

Bloke wrote #308193:

Sounds like you took the right approach. I tend to look around the web for sites I like, steal pay homage to the template via the View Source link and then rip out the static bits and replace them with my own. Tweak the Stylesheet. Job done. Lots of stuff on html5up.net for inspiration that I’ve borrowed for sites.

Hehe, hopefully it’s building on concepts already present. Once you get the basics down and tinker with some things, it does start to click. And using XML-style tags to drop in dynamic content in a sea of static HTML is a world away from having to learn PHP to do it.

I hear ya. The out-of-the-box template is just that: a template. Phil has gone to great lengths to document the default Pages and Forms with inline comments to help you see what each tag or segment does. That should allow you to start experimenting with tags and attributes. And if anything’s unclear based on feedback we get, we change it or streamline it. The template’s on GitHub (like it or not! I do have a GitLab account actually, just not used it in anger yet).

The proof that you can do striking sites that don’t look Textpatterny is all over the place, a few robbed from our home page or other places I know:

It just takes a bit of craft to get over the learning hump. And that’s where we come in here, or on TxpTips. Search the forum, ask questions, find out tips ‘n trick, then tinker. We’re here to help.

A big thanks to you, Bloke! I must admit, much of what I grumbled about was just the frustration
(see; lazy) of knowing I had (already) made my decision, and was just going to have to work it out, no matter how hard it seemed initially. :-)

and because misery loves company; ahem… and because I knew it would be great to get some quick answers to my seemingly stupid questions; I thought I’d test the waters here at the Forum, and boy, am I glad I did — you guys are great! Thank you! :-)

Gives me much hope for a smooth ride/transition. Much appreciated!

As to Phil’s“default” KISS — Keep It Simple Stupid, Theme. I’m glad he did it the way he did. Honestly, IMHO he made the right decision. Flooding “newbies”, not unlike myself, with technical data (unfamiliar tags, and other markup) I think, just overwhelms newcomers. It would just seem too far out of reach. So I have nothing derogatory to say about that theme. I only referenced it; in regards to not wanting my site(s) to look like a Textpattern mirror, or clone. Not that there is anything wrong with Textpattern. Just that I wanted my site(s) to like like my site(s). :-)

Well. I think I’d better get to figuring out how to get Textpattern to present my already created layout, and markup the way it is. Or get my layout, and markup to use Textpattern — however it’s intended to work. :P

Thanks for taking the time to provide some helpful references, and wisdom, Bloke! All the best to you!

—Chris

Offline

#25 2017-12-09 01:53:57

Chris H
New Member
From: In front of my monitor
Registered: 2017-11-20
Posts: 8

Re: TXP Themes

jakob wrote #308194:

You sound like you know your way around web things, so textpattern should be a doddle for you ;-)

You’d think ;-)

;-) Actually, there’s nothing to worry about. The basic principles of page templates, forms and txp:tags are the same as they have always been. It’s only the way of packaging them in themes that is new, and that is pretty much a direct reflection of the pattern you see on the Presentation tab, except as files and folders.

That’s reassuring!

I’d say that’s pretty much what textpattern can do. As much as I admire the simplicity of Phil’s starting template, I always start from scratch. You can craft your page HTML almost exactly how you want it, which means you can produce almost any layout you want.

If your sites are on the same server and follow similar patterns, you may find the multisite option very useful. It’s existed for a long time, but has recently been reworked for the upcoming 4.7 (this branch). I’ve been using this in an earlier iteration for a while now for a few sites run by the same organisation that share similar elements. In combination with working on the templates as flat files e.g. with oui_flat rather than through the admin interface (and site specific repos if you want to, too, in my case on gitlab like you mention), you can share some common resources across multiple sites. Example directory setup:

...

Bummer. The Forum ate you’re codeblock. :-(
But, yea. That may well be a good idea. But I’m just going to start with one. I’m still on the bottom rung of the ladder yet, where Textpattern is concerned. I’ll come back to Multisite, once I’m a bit better versed in TXP. :-)

Each site has its own front end and admin area, and each site can have its own templates and styling, but you only have one installation of textpattern for them all. You only need base stuff on the common bits you want. It works nicely if you have a collection of base sass files you use as a library of styled components, and have your site-specific styling on top of that. If you find you need to update a styled component (e.g. maybe remove some no longer needed browser prefix, or to update normalize.css), or update a javascript file (e.g. a slider) across all the sites, or you want to update textpattern for all your sites, you just need to update the respective item and recompile your css files.

That said …
… you don’t need github at all for textpattern, likewise sass, node, grunt, npm or any of those helpers. You can still write good old HTML and CSS, break your page down into sensible chunks and sew them together with txp tags.

Bummer. Looks like the Forum also ate your reference to oui_flat. :-(
None-the-less. I had already opened the link in another tab. This is great help — thank you! I can definately get my head around this. :-)
I can’t tell you how relieved I am I don’t require those other “helpers”. Not that they’re bad. Just that I’m more “old school”. I completely understand, and can easily use them. But they’re just not “my cup of tea”. Thanks for mentioning that. :-)

jakob, you’ve really hit the nail on the head here. You’re completely “on target” for addressing all my (previous) concerns. Your comments here have gone a long ways to helping me wrap my head around much of all this, combined with all the helpful hints, and wisdom from Bloke. I feel a great deal more comfortable with making Textpattern my only choice for Site management. Really shortens the “learning curve”!

A huge thanks to you both!

—Chris

Last edited by Chris H (2017-12-09 01:55:35)

Offline

Board footer

Powered by FluxBB