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

Markdown to HTML documentation build seems to be broken #2403

Closed
gpakosz opened this issue Nov 16, 2017 · 5 comments
Closed

Markdown to HTML documentation build seems to be broken #2403

gpakosz opened this issue Nov 16, 2017 · 5 comments

Comments

@gpakosz
Copy link

gpakosz commented Nov 16, 2017

Hello,

While studying options I noticed the documentation is hard to read.
It seems to me the source Markdown content tries to add anchors but ends up messing the output:

{#load_paths-option} `:load_paths`
: An array of filesystem paths or importers which should be searched
  for Sass templates imported with the [`@import`](#import) directive.
  These may be strings, `Pathname` objects, or subclasses of {Sass::Importers::Base}.
  This defaults to the working directory and, in Rack, Rails, or Merb,
  whatever `:template_location` is.
  The load path is also informed by {Sass.load_paths}
  and the `SASS_PATH` environment variable.

is rendered as
image

and as you can see #load_paths-option inserted as content instead of an id on the <p> element:
image

@nex3 nex3 closed this as completed in 57f195d Nov 16, 2017
@gpakosz
Copy link
Author

gpakosz commented Nov 16, 2017

Thank you

@gpakosz
Copy link
Author

gpakosz commented Jan 3, 2018

Hey @nex3 👋 It seems http://sass-lang.com/documentation wasn't updated with the fix.

image

@nex3
Copy link
Contributor

nex3 commented Jan 4, 2018

Looks like I forgot to deploy the update. Done!

@SKalt
Copy link

SKalt commented Nov 5, 2018

I'm getting this error again.

<p>## List Functions #list-functions</p>

Within the sass repo, how do you build the docs, so that I can test the error (and future fix) out?

@nex3
Copy link
Contributor

nex3 commented Nov 5, 2018

We're working on totally rewriting and revamping the docs, so rendering bugs with the old docs aren't a high priority right now.

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