Skip to content

Use SURF (not SURFnet) in docs and restructure README#29

Merged
sjoerdbeentjes merged 1 commit into
mainfrom
docs/surf-naming
Jun 17, 2026
Merged

Use SURF (not SURFnet) in docs and restructure README#29
sjoerdbeentjes merged 1 commit into
mainfrom
docs/surf-naming

Conversation

@sjoerdbeentjes

@sjoerdbeentjes sjoerdbeentjes commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

What

  • Replace SURFnet with SURF in descriptive text (README intro + root package.json description). SURFnet is the legacy name; the company is now SURF.
  • The @surfnet/* npm package scope and the surf-design-system repo name are left unchanged (legacy identifiers).
  • Restructure the README: both framework guides now live under a single Adding a component heading with React and Angular subsections, and the AI assistants section moves to after them.

Why

Feedback: descriptive text should use the current company name SURF, not the legacy SURFnet. Grouping the two framework guides together reads more naturally than having the AI-assistants section wedged between them.

SURFnet is the legacy name; the company is now SURF. Update the
descriptive text in the README and root package.json (the @SURFnet
npm scope and surf-design-system repo name are unchanged).

Also group both framework guides under one "Adding a component"
heading with React and Angular subsections, and move the AI
assistants section after them.
@sjoerdbeentjes sjoerdbeentjes merged commit 1c6676c into main Jun 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant