Idea: auto-generate breadcrumbs based on directory tree #1410
Labels
No Label
bug
build
cgi Scripting
design
disruptive
documentation
duplicate
easy
feature-request
help wanted
javascript
priority/low
question
system-hackers
tagging
text
translations
wait/bugfix
wait/inprogress
wait/misc
wait/proofread
wontfix
xsl
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
Depends on
#1392 Indication of publication date is complicated and inconsistent
FSFE/fsfe-website
#1372 Create new overview page for activities
FSFE/fsfe-website
#1419 Directory structure cleanup
FSFE/fsfe-website
Reference: FSFE/fsfe-website#1410
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, each page has to contain an explicit line to display the breadcrumb like this:
An exception are news (and newsletters and podcasts) where the breadcrumbs are automtically generated by some hardwired XSL magic.
My idea now is whether we couldn't replace both the literal line in each file as well as the XSL magic by some smarter XSL magic which determines the breadcrumbs with this algorithm:
<h1>
header of the page to where the breadcrumb links.Advantages:
<p>
does not have to be explicitly written in the file.Disadvantages:
Please let me know what you think.
Phew, nice idea, and I agree that this might become tricky. However, if you think you can manage it, I would celebrate :)
Also, it becomes obvious that we have to tackle what you call "structural hickups". Are you aware of more of them?
And just one side-note: a file that has the same name as its directory should have the same role as an index.en.xhtml (e.g.
/activities/routers/routers.en.xhtml
)I think I'll guive it a try.
Probably there are quite some which will be solved with the activities/campaings cleanup (there is no
activities/index.html
yet), and I guess some of the directories now in git root should go below "about" (for example, "associates" and "timeline").It's probably better to fix these first. Should we discuss these things here or should I open a separate issue for each "hickup"?
Yes. Absolutely.
I would suggest to open one separate issue for all problematic cases taken together
Done: #1419