Textpattern CMS support forum

You are not logged in. Register | Login | Help

#21 2015-07-09 08:34:06

Destry
Moderator
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,020
Website

Re: A new direction for TXP Magazine?

hcgtv wrote #292870:

Damn Destry, I didn’t know all the goings on behind the scene at TXP Mag, you ran it like the New York Times.

Heh. A structured workflow at least, I guess you could say. It’s tough to pull off grassroots situations, though.

Thanks for all your tireless work, maybe one day we’ll have Nirvana.

Thanks. A common Nirvana at that. There’s a concept.


The text persuades, the *notes prove。

Offline

#22 2015-07-09 08:42:44

Destry
Moderator
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,020
Website

Re: A new direction for TXP Magazine?

@Bloke: One thing we could do, which I only suggest for the sake of who the proposal is really for (bi-lingual readers; English as a second) is split the article in two:

  • A new direction for TXP Magazine?
  • A TXP Magazine proposal

The two section are basically written this way already. It would just need a couple copy adjustments and cross-linking between articles to bridge the two. Easy. Forum links stay the same, etc.


The text persuades, the *notes prove。

Offline

#23 2015-07-09 09:46:22

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

Re: A new direction for TXP Magazine?

Destry wrote #292940:

split the article in two:

Crossed my mind.


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

#24 2015-07-09 12:34:26

Destry
Moderator
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,020
Website

Re: A new direction for TXP Magazine?

Might be useful to clearly see what options exist for Textpattern to consider (what’s best against it’s abilities and priorities):

  1. Keep existing mag and model and find new lion tamer (tough, dangerous gig)
  2. The current i18n proposal (still seems complex; unlikely to garner enough interest to merit the re-dev)
  3. Use platform as the newsletter/mail list desk? (wavesource is editor); this gave me the idea
  4. Coop site to a dedicated Txp “journo” for in-depth pieces (longform stuff)
  5. Put domain into indefinite hibernation (understandable against human resources, but unfortunate and likely)
  6. Other?

The text persuades, the *notes prove。

Offline

#25 2015-07-09 13:34:31

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 959
Website

Re: A new direction for TXP Magazine?

Destry – if #4 are you thinking a quasi archive type of site – the best long form items we’ve collect over time, plus the occasional addition?

  1. also seems reasonable if #2 doesn’t fly.

Offline

#26 2015-07-09 15:28:09

Destry
Moderator
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,020
Website

Re: A new direction for TXP Magazine?

maverick wrote #292974:

Destry – if #4 are you thinking a quasi archive type of site – the best long form items we’ve collect over time, plus the occasional addition?

Actually, I hadn’t thought of the curate/archive angle. That’s good.

I was just thinking, based on my experience as editor in a collaborative workflow, where I could have wrote more but it wasn’t really appropriate under the circumstances, that it might work better if the site is recast as a solo responsibility. (Not to be taken as raising my hand, exactly.)

For example, Textpattern enters an agreement with someone (a solo writer/editor) where Textpattern maintains the site code/architecture/design and the editor writes at least one in-depth piece per month (no crucifixion if they’re a little late). Some refactoring might change the mag structure from an “issues” model to a single-article flow, but otherwise a lot is the same, just one writer instead of multi-contributors. That takes a lot of coordination overhead out of it, actually, which is needed.

Articles would still be things like people spotlights, thorough descriptions of new features with demos (e.g., imagine a detailed cover of new custom fields), Txp site profiles (big ticket stuff), etc.

Again, the emphasis here is on depth and quality per article, not speed and volume in article turnaround. Pieces would typically be longer than what works for a blog post (we saw how well that went over already).

And you can see how site profiles could handle “featured sites” content, removing that in the .com site (while still being in a “family” property). That would be a boon because there’s no editor to maintain .com content, which is always outdated.

Content in textpattern.com, with the exception of the blog, would ideally be a stripped-down, focused product site for a CMS. No docs, no FAQs, no gallery, no “our community rocks” puff-uppery, etc. etc. Just a direct focus on the CMS — features and download. Boom! Other stuff from community in blog by category for intended audience interests, news and marketing stuff in the MailChimp list (or whatever tech for that is picked), and high-end pieces in the mag.

But, yeah, I like the idea you bring too, that the mag editor serves a “curator” role too, responsible for finding/fixing/adding other pieces from around the web and re-publishing them in the mag with author permission. Why not? Great idea!

As I hear myself write this out, it still sounds like something already tried and failed, or a lot of expectation on the shoulders of one person. I mean, I know I could deliver something like that, but it’s still a lot of work. The writing is one thing, but there’s the research, contacting people, interviewing, following up with devs, etc — a lot to do before the writing even begins.

Last edited by Destry (2015-07-09 16:16:35)


The text persuades, the *notes prove。

Offline

Board footer

Powered by FluxBB