These are chat archives for ractivejs/ractive

13th
May 2017
Joseph
@fskreuz
May 13 2017 04:04
API, Extend and Integrations sections are now merged to one file each. The rest will take a while to reorganize and merge, but that's a start.
Bob Schellink
@sabob
May 13 2017 18:10
I like it already. The api is fairly big, but most of it is snippets. Not sure what others think? During this change the sidebar became "relative". (Previously it was "fixed" and had an explicit width). Was this change intentional?
Joseph
@fskreuz
May 13 2017 18:23
The static menu was intentional. Sort of never liked fixed menus, too much scrollbar action. I can change it back tho.
The API is big. That's Ractive for you :wink: Much of Ractive was never really exposed in the old docs. The new docs aims to put them up front. Most of the questions I see on Stack Overflow and Github are almost always about the user not being aware that some built-in feature exists that could have helped them.
Also sort of justifies why it's 200KB in size. Eeeverything you can think of is there. And we're still missing a few props/methods in the docs even.
Chris Reeves
@evs-chris
May 13 2017 18:40
I did get the scroll spy thing working again 😀
Joseph
@fskreuz
May 13 2017 18:41
:scream: oh noes.
Oh, I didn't break the scrollspy (phew), but the menu just doesn't stick anymore.
Bob Schellink
@sabob
May 13 2017 18:51
Fixed menu is probably a must. Otherwise one has to scroll all the way back to the top and back down :)
Bob Schellink
@sabob
May 13 2017 18:56
We can also style the nav menu scrollbar (similar to gitter) if folk find scrollbars ugly.
Joseph
@fskreuz
May 13 2017 18:58
For the top nav, I'm aiming for single-level. No dropdown on desktop, no scroll on mobile. Still thinking how to go about it tho.
Bob Schellink
@sabob
May 13 2017 18:59
Ah, make sense.
Joseph
@fskreuz
May 13 2017 19:00
Like how can you get away with a very simple layout without losing sight of all that information.
Bob Schellink
@sabob
May 13 2017 19:11
Do devs read technical docs on small screens? Maybe... Since API is alphabetic we could place a small (fixed) vertical alphabet on the side which jumps to the topmost Api starting with that letter. How to make that work with MKDocs is another matter though.