Textpattern CMS support forum

You are not logged in. Register | Login | Help

#11 2016-09-15 15:26:09

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,021
Website

Re: Textile vs Markdown

We are absolutely 100% staying on GitHub – that is not up for debate. Seriously! It’s taken enough time to build up a steady flow of contributors and moving to Bitbucket (or wherever) will kill that dead. I certainly won’t be contributing anymore if we move off GitHub.

Anyway, they are not dropping Textile in the main GitHub site, just on Jekyll hosting (although they could quite easily decide to drop it from main site too at some point). FWIW I have changed various repo README files to Markdown because other sites that hook into GitHub (such as the NPM site) expect README’s to be in Markdown format.

I am also stripping Textile from the pophelp files that we plan to include bundled with 4.7 releases, in favour of standard HTML. That is because I don’t want (or see a reason) for them to be tied to a particular text filter.

Which leads me to a subject that is up for debate: We need Markdown to ship as a core part of Textpattern NOT a plugin. I’m happy for Textile to stay as the default setting (which you can change at install time or afterwards in preferences to Markdown if you wish). New dev users will expect that, as will more and more end users who have grown up with Markdown.

Offline

#12 2016-09-15 15:31:13

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

Re: Textile vs Markdown

philwareham wrote #301538:

We are absolutely 100% staying on GitHub

Absolutely.

Anyway, they are not dropping Textile in the main GitHub site, just on Jekyll hosting (although they could quite easily decide to drop it from main site too at some point).

And probably will unless someone stands up and says we still use it.

I have changed various repo README files to Markdown because other sites that hook into GitHub (such as the NPM site) expect README’s to be in Markdown format.

A very good reason.

I am also stripping Textile from the pophelp files that we plan to include bundled with 4.7 releases, in favour of standard HTML. That is because I don’t want (or see a reason) for them to be tied to a particular text filter.

Also fine by me.

We need Markdown to ship as a core part of Textpattern NOT a plugin.

Parsedown please. Fast.


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

#13 2016-09-15 16:01:59

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Textile vs Markdown

jakob wrote #301535:

There’s gitlab too. It’s github-like, offers unlimited private repos and also supports textile.

Yeah, the comments section of all the blogs I was reading comparing Bitbucket and GitHub had the CEO of GitLab exclaiming the virtues of his new service.

philwareham wrote #301538:

We are absolutely 100% staying on GitHub – that is not up for debate.

Never said it was, it took us a while to get off of SVN, and I was a vocal proponent of the move.

Personally, I’m not going to learn another markup language. Between Textile, BBCode and Doku code, which I’ll soon switch to Creole, I can do my work and communicate effectively.

Phil, who did you talk with at GitHub?

Offline

#14 2016-09-15 16:05:58

michaelkpate
Moderator
From: Avon Park, FL
Registered: 2004-02-24
Posts: 1,081
Website

Re: Textile vs Markdown

hcgtv wrote #301505:

If this project, that brought Textile to the world, is giving up on our creation, then the future is bleak.

I am still working on converting all of my Betamax tapes to digital to burn on HD-DVD. :)

Sometimes the best choice just doesn’t win for whatever reason.

Offline

#15 2016-09-15 16:07:40

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,021
Website

Re: Textile vs Markdown

hcgtv wrote #301540:

Phil, who did you talk with at GitHub?

History here, and related. I’d stress this is Jekyll stuff – there is no indication GitHub will drop Textile support for its main site.

Offline

#16 2016-09-15 16:15:04

michaelkpate
Moderator
From: Avon Park, FL
Registered: 2004-02-24
Posts: 1,081
Website

Re: Textile vs Markdown

philwareham wrote #301538:

Which leads me to a subject that is up for debate: We need Markdown to ship as a core part of Textpattern NOT a plugin. I’m happy for Textile to stay as the default setting (which you can change at install time or afterwards in preferences to Markdown if you wish). New dev users will expect that, as will more and more end users who have grown up with Markdown.

+1 – easy for me because I won’t be doing any of the hard part

Offline

#17 2016-09-15 16:46:40

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Textile vs Markdown

“But Dean Allen began to fade away. He wasn’t an infocide, but for several years it was as if he were on infohospice.” – Resurrecting Mark Pilgrim and Why the Lucky Stiff

Always good reads from you Michael, thanks.

So it was the f*cking Apple Fanboys that we have to thank for Markdown ;)

Offline

#18 2016-09-15 17:09:54

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Textile vs Markdown

philwareham wrote #301543:

History here, and related. I’d stress this is Jekyll stuff – there is no indication GitHub will drop Textile support for its main site.

Fuck Ben, and since he’s a lawyer, he can come sue my ass if he doesn’t like what I say or what I’m about to say, here or everywhere.

That’s no reason to remove a mature markup language, it’s all politics, plain and simple.

Looking at this from another perspective, GitHub is a great collaboration tool, way better than Google Code, now that doesn’t mean we have to go, what did Dean say Buggerballs, into it.

Offline

#19 2016-09-15 18:00:17

michaelkpate
Moderator
From: Avon Park, FL
Registered: 2004-02-24
Posts: 1,081
Website

Re: Textile vs Markdown

hcgtv wrote #301546:

Looking at this from another perspective, GitHub is a great collaboration tool, way better than Google Code, now that doesn’t mean we have to go, what did Dean say Buggerballs, into it.

Phil explained this above but I didn’t understand it at first either the last time this came up. The issue is not with Github – that supports Textile. The issue is not with Jekyll – that supports Textile. The issue is that Github Pages no longer supports Textile.

You can use Markdown instead of HTML. Markdown is simpler to read and write. – About GitHub Pages and Jekyll

There are clear advantages to maintaining the Documentation in a Git Repository at Github. Unfortunately for us, it doesn’t include Textile support but the thing you have to keep in mind: What is the best choice for the people using the Docs?

Offline

#20 2016-09-15 18:08:51

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Textile vs Markdown

jakob wrote #301535:

There’s gitlab too. It’s github-like, offers unlimited private repos and also supports textile.

Check this out, GitLab is going to create an online IDE. This is getting interesting by the minute.

Time to give GitLab a try then, at least I can see the IDE in action and glean some knowledge from it. From what I’ve been reading, anything GitLab creates will be Open Source, so their interface will be in a repository for all to see. Go GitLab! Boo GitHub, not a friend to Open Source projects :(

Offline

Board footer

Powered by FluxBB