Embedded Editorial Images Style Guide

I am a style guide to demonstrate the various options for images, when they are embedded directly into long editorial copy. This uses the “Embed Images” feature, which enables you to set image, size, and alignment, then embed the images in editorial where you like.

Image 1: called without an image number

I am content on the page. It’s expected that if the image is aligned left, then content on the page would slide right.

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

A centered, large image

Image 2: Centered, large

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

It is expected that a centered image will not float left or right relative to copy content.

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

It is expected that a centered image will not float left or right relative to copy content.

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

A small image aligned right

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

Image 4: left align, large

The duration of this release planning (grooming) meeting will vary depending on sprint length. As a general rule of thumb, the team should allocate 15 percent of the team’s total available hours to this meeting early in projects. As the team progresses down the project lifecycle, the team will only need to set aside 5 percent to 10 percent of their available hours for release planning. As an example, at the beginning of a project using two-week sprints, up to 12 hours during that sprint may be allocated for this meeting (15 percent). As the project matures, this time may drop to as low as four hours per sprint. Stay within this range.

This is copy content after the image.