complete website revamp

Esri / esri-leaflet-doc

Documentation, API Reference and Samples

https://esri.github.io/esri-leaflet/

Apache License 2.0

81 stars 1.12k forks source link

complete website revamp #66

Closed jgravois closed 4 years ago

jgravois commented 8 years ago

goals:

responsive
inline API doc (maybe)
on fleek (definitely)

gavinr commented 8 years ago

:+1: on fleek :100:

rowanwins commented 8 years ago

Gday @jgravois

I'd be happy to provide a bit of assistance on this.

Did you have any thoughts on how you were going to tackle the reponsiveness, eg using some sort of framework etc?
In terms of the inline API doc do you mean utilising something like jsdoc to generate the docs?
I've got no idea what this fleek thing is other than what I can vaguely see in this repo

The responsive stuff is probably what I'm most comfortable with but I've dabbled a little with jsdoc.

Cheers Rowan

jgravois commented 8 years ago

@rowanwins Did you have any thoughts on how

i haven't dug into this yet, just logged an issue to remind myself to investigate a website rewrite at some point.

do you mean utilising something like jsdoc to generate the docs?

yes. thats definitely what i was referring to.

I've got no idea what this fleek thing is

urbandictionary.com - on fleek

rowanwins commented 8 years ago

urbandictionary.com - on fleek

We need a Google Translate function for American slang to Australian! In more positive news that reduces the requirements from 3 to 2!

I might make a start on the responsive aspect and will keep you posted.

jgravois commented 8 years ago

I might make a start on the responsive aspect and will keep you posted.

sounds good!

w/ all the head scratching i've done over ozzie/cockney rhyming slang over the years, i'm happy to try and repay the favor.

pmacMaps commented 6 years ago

Does the responsive goal relate to how some of the text breaks out of the container and requires horizontal scrolling? If so, does it also relate to the code samples, or are those okay to scroll?

jgravois commented 6 years ago

this is a 'high-level' issue, so the goal relates to any/all sub-optimal behavior on mobile devices.

@gavinr made serious progress on this front in #164, but as for what's left, the former is more irritating than the latter (to me anyway).

pmacMaps commented 5 years ago

I may have a lead on getting the tables more mobile friendly. Unfortunately I don't know the slightest SCSS/SASS, so I can't make the changes. But I think I may have zeroed in on some of the issues.

The proposed changes would need to be tested, and should only apply below a certain viewport width.

for the code.nobr elements, change white-space property to "pre-line"
there are some nobr elements. If those elements are changed to a span element, it should resolve the breaking text issues