List of Pipelines

Now that the concept of pipelines is clear and the form for creating them is done, it's time to display them.

This lesson takes a look at how Fedica currently presents the list of pipelines. While the layout technically works, it doesn’t fully reflect the nature of the content. Pipelines include connected social accounts, publishing logic, and other metadata — and that kind of information doesn’t always fit neatly into rows and columns.

Instead of forcing everything into a dense table, a more flexible layout is explored — one that highlights only the essentials: type, frequency, accounts, and actions. Easier to scan, easier to manage, and better suited to how publishing actually happens.

The current layout in Fedica

Fedica displays pipelines in a basic table. On the surface, it looks familiar — each row shows key details like name, status, and links. But the structure doesn’t quite reflect the type of data being shown.

That’s not a problem with tables in general — it’s just a mismatch between format and content. Pipelines contain a mix of light and heavy data: a short name, a status label, and then suddenly a row of social account icons.

This creates an unbalanced layout. On wide screens, the table stretches horizontally, but most columns stay nearly empty — except for one overloaded cell. Visually, it feels disconnected. Structurally, it’s hard to scale.

A card-based layout works better

The redesign switches from a rigid table to a card-based view. Each pipeline is shown as a self-contained unit, where related information is grouped visually — not stretched across disconnected columns.

Cards make it easier to surface the key attributes: pipeline name, type, associated time slot, number of posts per day, and whether reposts are enabled. There's also a direct link to view posts within the pipeline, and actions like edit or delete are tucked into a simple menu.

This structure is not only easier to scan — it’s more responsive. On smaller screens, cards naturally stack. On wider layouts, they remain balanced.

Special case: the default pipeline

Fedica includes a default pipeline that cannot be deleted — only edited. It’s always present, and its type is locked to automatic posting.

This behavior is kept, but the current design still needs a small improvement. In the three-dots menu, the delete option will appear but remain disabled, along with a short explanation: this pipeline is required as the fallback and cannot be removed.

Making this explicit helps avoid confusion and gives users confidence that nothing is broken — it’s just part of how the system works.