I suggest you ...

Master page inheritance

Hi. I think It would be great if there is some kind of master page inheritance. For instance: I have two masters pages (A) that has some elements. Then I create another master page (B) that inherits from A and has other elements. And then a page (X) that inherits from A and another page (Z) that inherits from B. If I change any element on A it will affect master B, X, and Z. But if I change B it will only affect X.

81 votes
Vinícius Alves OyamaVinícius Alves Oyama shared this idea  · 

5 comments

  • MihkelMihkel commented  · 

    I would say that its a crucial feature if one is looking for agile prototyping tool. Right now – a dealbraker for otherwise great product

  • David Wilson commented  · 

    This would be very useful for me too! One master per page (ie. single inheritance) is the better model, but a master page should also be able to have a master.

  • Benjamin commented  · 

    +1 Agree, that is needed for complex structures.

  • tgoguillot commented  · 

    I agree. I think the same result can be obtained if you can have multiple masters on a page, not only one. Inheritance would be a plus, but alone it does not solve the problem I think.

    Example for me : main navigation is a Master, and main content layout is a Master, but I cannot use both in the same page. It's annoying, cause I'm obliged to merge one with the page to see toe full picture.

    There is a suggestion by another user to see masters as objects instead of pages, but I think it is also the same idea.

Feedback and Knowledge Base

The Community was retired in March, 2017. To send your feedback and suggestions, please visit our new Moqups Help Center.

Moqups homepage → Help Center →