Code Monkey home page Code Monkey logo

office-add-in-ux-design-patterns's Introduction

office-add-in-ux-design-patterns's People

Contributors

alec-mcginnis avatar cwlock avatar danielmgalan avatar davidchesnut avatar hodlhodl avatar jedunn avatar reezaali avatar rick-kirkham avatar v-chloc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

office-add-in-ux-design-patterns's Issues

Pattern File Naming Convention

Until recently the naming convention for the repo files was Category_PatternName.ext.

But the convention is not being followed anymore.
For example, FirstRun_TrialVersion.md follows the convention previously mentioned, and Notification_Inline_Message.md doesn't. It seems that Notification files are not going to follow the convention. However, Notification_MessageBanner.md does follow it.

In a different approach, Tab_Bar.md has completely dropped the category and even further separated the name of the file into two words. It looks like navigation pattern file names only use the name of the component and will not have Navigation as a category.

Now, some file names use an underscore to separate their name if it is a compounded word. Some separate the category from the pattern name with an underscore, sometimes even if the pattern name is compounded.

If navigation file names will not include their category in their file name, I think we could change all the other files to follow this convention and simplify the entire practice of naming these files. We can still be more specific in the Readme.md file if needed.

Broken links

Word desktop base template
Powerpoint desktop base template

Developer Info Placemat Pattern

A place to list information about the add-in developer.
This could include about, support, copyright and privacy statement, license agreement.

A. One variant could be similar to the pattern "Multisection". However, this placemat would be located at an earlier step in the flow. For instance, it would list the developer's info and Privacy Statement; from there the user drills down to read the Privacy Statement.

B. A second variant, could be a compact version that sits in the footer area of the taskpane.
i.e. ## Developer | About | Support

Add In Store Experience Toolkit

Hello :-)

We are currently working on an Store Template Toolkit that can help you visualize your add-in in the store. If you think that you would find this Illustrator template useful and would like us to publish it, let us know by submitting a "New Issue" item in the Issue Tracker.

I would love to see this Illustrator Template. It helps much to beeing focused on other things when going to production (the first time) :-)

Thanks and all the best !

Dan

Any major changes planned? Also, consider add-in branding at top instead of bottom

It's been a while since many of the designs were updated and I was wondering if there are any major changes planned to the design guidelines. It's important to know if development was starting on a new add-in today or if existing add-ins were to be converted to be more in line with the guidelines.

Also, could you consider a variant of the add-in design where the add-in branding is at the top instead of the bottom? The primary reason is for vertical scrolling in the add-in which, as much as we try to eliminate it, still has to happen sometimes. With the branding header at the top the add-in can implement a feature which allows it to scroll off the top so the entire task pane can be used to view the important content. With branding at the bottom, scrolling off is not an option so devs would have to either not have branding or try to auto-hide the branding "on scroll" which is a much more difficult thing to do. As a side point, to me branding at the top seems more natural anyway.

Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.