Guidelines on using hyphenation in interactive design

It’s a well established recommendation for publications containing masses of continuous text to use hyphenation.

Are there any ideas or guidelines on how hyphenation should be (not) used on interactive elements of UI or those that do not represent part of text content? For example, when designing 1) a menu 2) sitemap 3) sidebar etc.

The search didn’t give me anything on this subject. I think mainly of web interfaces here but it may be interesting how this may be applied to app design too.

when using material design guidelines do you use exact heights for sections?

My question is if everything is suppose to be in 4px or 8px increments does that mean even the height of sections or containers? For instance if you wanted to have a section that filled the viewport you would set that section to 100vh. However that would break the baseline grid. I’m just confused because some of the guidelines seem to be counterproductive to responsive design. For instance setting an exact container / section height would mean resizing them all at specific breakpoints.

Guidelines to make Windows Server 2008 Common Criteria Installation

I’m new to certification arguments. I have an issue with a requirement that is to make an application in a certified Windows 2008 environment.

What are / where can I find a guide to WS2008 CC-compliant setup: which features can I safely install and which I shouldn’t (so I have a system on which I could do some tests and ‘touch’ the features available).

Are there any guidelines or best practices for the design of multi-monitor systems?

By multi-monitor I mean systems which arrive out of the box with several physical monitors, each with predefined functionality. These are usually industrial systems running their own software.

This type of systems raises interesting questions, such as – do we duplicate important stuff on all the screens? Do we gray out all screens to display a modal dialog on one of them? Do we create a hierarchy of screen “importance” or are they equal? Etc.

There is some research on this from the ergonomics perspective but I’m looking for more of a UX-oriented work.

Are there any guidelines in place governing the extent to which magic items can resize to different-sized users?

Are there any guidelines in place governing the extent to which magic items can resize to different-sized users?

The description given under “Wearing and Wielding Items” (DMG, p. 140) says:

In most cases, a magic item that’s meant to be worn can fit a creature regardless of size or build. Many magic garments are made to be easily adjustable, or they magically adjust themselves to the wearer. Rare exceptions exist. If the story suggests a good reason for an item to fit only creatures of a certain size or shape, you can rule that it doesn’t adjust.

Going by this, it’s possible that upon the party defeating a fire giant wielding a magical greatsword, the halfling in the party could go touch the massive weapon, and it would shrink down to the size of a regular sword within seconds, given that there are no stated limits. I know that a DM can decide the extent to which this can happen to fit his/her own game, but is there any standard or given ‘Rules as Intended’ governing how this should be handled?

Secure coding standards and guidelines

I was trying to research on available secure coding guidelines of server-side and client-side languages.

There are online documentation from Oracle for Java, Microsoft for asp.net, and w3 for html5 to name a few. THere were also third wender guidelines from SEI, Veracode etc

Question:

For secure coding should non-vendor documentation like Veracode needs to be followed?

will the parent vendor documentation (like Oracle, Microsoft, etc) lacks any security guideliness from third vendor publications like veracode.?

Does all scripts/programming languages has secure coding guidelines available? is it mandatory

Guidelines for developing search engine

I’ve been asked to research the redevelopment of a university search engine. The existing search engine looks for students and how much funding they have through by way of a grant.

The existing search engine is an expert system that has about 40 fields. Users typically only need 4 or 5 fields but these can vary depending on the task.

I’m approaching this by building a basic prototype which I’ll use to drive out deeper needs from users.

But my question is this: is there any specific guidelines or evidence that would help me build a good search engine? What things should I be looking to build? What features?