I had a Slack chat with my colleagues recently that we thought might be of interest to other themers.
Ernesto: I have a small theming question I’d like to clarify. Let’s say I have a page that is used as front page and there’s a section in the front page that displays some text. I can display the page’s content there, using
the_content(), but I would only want there to be text — no fancy shortcodes or custom content, just basic formatting.
Would you create your own content filter for that section? Something like adding
wp_kses_post (possibly others too, if they make sense) into that filter? Or just use
I am leaning towards the filter approach, since it may give me what I want, without giving users full liberty to put all sorts of things into a div that is supposed to hold some minor text and content.
Tammie: This feels like a UX issue too. Why are you restricting?
Ernesto: Because it’s not a full content post, it’s a space where there should be one or two paragraphs at most. Just some introductory text.
Tammie: Then why let full content appear anyway? Post restricting is expected behaviour, page restricting isn’t. Let’s not add a new behaviour.
the_content() and if user messes up, well…
If you limit that it’s adding a new behaviour.
Ernesto: Yeah, that makes sense.
Caroline: I’d agree with keeping it as simple as possible.
Tammie: Maybe they want to add a link. Adding a link there is a totally expected thing.
the_content() works 🙂 And then with [the new content settings feature we’re working on] they could change it to
the_excerpt() someday soon.
Tammie: Yep, win win.
Ernesto: Very good point… I see no problem with using
the_content(), but since I know users want to add everything + the kitchen sink, I was just trying to avoid that.
Ernesto: So yeah, win win.
Tammie: Well that’s assuming they do. Many don’t.
Technically the ones that do make up for ones that don’t😉
the_content() all the way.
Kathryn: Agreed 100%.
Ernesto: It’s interesting knowing your thoughts on this😀
David: If they put too much content in there, make the theme break elegantly.
Kathryn: If user wants to make their site busy, let them do it.
Kathryn: Users shouldn’t put a zillion widgets in one widget area, but we let them do that😉
Ernesto: Hehe, let them break and then tell them well… you shouldn’t do that.
David: It’s our job as developers to make themes that just work. Part of that is making edge cases not blow up a theme.
Tammie: Well, there’s hand holding and there is spoon feeding. Hands > spoons.
Kathryn: Very much agree re: “Part of that is making edge cases not blow up a theme.”
Also, making cluttered/ugly is different than “breaking”.
Ernesto: I think this is a very good & mature way of thinking… adding stuff for edge cases just makes the theme bloated.
Tammie: Also, edge cases aren’t always bad. We tend to have edge PTSD.
Kathryn: And there’s so much in between cluttered and minimal that is going to look just fine, I think.
Ernesto: Right, very good discussion and input, thank you so much, that’s why I love y’all:-)
Tammie: Also I kind of love the fact you didn’t even suggest a theme option for that.
Tammie: Times have changed and I like them.
Ernesto: I was going to admit it crossed my mind, but then noticed a page would be cleaner.
Tammie: And that’s why I have even more love about it. Self correcting rocks.
Ernesto: “If they put too much content in there, make the theme break elegantly.” – David Kennedy: Seriously?
David: Yep, I think that’s a sign of theme greatness.
Ernesto: That’s right, the I did what I could to hold the user’s content attitude, I like that too. Definitely adding some float-clearing there.
David: Before this, I worked at a place with a giant, talented editorial team. I thought, Perfect, we can work with them to get exactly the content we need! But they found ways to break things all the time. So whether you know the content, or don’t know it, make it highly fault tolerant.
Ernesto: Very very good advice, thank you!