-
Notifications
You must be signed in to change notification settings - Fork 11
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
Spike sassdocs integration #1
Spike sassdocs integration #1
Conversation
<% end %> | ||
|
||
<% if doc.example %> | ||
#### Example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like how the markdown needs to be indented differently to the rest of the file for it to render properly, makes it hard to read...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So good to see this in the TDT! Awesome work Nick. |
@m-green done |
Source code links should be permalinked to the specific version being deployed |
If we updated tech docs gem to allow https://github.com/alphagov/tech-docs-gem/blob/master/lib/govuk_tech_docs.rb#L43-L51 Edit: even if this is enabled markdown will not render, so i guess we should avoid this. |
…vuk-frontend-docs into spike-sassdocs-integration
There's a fair bit of complexity in the render view logic which would be nice to simplify but this is hopefully a good proof of concept for us to talk about.