v1: index.html has no Contact button; the other 12 nav pages do
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Compare index.html with the 12 other pages that contain the Contact button, focusing on the landing-page banner and the #footer target. Review the context from #72, then ask maintainers whether index.html should gain a Contact affordance or remain bespoke. Done means the decision is recorded and the page is either updated accordingly or closed as working as designed.
Written by the indexing model from the issue text.
Description
Observation
12 of the site's pages carry a Contact button in their nav section:
<li><a href="#footer" class="button special wide smooth-scroll">Contact</a></li>
index.html does not. Its banner offers a single action instead — Welcome jumping to #first (index.html:38).
This may well be intentional
There is a good reason for the difference: index.html is the landing page, its layout is a full-screen banner rather than the inner-page nav block, and the "Get in touch" footer is already on the same page a short scroll away. The other 12 pages use a shared nav pattern that index.html simply does not use.
So this is a question, not a defect — no behaviour is broken and nothing 404s.
The decision worth recording
If the intent is "every page offers a jump to Contact", index.html is the one gap and should get an equivalent affordance somewhere in its banner or nav. If the intent is "the landing page has its own bespoke call to action", then it is already correct and this should be closed as working-as-designed.
Worth deciding explicitly rather than leaving it as an accident of two different templates, particularly since #72 has just made the #footer anchor resolve uniformly across all 15 pages — the target now exists everywhere, so linking to it from index.html would work if wanted.
Found during review of #72; out of scope for that PR, which only moved the footer and normalised its id.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 58
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from laywill/laywill.github.io
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
laywill/laywill.github.io#186 ·
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
laywill/laywill.github.io#183 · 1 comment ·
-
Difficulty 2/5 Half a day Newbie friendliness 74/100
laywill/laywill.github.io#135 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
laywill/laywill.github.io#106 ·
-
infra needs-william
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
laywill/laywill.github.io#35 · 1 comment ·
All issues in laywill/laywill.github.io
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·