Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Inserting PHP code block into content article
Many interesting facets to this gem, yes.
Wiki page structure: Yes, we probably want to leave the consistent page structure alone or it will turn into tornado soup pretty quickly. I’ll straighten that out.
Wiki page meta: Meta tags won’t do anything to improve ranking of that page. The problem is the page is titled “PHP” (and that’s not going to change because it’s consistent with tag page titling). How many things online are competing with those three letters? Yeah. It’s like expecting “CMS” alone to race Textpattern to the top. Page section headers are the key (and keywords in body copy), and it shouldn’t matter where on the page. (An h2 is an h2 is an h2, etc. down the line.)
Markup, markdown, mark-around help: With regard to the markup mystery, I’d say we do have a gap (or few) in communicating certain bits of knowledge about Textile (or whatever) when the rare situation come up.
I’ve always been of the mind that the wiki should have a primary side link for “Textile use” or “Markup editing” (less Textile specific so it can cross other filter/syntax territory too), or whatever, where we don’t just show the formatting syntax like you see in the admin-side, but where actual use cases are more specifically demonstrated and easily found than they might otherwise be in tag page examples (still a hit or miss affair there).
Anyone opposed to the idea of doing that? We could start a single page and as examples grow, we organize them and branch out if necessary. Even if it’s just two or three examples, like demonstrated in this thread, it can be worthwhile and make a difference for someone. Here’s another situation that comes to mind that I run into all the time, using straight brackets: e.g., ...an opening clause ending with a ["link"url]--a clause inside em dashes--another clause...). I think I have that right. ;)
Offline
Re: Inserting PHP code block into content article
Destry wrote:
a primary side link for “Textile use” or “Markup editing” (less Textile specific so it can cross other filter/syntax territory too), or whatever…
Maybe “Formatting”? Or “Content formatting”?
Offline
#15 2012-10-04 17:30:11
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Inserting PHP code block into content article
Destry, because I’m not sure I understand you correctly: do you mean there would be a “formatting” (or whatever you decide to name it) link only on tag pages for which formatting examples exist? Similar to the links to translated tag pages? Or a link to a generic page that contains examples for various tags?
Offline
Re: Inserting PHP code block into content article
Sorry, I wasn’t very clear. Neither of those, actually. But now that I think about it… what I was trying to get it doesn’t make a lot of sense if we remember there’s http://txstyle.org/, and/or whatever Steve will be drumming up. These sites that are outside of the documentation are no as readily found or intuitive for new users, but we probably shouldn’t reinvent the wheel right now.
Offline