Templates/masters
Allow elements to be easily reused across pages.
29 comments
-
jp
commented
Any ETA on this?
-
kauthon
commented
yeah having an include file system would work well.
-
Daren John Scott
commented
Any update on this functionality? I'm having RSI (lol, no joke) having to redo every sub page when my 'master page' receives some retro-edits.
-
Robert Speer
commented
Need this feature for larger sites. I've mostly been using mockingbird for describing new features for existing sites. I've just mocked up a whole app's mvp and making changes to the global header & footer requires editing every page, which is not an effective use of my time.
-
Luke
commented
Anthony describes exactly what im looking for. i want to be able to design a "gadget" or page or component and then drag and drop it onto a canvas. now that i described it, it would be really cool if i could group something together and save that as a functioning widget that would display on my toolbar.
-
Eva
commented
I agree with Luke, Anthony, Will etc, I'd like to reuse groups of elements which will change automatically through the site when adjusting the original group. Thanks.
-
Anthony Whitaker
commented
Essentially, I would like to be able to design a Page. And then, drag & drop that Page onto the canvas, in exactly the same way we currently drop widgets. The dropped page would be uneditable... but these dropped pages should automatically update when the actual Page is updated.
Concrete example:
1) Create a page called "Login" add user/pass fields.
2) Drag the Login page from the "pages" box onto the "Home" page and position accordingly.
3) As needed, edit the Login page and preview results back on the "Home" page.If there is a way to donate, I will personally help fund this effort.
-
Anthony Whitaker
commented
I don't really need Master Pages, per se. But creating re-usable template widgets would be awesomely useful. I would like the software to easily support the work-flow for http://www.slideshare.net/Titine/user-interface-design-in-practice (starting on slide 21). If that worked, I could get my whole company would move to this mockingbird.
-
Rick
commented
Allowing a simple menu master page is kind of...essential...?
-
will123195
commented
I frequently use nav bars (and button bars and tabs). Since they are reused on various pages a template element would be great. However, for this to be useful I would need the ability to change the * selected element on each instance of the nav bar.
I imagine templates would be uneditable -- but you could still allow editing of the asterisks to change which tab has the active state.
-
luke
commented
Yep, this is needed. I'd ideally like to be able to create a library of (named) groups of elements. A library of 'sets'. This would allow enough flexibility to allow different users to create their own workflows - letting users create page templates and smaller widget templates.
-
Darwinium commented
Very very need this feature. Still mockingbird havn't this function, our company is unable to fully pass. Because of this we have to use the Axura PRO =(
-
Luke Crawford commented
Yes, I'd love a way to create my own "meta objects", basically a "named group" like someone else mentioned. It would be a collection of items that I group into one, and if I changed the "root" item all uses of it would change correspondingly. Kind of like Sketchpad back in the day. http://www.youtube.com/watch?v=mOZqRJzE8xg
-
Ben
commented
@Sheena - A master layout is good, but everyone here is talking about wireframe elements.
My thought is for "Named Groups" - in other words, group elements together and give it a name. Then, add a "Named Group" widget to the sidebar that users can drag onto the page. It initially starts as an empty container, but you can edit it to give it a name. It will use that name to look up the Named Group widget and render it. Bingo.
If you want to get really slick, make a Named Group appear directly in the widget sidebar so it can be dragged/dropped just like any native widget.
-
Vj
commented
Agreed that this is essential - on the flip side, I like the provided feature where I'm able to clone a page like *that* !
-
Kit
commented
Agreed that it is crucial to be able to duplicate the template site side such as the footer and header.
Kit -
Kitty
commented
Having the problem of clients making tiny changes that affects the WHOLE site... Example: if two items on my main navigation need to be swapped... I don't want to have to copy-paste this new navigation to ALL the slides >_<" it'd be time consuming and painful T_T
-
Sarah McAleer
commented
I copy ALL and paste to a new page. This I guess works ok for very small sites. I'm not sure if it stands up to a big site. Maybe make Masters like Indesign does. Where you drag the master over the page you want to place the template on.
-
Matt G
commented
This is the key to creating a big site wireframe -- FAST. Currently, we have to copy the pages. The problem is when we duplicate a page and then we change the original page. We need to re-copy these elements into the new page. I think we need the ability to create several different "templates" and when we update them, they update across all pages. This would be an incredible time saver.
-
Shef
commented
Here's an idea: the user creates a "widget" using primitives. Select the elements in the widget and group them. Click a menu option to save the group to the user's library of widgets. The widget can now be used like any other widget. It can also be ungrouped and edited once it's been added to a project. To modify the widget, add it to a project, ungroup it, edit, regroup, and add it back to the library.