Screen layouts that appear multiple times in my app have are cumbersome to create and maintain

Feature Requests
1

My social app has several standard screen layouts: profile, group details, place details, event details, etc.

These layouts appear in multiple places throughout my app so I have to re-create them each time. For example, if I decide to change the layout of my user profile page, I have to hunt around my app to find all the places where this exists -

Is this a problem for anyone else?

pete

2

It has 7 whole votes. :weary:

3

Now 8 :wink:

Well, good to know someone else feels my pain!

4

My similar feature request “Save layouts as templates” can be found here:

5

An option I see could help us a lot and working these days I realized it was to copy and paste more than one component as today we can only duplicate in the same screen

6

Sorry I missed that and it’s from back in Feb!

7

Not sure I understand what you are sayin’

8

Webflow calls these symbols. You create a component and then save it as a symbol and it’s available to place elsewhere.

9

Imagine we could select and copy all the componets I have in one screen, and paste in another we need those components too

10

And Glide columns in the editor! Copying and pasting of everything everywhere is really what’s needed!

11

Holy yes!

12

@Deena For all the apps, or when you create you can just use in that one?

13

Across projects! :grin:

https://webflow.com/feature/copy-and-paste-between-projects#:~:text=Great%20news!,re%20moving%20elements%20between%20projects.

Lucas_Pires 14

1 Like
15

1.) YES
2.) The reason this hasn’t been implemented yet is probably because components are tied to sheet columns. So if you copy components in one tab and paste them in a tab doesn’t have the same sheet columns, Glide wouldn’t know how to reconcile the data. Just my guess.

16
  1. very true but what if… Just the component types were copied and then if the column name matches the new destination, it gets inserted. If it doesn’t, you get the little ? in the component label — flagging that there wasn’t a matching column.
17

Also my guess

18

I wouldn’t mind, all we would need to do is
set the new column in this new table/screen :grin:

19

Oh gotcha. Copy and past would be helpful for sure. But it doesn’t solve the maintenance problem so I would prefer to have the concept of screen templates.

20

Fair

Like @Deena said