It's frustrating to be stuck with the stock gitbook styles when paying for a premium product.
For people interested in changing the font used by GitBook:
Are you using a public font hosted on Google Font or Typekit (Adobe Fonts) ?
Are you using a custom made font ? If yes, is this font hosted on Typekit ?
@Samy Pessé: We are using Nunito Sans, which is a public font hosted on Google Font.
@Samy Pessé: I'd be interested in the ability to use custom made fonts, hosted independently (not on Typekit etc.).
@Samy Pessé: We use a custom font downloaded from fonts.com
@Samy Pessé: Also using Google Fonts here (Open Sans and Merriweather).
We used custom css to support RTL languages by making the layout RTL. Please provide this feature in case you are not going to support custom css anymore.
Disappointed to see that four months later GitBook is still not providing such a fundamental feature needed to make GitBooks client facing.
We're considering using Gitbook for a range of services with a big client, but lacking this feature is looking like the only hard blocker.
Here's some suggestions, most of which are pretty restrained in scope but would be incredibly valuable:
- Custom fonts: from a technical implementation perspective its probably pretty easy to let users just pick something from Google Fonts, but more sophisticated support would probably be appreciated by companies that want a truly branded experience (i.e. remote web fonts/Typekit/etc.). Allowing for different body & heading fonts would be nice as well.
- Let users adjust text styling (e.g. bold/italic/underline) for links. One of our brand colors is black... but currently, setting the accent color to black makes links indistinguishable from normal text!
- A few more colouring options, like being able to choose the color for the left-hand navigation background or even the main page background (for a night-mode effect).
- There should be an option to hide the Gitbook stamp in the bottom left. For a product with a fairly premium price point, not having an option to hide this is pretty cheeky.
@Tom McCarthy: Yes to all of those. I don't need massive CSS customization, just some colour, text alignment, and text size adjustments. That's all I ask for.
We use very simple css to customize themed instruction check lists, adding vertical space, as well as using icon fonts (font awesome and octicons). Images sent to @Gabin
Custom CSS is a critical feature for me. I have no way of customising the branding, remove page elements that don't make sense for my personal use case, etc.
I would second this. In fact, I might not use Gitbook at all if I can't customize the CSS.
I use various systems altogether for my website (Craft CMS, UserEcho, Unbounce, etc.) and CSS customization in each of these allows me to establish a constant branding (font, colors, etc.), but also a more consistent navigation that allows users to jump from one another.
For example, my sidebar looks like the attached image in all of my different services. I see no way of even coming close to that with the built-in branding options of the v2, whereas it would have been possible with v1.
I understand the issue of maintainability, but this is a burden that is only optionally placed on the users, *if* they want to invest the time and effort to style their book further (and maintain that). This feature could come with a clear warning that future versions are not guaranteed to respect the same DOM model or base style sheet.
We are planning on adding more customization (fonts, colors, layout, etc.). But custom CSS doesn't look to us as a maintainable solution, it'll make it impossible for us to correctly improve the UI without conflicting with a large variety of custom CSS added by the teams.
What are the elements of the design you'd like to change ?
It'd be awesome to get a mockup from one of your designer of what you'd like to customize in the UI. It'll help us understand what customizations should be added.
Dropdowns in nav bar
The ability to remove target=_blank from external links
Remove Gitbook branding in the sidebar
Allow/assign hidden internal comments on public pages
Assign reviewers to changes
Suggestion/feedback box on pages
GitHub issue sync
Next and prevs ctas on pages
Custom fonts (all google fonts would be a great)
Custom syntax highlighting (we have our own realm branded style with our exsisting docs
CTA button color and size selection. All our buttons are forced to be text links today
Better lg-md-sm image resizing. Some of our portrait phone screenshots don't need to be full width.
Here are some things in ranked order that would be great as options. Sorry for the slow reply! I sent these to @Aaron O'Mullan a while ago.
@Samy Pessé: Oh my god. I don't use gitbook anymore. Your decision is too stuck!
@Samy Pessé: Would that be a bad idea if custom CSS were implemented in the spirit of “you can add your code, but it's your responsibility to make it work”?
That's how Semplice (https://semplice.com) decided to approach that very same problem. Custom code is very common there, yet no additional burden is created for the development team.