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

Migrate docs.bazel.build to use GitHub Flavored Markdown instead of Kramdown #11451

Closed
Wyverald opened this issue May 20, 2020 · 1 comment
Closed

Comments

@Wyverald
Copy link
Member

GFM supports some very useful extensions (such as markdown tables, autolinks, etc), is more widely used and well documented.

This would unblock some other improvements such as #11428.

@aiuto
Copy link
Contributor

aiuto commented May 21, 2020

@floriographygoth Does this make sense w.r.t other overhaul plans?

bazel-io pushed a commit that referenced this issue Jun 2, 2020
…ramdown, attempt #2

Rollforward after redirect pages have been fixed by 565f774. Fixes #11451

RELNOTES:
PiperOrigin-RevId: 314288440
bazel-io pushed a commit that referenced this issue Jun 2, 2020
*** Reason for rollback ***

Still broken: https://docs.bazel.build/versions/3.2.0/index.html

*** Original change description ***

Migrate docs.bazel.build to use GitHub Flavored Markdown instead of Kramdown, attempt #2

Rollforward after redirect pages have been fixed by 565f774. Fixes #11451

RELNOTES:
PiperOrigin-RevId: 314304669
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