mantoshkumar1 / mantoshkumar1/mantoshkumar1.github.io
Recruiter readiness: publish the DogBuild website project page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
Parent
This is a bounded cross-repository deliverable under DogBuild #183. It does not complete or close the broader documentation source-of-truth program.
Deliverable
Publish the DogBuild project page and its website integration through PR #71, with evidence-backed claims, working navigation, accessibility, SEO integration, and real desktop/mobile browser coverage.
Exact candidate
- PR: #71
- Branch:
docs/dogbuild-project-entry - Reviewed head:
7653743a0f5bfeb76d164172374067ebdb6a2573 - Independent verdict: CLEAN
- Browser evidence: 40/40 passing
- Founder content decision: approved
- Current state: draft, unmerged, undeployed
Acceptance criteria
- Recruiter-facing DogBuild page and knowledge entry are complete and truthful.
- Floor and audit checks are green.
- Desktop/mobile browser suite passes 40/40 with a retained artifact.
- Independent review is CLEAN.
- Founder approves the content.
- Founder records protected-test approval through the repository's approval mechanism.
- Guard passes on the frozen exact head.
- Founder personally marks the PR ready and merges it.
- The reviewed commit is contained in
main. - Production deployment succeeds.
- Live page, navigation, links, accessibility, desktop, and mobile behavior pass smoke verification.
- Closeout evidence is recorded without claiming that parent DogBuild #183 is complete.
Authority boundary
Agents must not apply the protected-test approval label, mark PR #71 ready, enable auto-merge, merge, deploy, publish, or change its frozen head. The founder alone performs those actions.
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 PR #71 on branch docs/dogbuild-project-entry and verify the reviewed head 7653743a0f5bfeb76d164172374067ebdb6a2573 against the listed acceptance criteria. Check the retained 40/40 browser evidence, approval and guard status, then verify deployment and live desktop/mobile, navigation, links, and accessibility smoke checks. The deliverable is complete only after the founder performs the protected approval, merge, deployment, and closeout actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, javascript
- Domain
- accessibility, content, documentation, release, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100