Ticket #220 (closed Defect: worksforme)

Opened 12 years ago

Last modified 9 years ago

book links at the bottom of each page in "structure"..

Reported by: Malte Owned by: Malte
Priority: Major Milestone: Release 4.8
Component: Drupal Website Version: 4.0.9
Keywords: Cc: jri
Complexity: 3 Area:


arguemnts against displaying these links again at the bottom of each page:

  • duplicate links
  • seldomly needed

Change History

comment:1 Changed 12 years ago by Malte

argument for keeping them at the bottom of each page/ resp. the pages we need them:

these links are very useful when pages are in a sequence, think of the two upcomding visual guidess for "so geht" and resp. the "users/machines manual" and in this cases..

  • they save editorial work when needed

-- when they are needed, they are needed at the bottom of the page, not at the top.

comment:2 Changed 12 years ago by jri

wouldn't it be perfect natural ...

  • to show the prev/next links if there *is* a true page sequence, e.g. in the visual guide AND
  • to hide the prev/next links if there is *no* true page sequence, e.g. the "Konzept" section's sub pages

Would this be possible?

And would it be possible to remove the "nach oben" link in any case?
I think most people would interpret it as "zum Seitenanfang" rather than as
"move up one structural level in a structure that is *not visible* here but only existent in the mind of the page author".

Last edited 12 years ago by jri (previous) (diff)

comment:3 Changed 12 years ago by irau

I agree: prev/next only make sense when there actually is a sequence. But don't we have that allready? We can decide for any number of pages if they should be a book or not. Only when combining them in book we see the book typical navigation.

The up/down navigation is less usefull I agree. However I would doubt user interpret it as "go to the Main Page".

comment:4 Changed 12 years ago by Malte

  • the _if_ approach suggested by jri would not be so easily possible, just throw some custom logic in our templates or the module, i guess.
  • the "move up" could be generally removed or renamed easily i think, should i do that? i think we can leave it or hide it everywhere, i actually don't care.

comment:5 Changed 10 years ago by jri

  • Milestone Launch Website deleted

Milestone Launch Website deleted

comment:6 Changed 9 years ago by jri

  • Status changed from new to closed
  • Resolution set to worksforme
  • Milestone set to Release 4.8
Note: See TracTickets for help on using tickets.