I did some more monkey patching to make the site look nicer. We would still want to write our own theme. Standardise the fonts and colors a little bit.

Can I work on this?

Yes.

You should give the guidelines a read 😅 . Check this, you do not need permission to work on help wanted issues.

Got it, I'll try to have it finished by Monday

@KBB99 Let's do it together if @raisedadead is okay with it? I will read the contribution guide too :D

Sounds good @sujithnath . I'll change the fonts to match the Free Code Camp font.

@KBB99 Are you still working on the PR to change the font? If you are busy, I can take it from here.....

@raisedadead Would you like to create a new CSS file for the docsify theme or add the CSS to the already existing custom.css?

We would prefer updating the theme.css currently in the /docs/components. You are welcome to purge and tweak as per your best judgement.

Criteria:

• We want the fonts to be legible and readable using the typography from the design guide.
• Modular if posible, to be able to use dark/light mode would be nice touch.

@raisedadead any thoughts on hosting the FontAwesome fonts rather than using the kit? The kit creates a flash of unstyled content and sometimes takes a while to load.

I think I used our pro license. We sure can host it too, but I am not sure it can be bundled any better because all of this is client side.

Unless there's a licensing issue with putting pro fonts on GitHub, I think it should be okay. Rather than going render -> get kit -> re-render it would be get fonts from GitHub -> render. Everything style related should be ready before the first render.

I guess the ideal solution would be to inline the svgs, but that's both a pain and possibly not okay as far as FontAwesome are concerned.

I will check about hosting, but we are a public repo, so I think it would not be possible to host the licensed icons. We could always swap these for the free (open-source) ones and host that instead, which I am fine with.