Unblock the migration of the per rail, per account, and per operator pages to the new UI library

[silent-cipher]

We are currently migrating from @filecoin-pay/ui to @filecoin-foundation/ui-filecoin.
Most pages have already been updated using a combination of both libraries because @filecoin-foundation/ui-filecoin does not yet provide all required components.

Task

Migrate the remaining three pages:

• Per Rail
• Per Account
• Per Operator

Use the already-migrated pages as references to understand:

1. Which components need to be replaced or shimmed,
2. What patterns we are using for combining the two libraries,
3. Any layout or style differences introduced by the new library.

[timfong888]

Can I get coloring on what the problem being solved is?

Is it because the FF will take over operations?

[BigLep]

@silent-cipher or @SgtPooki : can you please to why we want to do this? I'm not disagreeing, but lets answer the impact of doing this work.

[silent-cipher]

This is important to do because the current pay.filecoin.cloud deployment only includes five pages (Home, Console, Accounts, Rails, and Operators) using the new Figma UI.

In total, there are eight pages - the remaining three (Rail, Account, and Operator detail pages) weren’t completed before the BA launch due to time constraints.

This issue is mainly to track and unblock the work needed to complete those remaining pages.

[timfong888]

I'm reading two things though:

1. We are currently migrating from @filecoin-pay/ui to @filecoin-foundation/ui-filecoin. Which is a migration
2. Adding new pages. What is being added. Can I see the new Figma UI?

Context:
The reason I'm asking is I am trying to streamline parts of filecoin pay before we do additional work.

So far, if the primary persona for GA is the Protocol, the pages that enable measuring Wallet Growth and Settled, doesn't need some of these additional pages and actually needs to separate Payers from Payees.

The second use case is when an SP or the Payer wants to find their data. In the case of the Payer, Filecoin Pay is the best initial entry point but doesn't support this flow. I am working on the flow for an SP, which may bypass the need to go to Filecoin Pay if we continue to have multiple other explorers.

[timfong888]

Right now, till I get a little better coloring on impact, it doesn't seem like an M4.....

What would happen if this work were not done.

[silent-cipher]

Adding brief clarification on scope and impact.

This issue is not adding new pages or expanding scope. The Rail, Account, and Operator detail pages already existed and were previously deployed (on staging-pay.filecoin.services). They weren’t migrated to @filecoin-foundation/ui-filecoin before the BA launch due to time constraints.

The goal here is simply to complete the UI migration so all 8 pages are consistent with the new foundation UI. No new functionality or personas are being introduced.

If this work is not done:

• These detail pages remain inaccessible as well as inconsistent
• Navigation depth is incomplete
• The app stays in a partially migrated state, increasing maintenance and cleanup cost later

The current Figma set doesn’t explicitly include these pages, but this work follows patterns already used in the migrated pages rather than redefining UX.

[silent-cipher]

Attaching screenshots from the earlier staging-pay.filecoin.services deployment for reference.
These show the existing Rail, Account, and Operator detail pages, including the data and interactions they previously exposed.

These aren’t new pages, the screenshots are just to provide visibility into what existed before and what this migration is aiming to restore in the new UI.

[mirhamasala]

@silent-cipher Was discussing with @BigLep whether it would be helpful if FF UXIT takes this on?

CC: @barbaraperic

[silent-cipher]

Yes, I think it would definitely be helpful if FF UXIT team takes on this.

A couple of reasons:

• The team already has strong familiarity with @filecoin-foundation/ui-filecoin library, which would help things move faster.
• There’s currently no Figma UI, and FF UXIT should be able to effectively work around that.

The only caveat is that unfamiliarity with the existing codebase may slow things down a bit initially.
Happy to help unblock wherever needed.

[mirhamasala]

@silent-cipher We're happy to help out here! And can start migrating the components that already exist.

I did want to clarify that there is a Figma UI (see screenshot). Is that what you mean? Looking at Figma, I believe you should have access to the designs as well. The screens for these pages start here.

CC: @barbaraperic @BigLep