Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Magazine to newsletter
Bloke, Phil,
+1 on all that.
Offline
Re: Magazine to newsletter
Bloke wrote #292339:
And anyone who complains there’s no activity has themself partially to blame :-D
True, I think I’ve only done one official blog since being a dev – my bad!
Offline
Re: Magazine to newsletter
Ultimately we come to the question of what to do with txpmag.com if it’s not going to actually work as a project magazine.
I can’t answer that because my role was as editor in favor of making a magazine work. But without a budget, or even a modicum of coin flowage through the pipes, that might otherwise entice knowledgable writers, then my role as magazine editor comes to an end and the property owner has to make a decision.
One option for the property owner, assuming they think a magazine can still work, is to find another editor to take up the monumental task. Another option is to turn the property into something else, but the domain name itself kind of limits that.
A third crazy option that addresses the multi-lingual slant is to open it up as a multilingual “community” magazine. In other words, we don’t worry about translation, writers can submit whatever language they want and that gets published for whoever can read it, though someone should make attempts to keep languages staggered as much as possible. There should still be some editing attempts, of course (and appointed editors in the CMS for each language in that respect), but no effort at trying to unify articles to one language standard. Any respectable topic goes if it just means getting people writing. A set of categories for each language makes it easy to RSS each stream? Etc.
Last edited by Destry (2015-06-30 09:38:08)
Offline
Re: Magazine to newsletter
So, exploring this notion of an open blog, what infrastructure does it need?
- An inbox somewhere that a bunch of us have access to?
- Some third party content-writing channel that we are pinged about when there’s activity?
- Somewhere that acts as a moderation queue of some kind?
- A way to tag an article as from a contributing author (a custom field?) and maybe a way on .com to filter content by contributing author? Although it’d primarily be a newsletter channel, some way to slice and dice the content might be handy when searching for posts. Bear in mind that, without each contributor having an actual account, we can’t leverage the built-in author tags / URL flow.
- Stick with the
/weblogURL endpoint or change it to something else and add a redirect from/weblogto the new location for old posts? - Think about a seamless way for content to be “approved” and “tagged” instead of having to log into .com, go to the Write panel, paste the content in, set the categories, set the custom fields, Publish. Or is login and manual wrangling necessary, given the sensitive nature of the .com domain being the key to our downloads? If so, is there anywhere else, less sensitive, we could move the blog to and redirect existing links? TXP Mag maybe, since we have the contributing author thing set up already? We could read the feed from there and list the content on .com for added visibility, with links to the actual content in TXP Mag’s newsletter channel.
Are there any cool workflow tools out there that could help us achieve this? Or is an email inbox the simplest, lowest cost of ownership solution in the KISS mould?
Then there’s the need for a way to get the message out that the blog is in the hands of the community too. Twitter, G+, here, on the weblog itself… :-)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Magazine to newsletter
Destry wrote #292343:
A third crazy option that addresses the multi-lingual slant is to open it up as a multilingual “community” magazine. In other words, we don’t worry about translation, writers can submit whatever language they want and that gets published for whoever can read it, though someone should make attempts to keep languages staggered as much as possible. There should still be some editing attempts, of course (and appointed editors in the CMS for each language in that respect), but no effort at trying to unify articles to one language standard. Any respectable topic goes if it just means getting people writing. A set of categories for each language makes it easy to RSS each stream? Etc.
In fact, the magazine could be for every language except English, with all English writing efforts going to the Textpattern blog.
I’m starting to like this idea.
So, to summarize, the “international” magazine would:
- Be open to any language writer. No translation needed.
- A language editor must first be appointed in the system before any articles for that language are published. (Addressing the serious matter of quality control. You don’t want evil being published unknowingly by someone from the Far East, for example.)
- Articles in any given languages should be staggered as much as possible to avoid bias of long streams of one language only. (Maybe we keep the “issue” model and each issue is composed of one article from various languages. An issues doesn’t publish unless there’s at least two.)
- Languages have their own RSS feeds.
Other?
Imagine the fun design ideas to be had with this too… a different theme/typography, for example, for each language type, where it would work culturally.
Last edited by Destry (2015-06-30 09:58:18)
Offline
Re: Magazine to newsletter
Destry wrote #292346:
Imagine the fun design ideas to be had with this
That’s just crazy enough to work. Explore…
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Magazine to newsletter
OK, I promised Stef I’d write some copy for .com blog post about translation strings – so I’ll get that done by this weekend.
That ticks the boxes for a) English language content b) an international twist c) a non-dev person as the author d) a call to action and e) a refocus on the summer 2015 epic The Road to 4.6.
Offline
Re: Magazine to newsletter
Bloke wrote #292347:
That’s just crazy enough to work. Explore…
Well, none of that will get done if left to me. For this to work at all, those respective “languages” need to coordinate themselves and make the mechanics happen. And that likely means Txp giving reps from each language the ability to merge their stuff. Someone has to oversee all that from Txp’s side.
Basically, for those non-English speakers trying to promote using the magazine for non-English content, they need to put their actions where their ideas are. ¯\_(ツ)_/¯
Offline
Re: Magazine to newsletter
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Magazine to newsletter
Destry wrote #292351:
for those non-English speakers trying to promote using the magazine for non-English content, they need to put their actions where their ideas are.
Absolutely. That might dictate how far this idea goes. Wanna write a guest blog post outlining the proposal with calls to action? We could pimp it here and see if anyone bites as a first step.
I’m still not quite clear — on a technical, admin-side level — how it would work:
- Section per language
- Use a custom field for language designator
- Use a category
- Or a tag
and how we’d then filter that into feeds, but I’m sure someone has some ideas on how to figure out a decent workflow that ticks all the boxes.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Magazine to newsletter
Bloke wrote #292353:
Wanna write a guest blog post outlining the proposal with calls to action?
I’d be happy to.
Offline
Re: Magazine to newsletter
Destry wrote #292343:
A third crazy option that addresses the multi-lingual slant is to open it up as a multilingual “community” magazine. In other words, we don’t worry about translation, writers can submit whatever language they want and that gets published for whoever can read it, though someone should make attempts to keep languages staggered as much as possible. There should still be some editing attempts, of course (and appointed editors in the CMS for each language in that respect), but no effort at trying to unify articles to one language standard. Any respectable topic goes if it just means getting people writing. A set of categories for each language makes it easy to RSS each stream? Etc.
YES, that’s what I meant.
No traduction. Each Textpattern user can write in their own language.
Why not a “textpattern medium” ? A Textpattern user can open a account and writing article about Textpattern in his native laguage.
A chief editor (or moderator) for each language is interessting for validated content about Terms of use.
Last edited by sacripant (2015-06-30 10:37:09)
Offline
Re: Magazine to newsletter
Bloke wrote #292353:
I’m still not quite clear — on a technical, admin-side level — how it would work:
- Section per language
- Use a custom field for language designator
- Use a category
- Or a tag
and how we’d then filter that into feeds, but I’m sure someone has some ideas on how to figure out a decent workflow that ticks all the boxes.
I’ve never setup a multi-lingual site, so I’m not savvy of any constraints that might exist. Anything I proposed before is ignorant of that.
But what I had in mind requires ridding yourself of the notion that we’re going segregate content by language from top to bottom. MLP doesn’t apply here. Instead treat all articles, regardless of language, the same way, but give each language it’s own category for RSS reasons. In fact it might be the only category you use in this case. Otherwise, it’s just tags that’s making articles searchable by topic.
The last part is the tricky part, I guess. There needs to be a taxonomy for tags, with each language having it’s own translation of that taxonomy.
I don’t know. Maybe it’s not a good idea after all. I’m just a concept man, not a developer. ;)
Offline
Re: Magazine to newsletter
sacripant wrote #292360:
YES, that’s what I meant.
Great. Consider yourself the coordinator for your language.
First step: Help Bloke figure out how admin-side IA will work.
Second step: Start recruiting writers/topics in your language, and maybe write something yourself.
Weeeeee! ;)
Offline
Re: Magazine to newsletter
For me, a textpattern blog plateforme (same concept as Medium) is technically simple.
When a contributor want create a account, he choose a contribution language (a smd_user field ?) and validate terms of use.
I think with this field, it’s possible to filtering content by author / by langage, create a specific RSS by user / by language, etc.
Each author has his landing page (authors context).
Each language can have his landing page (sections context ?)
Perhaps the only difficulty is to set up a multilingual interface. But with Textpack and <txp:text /> was a good basic.
Offline