Commitd47d0b3

committed

Update the filtering so tips work

1 parent32e1a67 commitd47d0b3Copy full SHA for d47d0b3

File tree

+13

-2

lines changed

+13

-2

lines changed

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -26,6 +26,15 @@ compile '/feed/' do`
`26`	`26`	`filter:kramdown,:toc_levels=>[2]`
`27`	`27`	`end`
`28`	`28`
	`29`	`+compile'/integrations-directory/*'do`
	`30`	`+filter:erb`
	`31`	`+filter:kramdown,:toc_levels=>[2]`
	`32`	`+filter:tip_filter`
	`33`	`+filter:colorize_syntax,`
	`34`	`+:colorizers=>{:javascript=>:rouge}`
	`35`	`+layoutitem[:layout] \|\|'integrations-directory'`
	`36`	`+end`
	`37`	`+`
`29`	`38`	`compile'/v3/*'do`
`30`	`39`	`filter:search`
`31`	`40`	`filter:erb`

Lines changed: 2 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,5 @@`
`1`	`1`	`---`
`2`	`2`	`title:Getting listed in the Integrations Directory \| GitHub API`
`3`		`-layout:integrations-directory`
`4`	`3`	`---`
`5`	`4`
`6`	`5`	`#Getting your integration listed`
`@@ -63,7 +62,9 @@ We offer two types of listings: OAuth installation listings and "learn more" lis`
`63`	`62`	`###OAuth installation listing`
`64`	`63`
`65`	`64`	`{{#tip}}`
	`65`	`+`
`66`	`66`	`This is our preferred type of listing wherever possible.`
	`67`	`+`
`67`	`68`	`{{/tip}}`
`68`	`69`
`69`	`70`	`The OAuth installation listings are used so customers can immediately install your integration directly`

Lines changed: 2 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,5 @@`
`1`	`1`	`---`
`2`	`2`	`title:Integrations Directory marketing guidelines \| GitHub API`
`3`		`-layout:integrations-directory`
`4`	`3`	`---`
`5`	`4`
`6`	`5`	`#Marketing guidelines`
`@@ -25,6 +24,7 @@ Write a single paragraph that describes your integration clearly and speaks dire`
`25`	`24`	`Keep this section short and sweet.`
`26`	`25`
`27`	`26`	`Example`
	`27`	`+`
`28`	`28`	`>Sample CI helps you deploy your code with confidence by continuously running your test suite. Avoid bugs and avert deployment disasters by catching bugs before they reach your users. Sample CI can update the build status on your pull requests as they progress and can deploy successful builds to production automatically.`
`29`	`29`
`30`	`30`	`##Images`
`@@ -50,6 +50,7 @@ List some features to give people a better sense of what your integration offers`
`50`	`50`	`- Does your feature require any setup?`
`51`	`51`
`52`	`52`	`Example`
	`53`	`+`
`53`	`54`	`>Deploy anywhere, with confidence`
`54`	`55`
`55`	`56`	`>Deploying to production after a successful build is as easy as setting up a bit of configuration, and we’ll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, CloudFoundry, AppFog, and Amazon OpsWorks.`

Comments

(0)