Skip to content

Rewrite Introduction and add UI and agentic surfaces page#1112

Merged
bert-e merged 1 commit into
development/1.0from
improvement/introduction-vision-pages
May 21, 2026
Merged

Rewrite Introduction and add UI and agentic surfaces page#1112
bert-e merged 1 commit into
development/1.0from
improvement/introduction-vision-pages

Conversation

@Cuervino

@Cuervino Cuervino commented May 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Rewrites the Introduction page with a revised set of design principles, and adds a new "UI and agentic surfaces" page.

Introduction.mdx

  • Replaced the old generic objective section with a revised set of design principles: Affordance, Feedback, Findability, Simplicity, Predictability, Trust and transparency, Observability, Sequential flow
  • Updated Consistency (user-centric framing) and Accessibility.
  • Removed the old design principles page (content merged here)

AgenticSurfaces.mdx (new page)

  • Documents the paradigm shift happening in Q2 2026 as agentic tools enter the mainstream
  • Two sections: "The new interaction landscape" (new surfaces, autonomous systems, role of UI) and "Designed for humans and tools" (documented intent, shared body of knowledge)
  • Removes designprinciples.mdx

- Rewrite Introduction.mdx: new design principles (Affordance, Feedback,
  Findability, Simplicity, Sequential flow, Predictability, Trust and
  transparency, Observability), updated Consistency and Accessibility
- Add AgenticSurfaces.mdx: new page on the shifting interaction paradigm
  and the direction toward a machine-readable design system
- Remove designprinciples.mdx: content merged into Introduction

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@bert-e

bert-e commented May 20, 2026

Copy link
Copy Markdown
Contributor

Hello cuervino,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented May 20, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@Cuervino Cuervino requested a review from a team May 20, 2026 20:12
@Cuervino

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented May 21, 2026

Copy link
Copy Markdown
Contributor

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e

bert-e commented May 21, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/1.0

Please check the status of the associated issue None.

Goodbye cuervino.

@bert-e bert-e merged commit aef13b8 into development/1.0 May 21, 2026
6 checks 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.

4 participants