laywill / laywill/laywill.github.io
Landing page: copy and build
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 58
Description
Hero with name (CV-matched Raleway treatment), professional one-liner, LinkedIn CTA above the fold; proof strip (GitHub, roles, certs); toolbox icon grid; brief interests teaser. Copy rules from design-brief.md: 150–350 words, scannable, specific CTAs. Mine laywill/cv body.tex for canonical role/skill copy.
CV download links to https://github.com/laywill/CV/releases/latest/download/<asset>.pdf — confirm the release asset filename is stable.
Depends on: component library.
Acceptance criteria
- LinkedIn CTA visible without scrolling on mobile and desktop
- Body copy 150–350 words
- William reviews and approves copy
- CV link serves the latest release build
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.
Research direction
Start with docs/overhaul/design-brief.md, then inspect the component library and the landing-page entry point. Use body.tex in laywill/cv to compare canonical role and skill copy, and verify that the latest GitHub release asset matches the stated CV URL. Done means the responsive page meets the listed acceptance criteria and William approves the copy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- content, design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100