Update footer and sidebar navigation #195
No reviewers
Labels
No labels
activitypub
admin
api
articles
auth
bug
cleanup
cli
comments
compatibility
config
contacts
database
deployment
design
dev-env
docs
documentation
email
enhancement
feature
federation
feed
homepage
implementation
integration
media
openapi
priority:high
priority:low
priority:medium
proof
public-routes
public-ui
release
safety
social
sources
status:active
status:canceled
status:done
status:inprogress
status:waiting
syndication
tailwind
template
test
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit!195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/task-143d2b0d-footer-sidebar-navigation"
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?
Summary
Update footer navigation sections and sidebar ordering for feed/tag pages.
Task
Task: #task-143d2b0d
Changes
/feedstarts with Feed and/tags/{tag}starts with Tags.Testing
Verification:
npm exec --workspace @slugkit/template-site -- vitest run --config ../../vitest.config.ts src/routes/__tests__/public.test.ts src/__tests__/app.test.ts./scripts/pre-pr.shnpm run build && npm run lint && npm testChecklist
./scripts/pre-pr.shpassesPR Review
Summary: Reviewed PR #195 against task
task-143d2b0d, the PR body, diff, and Forgejo Actions run #269.Acceptance criteria:
PublicSidebar/SidebarNavigationCardsections across affected public pages./tags/{tagname}renders the Tags sidebar section before Feed.Verification:
task-143d2b0dand lists relevant changes/tests.build-lint-test, pull_request).Blocking issues: none.
Warnings: none.
Final verdict: approved. Do not merge until human merge approval.
PR Review: #195
Summary: Reviewed task
task-143d2b0d, PR body/diff after0e01d80, local targeted tests, and Forgejo Actions #270 (build-lint-test, success).Acceptance criteria:
/tags/{tagname}shows the tags section first in the sidebar.Blocking issues:
PublicSidebarfor feed content, withlinks={["articles", "sources", "tags"]}and no Feed-first section. Tag detail replaces the shared sidebar with only a singleTagCard, so/tags/{tagname}does not show a consistent sidebar with the Tags section first; it omits the other navigation sections entirely.Warnings: none.
Verification:
npm exec --workspace @slugkit/template-site -- vitest run --config ../../vitest.config.ts src/routes/__tests__/public.test.ts src/__tests__/app.test.ts(2 files, 18 tests).build-lint-test, commit0e01d80).Verdict: changes requested; do not merge until the shared sidebar/navigation ordering criteria are implemented.
Corrective PR Review: #195
Summary: Re-reviewed PR #195 after commit
0e01d80using the final human-approved sidebar/footer scope. This supersedes my earlier changes-requested sidebar note: the final scope intentionally removes public sidebars from/articles,/contacts,/sources,/sources/{id}, and/tags, keeps only/feedwith a sidebar that excludes a Feed self-card, and uses a contact-detail-style layout for/tags/{tag}.Acceptance criteria:
/feedhas a public sidebar without a Feed self-card.renderFeedContentusesPublicSidebarwithlinks={["articles", "sources", "tags"]}./articles,/contacts,/sources,/sources/{id}, and/tagshave no public sidebar.PublicSidebaris only used by feed content, and targeted tests assert the removed sidebar links are absent on affected pages./tags/{tag}uses contact-detail-style layout with the tag card in the left rail and no public sidebar. The tag detail render now uses an<aside>withTagCardand does not render feed/sidebar navigation or RSS/account cards.API DocumentationandSource Repository.Verification:
0e01d80.npm exec --workspace @slugkit/template-site -- vitest run --config ../../vitest.config.ts src/routes/__tests__/public.test.ts src/__tests__/app.test.ts(2 files, 18 tests).build-lint-teston0e01d80408.Blocking issues: none.
Warnings: none.
Verdict: approved; awaiting explicit human merge approval. Do not merge without that approval.