reduce number of menu items #27
Comments
|
I've always found the most frustrating part of the website to be the lack of a table of contents (or something along those lines) at the top of each page. That is, not knowing what's on a page without having to scroll through the whole thing. For example, the current Citations page has "How to Cite Stan" as the header, which is fine, but there's a lot more on the page besides what is described by "How to Cite Stan". There are also books about Stan, papers using Stan, books with examples translated into Stan, etc. Reducing the number of menu items sounds good to me, but then I think it will be even more important to have a table of contents at the top of each page linked to from the menu since there will now be even more content per page (or at least more content linked to from each page). |
|
Good point. But I don't like tables of contents. It seems to
be trying to put a band aid on a problem that's more structural.
What if the pages are shorter, so that "how to cite Stan" and
"citations of Stan" are no longer on the same page? Of course,
it makes the site deeper, but perhaps easier to navigate. At least
I think that was Andrew's thinking.
- Bob
… On Dec 27, 2016, at 4:55 PM, Jonah Gabry ***@***.***> wrote:
I've always found the most frustrating part of the website to be the lack of a table of contents (or something along those lines) at the top of each page. That is, not knowing what's on a page without having to scroll through the whole thing. For example, the current Citations page has "How to Cite Stan" as the header, which is fine, but there's a lot more on the page besides what is described by "How to Cite Stan". There are also books about Stan, papers using Stan, books with examples translated into Stan, etc.
Reducing the number of menu items sounds good to me, but then I think it will be even more important to have a table of contents at the top of each page linked to from the menu since there will now be even more content per page (or at least more content linked to from each page).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Yeah I have no particular love for tables of contents, so if we can solve
the problem I described a different way that would be fine from my
perspective. More pages with less content per page is probably better than
having ToCs everywhere. As long as it's possible to know what information
the cite provides (at a high level) without actually having to scroll to
the bottom of a lot long pages it will be an improvement
…On Tue, Dec 27, 2016 at 5:09 PM Bob Carpenter ***@***.***> wrote:
Good point. But I don't like tables of acontents. It seems to
be trying to put a band aid on a problem that's more structural.
What if the pages are shorter, so that "how to cite Stan" and
"citations of Stan" are no longer on the same page? Of course,
it makes the site deeper, but perhaps easier to navigate. At least
I think that was Andrew's thinking.
- Bob
> On Dec 27, 2016, at 4:55 PM, Jonah Gabry ***@***.***>
wrote:
>
> I've always found the most frustrating part of the website to be the
lack of a table of contents (or something along those lines) at the top of
each page. That is, not knowing what's on a page without having to scroll
through the whole thing. For example, the current Citations page has "How
to Cite Stan" as the header, which is fine, but there's a lot more on the
page besides what is described by "How to Cite Stan". There are also books
about Stan, papers using Stan, books with examples translated into Stan,
etc.
>
> Reducing the number of menu items sounds good to me, but then I think it
will be even more important to have a table of contents at the top of each
page linked to from the menu since there will now be even more content per
page (or at least more content linked to from each page).
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHb4Q3zV5H2UKKsnnj-pqTlF-PZG1clCks5rMYyggaJpZM4LWZ_R>
.
|
|
@jgabry on the mailing list suggested that we not have deep nesting on a page like on the current citations and docs pages (where you have to scroll down to see what's there). One solution would be a table of contents on each page and another would be shorter (but more deeply nested) pages. |
This is from @andrewgelman, who wants to reduce the number of menu items on the top page in order to focus user search. The plan will require more clicks to get to some things but there will be fewer choices at each stage.
What should we do about the workshop pages and other "hidden" content?
Any URLs that go away should forward somewhere reasonable or be replaced with a page to manually follow.
Here's the new plan from @andrewgelman:
Home Page
As is.
Top-level Menu Items
These will be the menu choices on the home page and the targets of the menu items:
The first three will remain the same.
Community will get a landing page with links to all the previous pages:
If we can figure it out, it might make sense to have a submenu of some kind. Otherwise, each of the pages will only have the top-level menu items and it'll be a challenge as to how to lay out that community page index, as it'll require a bit of explanation for each item and some scrolling.
What we have now
Thsi is just an outline of the current site (as of this issue submission):
CAPS are menu pages. Bold items have their own web page.
HOME
INTERFACES
DOCS
ISSUES
EVENTS
COMMUNITY
CITE
TEAM
DEVELOP
SHOP
SUPPORT
We also have a hidden page that doesn't have a menu item or any links to it from the site:
Workshops
The text was updated successfully, but these errors were encountered: