![rhinoceros 5 call out rhinoceros 5 call out](https://www.awf.org/sites/default/files/Website_SpeciesPage_Rhinoceros01_Hero.jpg)
png, but any browser-friendly bitmap format will work. When using bitmap images, the preferred format is. svg vector format for images, especially for diagrams. It is also safest to use lowercase filenames and extensions. Please use image names without spaces (use a hypen - NOT an underscore - for word separation).
RHINOCEROS 5 CALL OUT CODE
“openNURBS” (not OpenNURBS, nor opennurbs, nor oPeNnURBs) unless it refers to a namespace in code where it is capitalized, or a path where it is not.“Plugins” is not hyphenated unless it refers to a place in the Rhino UI where it is hyphenated.The following spelling and case conventions are adopted on this site: Bold should be used sparingly as it is often present in headers as natural division of content. **Bold** (strong emphasis) is used in instructions to highlight critical instructions that are very important. Navigate to C:\Program Files\Rhinoceros 5 (64-bit)\Plug-ins. *Italics* are used to denote filenames, paths, and file extensions. The operating system-specific font weight is set in the footer using javascript. On macOS, the site will (almost) certainly use Helvetica Neue or Helvetica (font size: 16 px, font weight: 300, line height: 1.6). On Windows, this site attempts to use Segoe UI (font size: 16 px, font weight: 400, line height: 1.6) and falls back to Frutiger Linotype, Dejavu Sans, Helvetica Neue, Helvetica, Arial, in that order. # Sub Header become H3 headers and are reserved for sub-sections within a major section. # Header become H2 headers and are reserved for major sections within the page. # Title become H1 headers and are reserved for the title of the page only. As with guides, this is not a hard-and-fast rule, but rather a general convention. In general, when considering new file names for samples, please imagine you are saying “_ sample”. Obviously, this is not a hard-and-fast rule, but rather a convention. This often leads to verbs ending in “-ing”, the progressive or continuous verb tense. In general, when considering new file names for guides, please imagine you are saying “Guide to _”. Google treats and underscore as a word joiner - so “red_sneakers” is the same as “redsneakers.”
![rhinoceros 5 call out rhinoceros 5 call out](https://wiki.documentfoundation.org/images/9/9d/IvanIconDraftReference.png)
Google treats a hyphen as a word separator, but does not treat an underscore that way. The file name for this guide is style-guide. For example, consider the name of this guide: “Style Guide”. In addition, Google recommends one construct compound URL names with - and not underbars ( _). This leads to more consistent and legible URLs. The naming convention for files - guides, samples, etc - is lowercase with - used as spaces. It will save you from redoing your content many times. How is the new feature different from the alternative?Īrmed with the answers, build an outline by filling in the following template to form a single paragraph:īefore you start creating content, have someone review your elevator pitch.It could be a more painful Rhino workflow. What was the alternative before this feature was available? This doesn’t necessarily mean another vendor’s product.What is the key differentiator? Just pick the ONE that is most likely to keep someone’s attention.What is the feature’s category (modeling, editing, rendering, export, etc.)?.What pain will the new feature make go away? What is a day in their life like both without and with the feature? Why do they want it? What compelling need does the feature satisfy? While there may be many needs, pick the one or two really compelling reasons customers will use the feature.Who is the new feature targeted at? Of course many potential users can benefit.It will save you from redoing your content many times.”īefore doing a video, forum post, blog post, or any new feature content, write down the answers to these simple questions: If you can’t answer them, don’t start creating content. Before you start creating What/Why content, do this. In those few seconds she should understand what the feature is, who it’s for, how she might benefit, and how the new feature is different from an earlier version. “You have only a few seconds to capture the attention of a Rhino user, potential user, or boss that knows nothing about a new Rhino feature.