Patrice Chalin
Patrice Chalin
> Agree about the lack of repetition but I wonder would it be useful to have something (possibly just by updating the top level README instead) explicitly telling users that...
> If npm scripts were implemented They are. To set things up one must run `npm install`, after that: - To build, run `npm run build` - To serve locally,...
@deining, you wrote: > > I prefer to avoid unnecessary repetition/duplication. The (top-level) repo README already has all the necessary information (in fact those commands could be updated to use...
This seems like a great feature to have. IMHO our current nav is too busy -- something I've been wanting to address for a while. The text labels could be...
IMHO, the best way to approach this is to hide the name using styling (this is what we've done over on the grpc.io site), using something like this: ```scss .td-navbar...
Sorry for being late to notice this issue until you (@gitautas) had already submitted a PR.
> So is the idea that the user would add this custom styling to their site? Yes, to https://github.com/google/docsy/blob/main/assets/scss/_styles_project.scss > We'd need to document it to make sure it's an...
/cc @nate-double-u @celestehorgan
Actually, if you refresh a few times you might see this syntax highlighting: > This seems to correspond to when there are 404 errors in the console, like these: ```erlang...
Good job tracking that down! Sure that makes sense. If that sort of configuration isn't possible, then maybe we can simply document that hardcoded dependency in the user guide.