Looker Community

Markdown Document Navigation

Thanks for this, I have been searching around for this syntax and it isn’t anywhere online!
I am struggling setting the document to a location other than the current path (I am spreading my documentation out across the projects in which the documentation refers).
Anywhere I can do some more reading or any help greatly appreciated.

1 Like

I’ve been trying to figure this one out with the help of a few others, and I can’t find much more than you. Our docs do have this: https://docs.looker.com/data-modeling/getting-started/other-project-files#adding_a_navigation_structure_to_your_documentation which explains the use of the syntax, but don’t shed light on how to reference another project.

We are on the hunt internally, and we’ll definitely figure it out one way or the other. Stay tuned.

It looks like it’s not currently possible to reference documents from other projects— Worth opening a feature request for! I suppose you could add literal links to get there, but it won’t mesh as nicely.

I am far from even a rookie with html/css/md but something seems off. This page suggests that the css tag of “float” is ok, yet on a md document page I cant get anything to stick to either side (I am making my own navigation panel). It just puts everything into the middle of the page. I can hack it around so that it pushes it to the left by putting stuff on the right of it but this is going to mess up with different screen sizes and is far from consistent.
Anyone offer any help here?

1 Like

That docs page specifically references which parameters are allowed in the html parameters— I think the dashboard text is actually “Github Flavored Markdown”, which includes some but not all the functionality of HTML.

I wonder if markdown just doesn’t support the use of those kinds of tags? That seems unlikely to me.

Getting this some visibility from those who know just what Looker’s markdown is capable of…

Hi, any news on this one?

1 Like

I did some research but similarly couldn’t figure it out, waiting on the engineers who created our markdown implementation to get back to me. I won’t forget to update this thread.

1 Like

Any info about this, wanting to implement this dispersed home page where each team looks after their own page from their own projects but I own the central page. Cant use the navigation function the OP posted about but wishing to create my own navigation…stuck to the left side of the page.

1 Like

It looks like this page: https://docs.looker.com/dashboards/using-markdown-in-text-tiles which lists what’s allowed in text tiles, is also the reference for .md files in projects.

The following Markdown syntax is not supported in dashboard text tiles:

Images with alt text
Links with alt text
Language-specific syntax highlighting
Strikethrough using two tildes

also don’t seem to work in a .md file, which is a hint that it’s the same set of rules.

I felt lazy for just saying that. I found out what library we use to create our markdown, and while I’m not sure if that’s privileged info or not (if I find out it’s not, I can share), I discovered some secrets you may enjoy. Here’s a particularly salient one!

While markdown floating doesn’t seem to work very well, try HTML.

<div style="float: right">
stick to the right!

This was what I had tried and mentioned above, in the css style tag and float didn’t work for me on a md document page, just comes up in the middle of the page!

1 Like

Oh, weird! I wasn’t sure what syntax you’d tried.

Mine looks like this, with that syntax:

I guess it is kind of the middle of the page. There must be a margin of some kind… Is that what you’re referring to?

I tried float left (want navigation on the left). Seems float left and not trying to do anything with it results in the same alignment…middle of the page.

1 Like

Oh I get it— You want it where my x-marks-the-spot is?:

I think this must be the same sort of default margin that’s present on dashboard text tiles, which as far as I know is enforced by the pre-packaged Looker CSS and can’t be changed.

sad times, sticking navigation in the middle of the page looks bizarre, the built in md navigation this post is about is perfect apart from it has to be in the same project.

1 Like

Yeah, that would be the easiest way for sure. I’ve asked if it’d be possible to add that capability.

A post was split to a new topic: Markdown navigation not compatible with IDE folders

Hi, is there any update on this one? We’re using a .md file to produce a data dictionary, but because the default margins are so wide, it’s causing much of the text to wrap within the cells of the table. Has a way to reduce the margins in the .md file been discovered?

1 Like

@haleyb we really like this idea of being able to keep our documentation inside of our Looker repo and making it available from within Looker, rather than having to maintain and make that doc available somewhere else outside of Looker, so thanks for sharing!

However, it seems that users must have the ability to at least view LookML in order to view these documentation (.md) files - in the default Looker roles, that equates to having at least the User role.

We have some users that only have the Viewer role, meaning that it doesn’t appear they’re able to view any of these documentation files, which kind of makes using documentation here not as valuable, as not all Looker users can benefit from it.

I bring this up out of curiosity to see if (a) I’m mistaken about Viewer role users not being able to view this documentation or if (b) you or anyone else has similar documentation requirements and woes related not all of their users being able to take advantage of documentation files that live in your Looker repo and what you’ve done to get around that constraint or what you’ve done documentation-wise instead.

Perhaps @izzy could shed some light/weigh in here as well.


1 Like

I actually think I’ve answered my own question - it is possible for a Viewer user to view .md documents, via the in-app “view” URL for these types of documents, e.g.