On Tue, Mar 26, 2019 at 6:12 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Hash: SHA256
> Konstantin,
> On 3/25/19 17:41, Konstantin Kolinko wrote:
> > My main concern is that the documentation is printable and is easy
> > to use as a reference document.
> >
> > 1) Not being able to print is a show-stopper. (Really.) Anything
> > else is just a personal preference.
> @media print {
>   ...
> }
> Ought to be able to handle any changes required for print media. The
> menus never have to print. Never. Because they will never be navigable
> on paper. So they can just be removed. Horizontal, vertical, 3D,
> zooming, it doesn't matter. Just remove them when then are printed and
> it's not an issue.
> The main body of the content is still a wall of text from top to
> bottom. That should render just fine on a printer on in PDF.

Right.  We can fix the printing and it can be rendered differently from the
screen as Chris pointed out, so that's definitely fixable.  I absolutely
agree that Print is an important function.

> > 2) Left-side menu allows to navigate to a needed page with a
> > single click. I really like this feature of this menu.
> Unless you scroll too far down the page. I've always been irritated
> about this "feature" of the Tomcat documentation. Once you scroll away
> from the menu, it's no longer "one click away". So if it could "stick"
> to the top of the window (horizontal) or never scroll completely off
> the top of the page, that would be a nice improvement.

The current proposal has a sticky navbar at the top so that is already
implemented, unless I misunderstood something.

> >> It utilizes the Bootstrap 4 framework and is very trendy.
> >
> > One announcement that made a big impression for me in year 2018 was
> > this one: https://twitter.com/mislav/status/1022058279000842240
> > "We’re finally finished removing jQuery from http://GitHub.com
> > frontend" [...]
> IMO we should avoid javascript at all costs. Almost everything worth
> doing can currently be done with CSS.
> Bootstrap can use jQuery, but it doesn't have to.

We can replace jQuery with newer JavaScript constructs as browsers nowadays
conform to standards much better than they did a decade ago.  jQuery simply
makes it easier to develop.

I'm not sure that we want to avoid JS altogether though.  For example, the
font-size widget that I added relies on JS.  The current site also has some
JS code.

> > Regarding concerns raised in a subsequent thread on this topic
> > "Tomcat Website Redesign" thread
> > https://www.mail-archive.com/dev@tomcat.apache.org/msg132281.html
> >
> >> a) Do nothing, i.e. keep the website as-is [1] for now
> >>
> >> [...] IMO option (a) is not good because the site is very
> >> outdated and not mobile friendly.  Many users nowadays view sites
> >> on their phones and/or tablets, which a modern design can
> >> address.
> >
> > The current site was redesigned several years ago. (See the log
> > history of "/xdocs/stylesheets/tomcat-site.xsl" file)  I think it
> > should be mobile-friendly.
> >
> > What are the specific issues?
> >
> > Is it possible to make changes in small incremental reversible
> > steps?
> IMO, this *was* fairly incremental.

IMO as well.  The first update was done a while ago when I made the navbar
on the left "responsive" for the current site.  We can continue the
incremental way only if stick to a vertical navbar.  The horizontal navbar
requires too many changes to the structure of the HTML.

The problem with going the incremental way, though, is that it continues as
a patch work so it creates inefficient spaghetti code which is much harder
to refactor since we don't have the tooling that Java provides, for example.


Reply via email to