microsoft/citadel

microsoft/citadel

Description: PM repo

Language: HTML

Stars: 0

Forks: 0

Open issues: 3

Created: 2026-06-22T06:20:10Z

Pushed: 2026-06-22T06:40:44Z

Default branch: main

Fork: no

Archived: no

README:

PM Essentials — Team Launchpad

A single-page hub for the PM team covering vibecoding, spec'ing, analysis, and decision making. Modelled after Athanor's structure.

Files

• index.html — the entire page (HTML + inline CSS, no build step needed).
• favicon.svg — optional, drop one in if you have a product mark.

Local preview

Just double-click index.html — it opens in your default browser. Or:

Start-Process index.html

Or run a tiny local server (better for testing relative paths):

cd C:\Users\madh\Documents\pm-essentials
python -m http.server 8000
# then open http://localhost:8000

Placeholders to fill in

Search the file for [PLACEHOLDER: — every spot needing real content is marked. You'll want to provide:

1. Product / team name — header, hero, footer. 2. Hero tagline — one or two lines on who this is for. 3. "Why" prose — three paragraphs explaining the problem and the value. 4. Pillar cards — for each of the 4 pillars, the actual tools / templates / agents you have. 5. "Powered by" rows — your real data sources (Kusto cluster, ADO project, dashboards, etc.). 6. Get Started links — access request URL, bootstrap script URL. 7. Contribute links — MyAccess link, repo path, contribution guide URL. 8. Learn More links — docs / wiki URL, Teams channel deep link.

Publish on GitHub Pages — restricted to Microsoft users

This requires GitHub Enterprise Cloud (which Microsoft has). The "Private Pages" feature gates the site behind GitHub auth and only org members signed into the Microsoft GitHub org can view it. That's the same setup the Athanor page uses (notice the vigilant-adventure-g45pjg1.pages.github.io random hostname — that's GitHub's auto-generated obscured URL for private Pages).

Option A — UI only (easiest)

1. Go to https://github.com/microsoft (or whichever Microsoft GH org you have access to). 2. Click New repository.

• Name: pm-essentials (or any name you want)
• Visibility: Internal (Microsoft-only) or Private (you-only) — pick Internal so your team can see it
• Initialize with a README? unchecked is fine.

3. Upload files:

• On the repo page → Add file → Upload files
• Drag index.html (and README.md) into the browser
• Commit to main.

4. Enable Pages:

• Settings → Pages
• Source: Deploy from a branch
• Branch: main / / (root)
• Save

5. Set Pages visibility to private:

• On the same Pages settings page, under Visibility, choose Private
• (This option only appears for Enterprise Cloud orgs.)

6. Wait ~60 seconds. The Pages URL appears at the top (e.g., https://.pages.github.io). Share that link — anyone signed in to the Microsoft GitHub org can open it; anyone else hits an auth wall.

Option B — via gh CLI (faster if you have it set up)

cd C:\Users\madh\Documents\pm-essentials

# 1. Auth (one time)
gh auth login

# 2. Create the repo in the Microsoft org as INTERNAL
gh repo create microsoft/pm-essentials --internal --source=. --remote=origin --push
# (or use whichever org name you have access to)

# 3. Enable Pages on the main branch
gh api -X POST /repos/microsoft/pm-essentials/pages `
-f source.branch=main `
-f source.path=/

# 4. Set Pages visibility to private (Enterprise Cloud feature)
gh api -X PUT /repos/microsoft/pm-essentials/pages `
-f visibility=private

# 5. Check the deployed URL
gh api /repos/microsoft/pm-essentials/pages --jq '.html_url'

Custom URL (optional)

Microsoft's aka.ms lets you create vanity short links:

1. Open https://aka.ms/managealiases 2. Add an alias like aka.ms/pm-essentials → pointing at your Pages URL. 3. Share aka.ms/pm-essentials instead of the random Pages URL.

Updating the page

Just edit index.html, commit, push. Pages rebuilds in ~30–60 seconds.

git add index.html
git commit -m "Update pillar cards"
git push

Troubleshooting

• 404 after enabling Pages — wait 60 seconds, sometimes 2 minutes on first publish.
• Page loads as plain text — make sure the file is named index.html exactly (lowercase) and is at the repo root, not in a subfolder.
• No "Private" visibility option — the org isn't on GitHub Enterprise Cloud, or Private Pages isn't enabled for that org. Talk to the org admin, or set the repo itself to Internal so only org members can clone — they'll still see the Pages site if it's set to "Public" within the private repo (this is the older model).
• Auth redirect loop — sign out of github.com fully, sign back in with your @microsoft.com linked GitHub account.