http://textileit.com/ leads to 404 page

[mblayman]

@netcarver, I wasn't sure where else to file this, but the textile organization page has http://textileit.com/ as the URL. That URL leads to a page that only gives 404 messages.

[netcarver]

Hello Matt, yes, I grabbed that domain a couple of years back to reserve it for possible future use by the textile organisation. I've can't invest any more time in it (and front-end design isn't my speciality anyway) so I'm waiting for people to pick up on the 404 and make suggestions or contribute towards getting something up there.

I've only one criteria for that domain: that it doesn't become fixated on any particular implementation of textile - be it Ruby, PHP, Python or another - but that it promotes textile across all its implementations.

I know @gocom has been working on a textile site and he's most welcome to use the textileit.com domain for it if it fits the criteria above.

[mblayman]

http://txstyle.org/ is slightly PHP specific. I see your point about generic Textile info and I think that is a noble goal. Since a purely language agnostic does not seem to exist, what do you think about redirecting http://textileit.com/ to http://txstyle.org in the interim? http://txstyle.org looks to be about 90% agnostic and it sure beats a 404 page in my opinion, especially if http://textileit.com/ is the primary link for the Textile organization on GitHub.

[gocom]

TxStyle.org has no official affiliation with us. It's not the projects' home page and we don't operate the site. It's run by few Textpattern community members and is, indirectly, linked in Textpattern CMS admin panel as reference manual for Textile.

We link to it because it's a working Textile reference. But we can't promise the site's safety. I've never seen its source code, nor we know who has access to its data.

[netcarver]

@mblayman, yes, it would be good to have something there. Whilst I'm happy for whatever goes there to have a demo page using a particular implementation, the site should promote textile in an implementation agnostic way and link to as many other implementations as possible (which is what I meant when I said 'fixated'.)

@gocom, what's the status of your textile site? I've not seen what it looks like yet.

BTW, The author of TxStyle was good enough to zip up and send me the files for his site so we could host it ourselves if we chose to go down that route.

[philwareham]

TxStyle.org is only linked to Textpattern in lieu of an Textile official site - if an official one gets created at some point in the future, we'll of course repoint the link to it.

[eliph]

TxStyle.org was created about two years ago to fill a then existing gap in documentation. I would be happy to donate it to the community. It generated 219122 page views in May and 197228 page views in April 2014. This underlines the need for such a documentation site.

[gocom]

@netcarver The site is for PHP-Textile, and all the code is in this repository.

[eliph]

@gocom I could extract TxStyle's Textpattern articles and code, and publish it on GitHub, if I knew of a tool, such as a Textpattern plugin, that would allow the dumping of an existing Textpattern site for this purpose. Is this doable? Or even synchronize a Textpattern site with GitHub, in both directions? This would allow for a community development then, since no one seems to be inclined to overtake the documentation project.

[gocom]

@eliph Not really doable with Textpattern, nor is there a reason to use Textpattern when the content itself consists of real files. First thing you would have to do is to migrate from Textpattern to something else better suited; for example to a static site generator, Sculpin.

[eliph]

This is an interesting perspective. However, in my opinion, a documentation site should go beyond syntax documentation, and include advice that is related to the use of Textile, for example on the interplay of Textile and CSS, like in the use of CSS for alignment of images. Also, questions on installation could be covered. And for this purpose, a CMS like Textpattern would be well suited.

[jdlx]

my2¢: i would keep it as simple and maintainable as possible.. like not bother with frontend at all, not use a CMS, rely on a "anyone can handle" service for content creation and editing.. e.g.:

• Bootstrap (or alike framework) for the frontend.. (some mixins where needed)
• a dedicated Github wiki for the site's content..

The content could be pulled on a daily basis (or even triggered), and outputted via either a native gollum (readonly), some php wrapper, or something alike.. whatever'd be the least hustle..

[eliph]

Actually, yes. For a markup language, a compact, side-by-side presentation of its elements is good, and also this is what 95% of users are looking for, including me when I am lost how to disable Textile in line, for example. The "Textile Cookbook" https://github.com/textile/textile-doc-server does just that, has a nice design, and dynamically serves formatted documentation from the Textile specification. Of course, this is the Ruby flavour of Textile, but it overlaps in 98% with PHP Textile. Perhaps a transformation of this Textile Cookbook into a Github site is all that would be needed for an official documentation, in addition to a more in-depth information site on PHP Textile that already exists.

[jdlx]

dang.. there's a prob with the Github wiki idea i had forgotten: Github's textile parsing.. it's different from php-textile and craps out quite a bit.. example: i put together a cheatsheet derived from php-textile's class comments.. this is what it looks like parsed with php-textile, and this how the github parser butchers it..

[wion]

@philwareham,

Maybe this is a closed issue?

Do you have a URL in mind for this initiative?

[philwareham]

@wion the txstyle site was handed to me to update (which I’m doing gradually) although I’m keeping the install as Textpattern just for simplicity - it works and is good enough. We are going to host on the Digital Ocean Textpattern servers so I can use that domain name or something else. Probably keep it though to avoid link rot. Should be ready in a couple of weeks unless real work gets in the way.

[wion]

@philwareham,

Thanks for the update.

[philwareham]

Actually thinking about this further I’ll likeky get a new domain and then domain forward the txstyle.org name to it. Got one in mind that would be more suitable.

[philwareham]

The main issue of this topic (404 in organisation url) is fixed and I’ll amend again when new site is live. So closing.

[wion]

I won't reopen the thread, but just to reiterate what I posted in the forum...

Actually thinking about this further I’ll likeky get a new domain and then domain forward the txstyle.org name to it. Got one in mind that would be more suitable.

Depends what the scope of focus of the site is...

If scope is php-textile in general, I don't know, probably something like php-textile.net, or whatever.

But if it's txp-textile specifically, as I presume, then the obvious direction as far as I see it is textile.textpattern.com. This matches the architecture the project is headed toward anyway, so makes sense to stay true across the board, and you don't have to buy an extra domain this way.

Taking the idea further, by anticipating the potential of markup testers for txp-markdown, txp-textup, whatever, you could have filters.textpattern.com, then provide for each one:

• filters.textpattern.com/textile
• filters.textpattern.com/textup
• etc.

Maybe a little more work on the latter tack, but greater traffic and link juice in the long run, thus more exposure to the project.

Two good factors to weight for this choice, though. First, I think people who would want to use Markdown, already know how, so that filter tester probably isn't important, in fact, and, well Textile is better anyway. ;) But, if Bloke eventually does tackle creating Textup some day, which would really make it a new Textpattern project filter, then this choice would be strong, even without Markdown in the picture. Conversely, if he doesn't ever want to, then the choice is easily made for textile.textpattern.com

[philwareham]

@wion from my understanding it'd be a site to show the syntax and how to use it, regardless of underlying language (although, yes, it runs txp-textile/php-textile as its engine).

Sure, if I was building a new site from scratch I'd maybe use a different web page generator (indeed, I used Jekyll/GitHub Pages for the Textpattern documentation site, so pages can be hosted, edited and collaborated on directly within GitHub) but I haven't got much time to spare on this and the txstyle.org site works well for what it is intended. Besides, since Jekyll has dropped redcloth and GitHub Pages doesn't allow you to run your own Ruby gems (although we could use a JS solution), it would be a disservice to Textile IMO to have its site running Markdown pages throughout.

I have a general 'textile-...' domain in mind that envelopes the project as a whole.