Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Repositories" Content Discussion #453

Open
jaredmorgs opened this issue Dec 22, 2015 · 3 comments
Open

"Repositories" Content Discussion #453

jaredmorgs opened this issue Dec 22, 2015 · 3 comments

Comments

@jaredmorgs
Copy link
Member

http://asciidoctor.org/docs/user-manual/#repositories is currently available to create content for.

Use this issue as a tracker for content suggestions, or feel free to provide PRs referencing this ticket to keep track of contributions.

This content is contained in https://github.com/asciidoctor/asciidoctor.org/blob/master/docs/user-manual.adoc

@jaredmorgs
Copy link
Member Author

I think we should mention here that not all repositories are equal when it comes to Asciidoctor support. For example, GitHub is pretty great, but BitBucket (Atlassian Stash) is absolutely terrible.

Can't speak for GitLab but I assume it is pretty good. I know Red Hat were using an implementation of GitLab to do all the docs migrations to Asciidoc.

@mojavelinux
Copy link
Member

mojavelinux commented Jan 1, 2016 via email

@jaredmorgs
Copy link
Member Author

Hot off the press for BitBucket Server installations today, is Asciidoctor
support
https://marketplace.atlassian.com/plugins/org.christiangalsterer.bitbucket.server.bitbucket-asciidoc-plugin/server/overview

This is a 3rd party plug-in that is not compatible with bitbucket.org
(Cloud). Only self-hosted server instances can be used at this stage.

There is another plugin under development, but not hosted on the
marketplace https://github.com/noamt/bitbucket-asciidoctor-addon

I would like to see both devs collaborate and unify, but that is out of
scope for this fix.

On Fri, 1 Jan 2016 at 14:07 Dan Allen [email protected] wrote:

Definitely. Setting some expectations here would be ideal and likely save
us a lot of support questions.


Reply to this email directly or view it on GitHub
#453 (comment)
.

Sent from Mobile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants