GitHub access, About, and topics
GitHub search ranks the repository name, About description, topics, and README. About, topics, homepage, and the social preview are not stored in Git. Keep them aligned with package.json keywords and the root README lead.
This repository is currently private. Topics and About still help collaborators search GitHub; they do not surface the repo in public search until it is public.
Repository About and topics
| Field | Intended value |
|---|---|
| About | Nx + Nuxt 4 SSR portfolio with SQLite, Docker/Postgres, and AWS SAM (Lambda, DynamoDB, CloudFront). |
| Website | https://likwidmack.com |
| Docs (Pages) | https://tamaramack.github.io/portfolio/ |
| Topics | nuxt, vue, typescript, nx, ssr, nitro, aws-lambda, dynamodb, cloudfront, docker, sqlite, postgresql, serverless, portfolio |
Social preview: upload .github/social-preview.png (1280×640, under 1 MB) in Settings → General → Social preview. GitHub has no API for this step. Private repos only show the image after that upload; public unfurls require a public repository.
Apply or verify with the GitHub CLI as tamaramack:
gh auth status --hostname github.com
gh repo edit tamaramack/portfolio --description "Nx + Nuxt 4 SSR portfolio with SQLite, Docker/Postgres, and AWS SAM (Lambda, DynamoDB, CloudFront)." --homepage "https://likwidmack.com"
gh repo edit tamaramack/portfolio --add-topic nuxt --add-topic vue --add-topic typescript --add-topic nx --add-topic ssr --add-topic nitro --add-topic aws-lambda --add-topic dynamodb --add-topic cloudfront --add-topic docker --add-topic sqlite --add-topic postgresql --add-topic serverless --add-topic portfolio
gh repo view tamaramack/portfolio --json description,homepageUrl,repositoryTopics
Do not use filler topics (hacktoberfest, year tags, seo). Do not rename the repository; portfolio is the brand slug and discovery comes from About, topics, and the README lead.
Lockstep check: node --test scripts/github-search-seo.test.mjs (also in CI deployable-gate tests).
Enable GitHub Pages from Settings → Pages → GitHub Actions (workflow .github/workflows/pages.yml). Pages source is docs/ (see docs/_config.yml). The github-pages environment must allow deployment branches development and main — npm run gh:setup-environments adds any that are missing. If main is omitted, a squash-merge to main builds the site then fails the deploy job in about a second with empty logs.
GitHub CLI account
Multiple GitHub CLI accounts can coexist. Check the active account before repository API writes:
gh auth status --hostname github.com
gh auth switch --hostname github.com --user tamaramack
Related: CI/CD (environments, OIDC, rulesets), contributing.