Intranet tour

A walk through what you see at https://intra.valinorinfo.com.

The homepage

One long page divided into two halves:

Tools — every JSX app on the site, as clickable cards. The badge in the corner tells you the kind:

• JSX — an interactive React app
• Draft — a preview app, not wired up yet
• Map — a visual product or product-flow diagram

Most of what you'll use lives here: Laurelin (the CRM), Company References (partnership reviews), Content Library (educational explainers), Recruiting, Dashboards, Team Calendar, Portfolio Reports, Intake.

Documentation — the docs you're reading. Same card pattern, with audience tags (Team / Engineering / All Docs).

What's not on the homepage

Everything in static/ — that's where partnership reviews live, ~125 HTML files. You don't browse them by filename; you reach them through the Company References app, which groups them by company and category, with filter pills.

A few specialty pages:

• /static/Laurelin_Roadmap_*.html — the public roadmap doc
• /static/Morpho_Stack_Reference.html and the various MorphoBlue_* files — technical architecture references
• /static/BDC_* and /static/OATFI-001_PortfolioReport_* files — IC screening memos and portfolio reports

If you find yourself navigating by URL, you're doing it wrong — the apps surface everything by topic.

Navigation patterns

• Sign in with @valinordigital.com the first time. Cloudflare Access prompts for it, then keeps you logged in. If you see "Access denied", you're using the wrong email.
• Hard-refresh when the site looks stale. ⌘⇧R (Mac) or Ctrl⇧R (Win). The deploy script runs every 5 minutes — your push is live within that window, but your browser may cache aggressively.
• Bookmark the apps you use daily. /apps/laurelin.html, /apps/dashboards.html, etc. Faster than the homepage.

How content gets here

You don't upload anything through a UI. The flow is:

1. You (or someone on the team) edits a file in the valinor-intra repo.
2. You push to main.
3. Within 5 minutes, ValinorPC pulls the change and re-renders the site.
4. You hard-refresh and see it.

This means: anything you can write to a file (a partnership review HTML, a JSX app, a markdown doc, a JSON config) can be on the intranet. Anything that needs a database lives in Laurelin instead.

Asking Claude to add something

The team uses Claude Code for the bulk of authoring. For a new partnership review:

Create a new partnership review HTML for . They are . Cover . Use an existing review in static/ as a style reference. Add to the homepage with the right categories.

See Add a partnership review for the full recipe.

For a new JSX app:

Add a new JSX app at apps/<name>.jsx that . Single file, useState only, follow the patterns in apps/data_ops.jsx.

See Add a JSX app for the rules.

The two URLs that aren't the homepage

• https://laurelin.valinorinfo.com/apps/laurelin.html — Laurelin on the dedicated CRM hostname. Same Cloudflare Access sign-in.
• https://intra.valinorinfo.com/apps/laurelin.html — same Laurelin, reached through the intranet hostname.

Same database underneath; same Laurelin. Two front doors.