forked from open-y-subprojects/openy_docs
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DS-28 docs: Rebuild Content Types section to remove old references
- Loading branch information
Showing
52 changed files
with
344 additions
and
306 deletions.
There are no files selected for viewing
File renamed without changes
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 15 additions & 14 deletions
29
...user-documentation/content-types/alert.md → ...cumentation/content-types/alert/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,47 +1,48 @@ | ||
--- | ||
title: Alert | ||
description: Displays timely information in a thin banner across your site, just below the header or above the footer. | ||
--- | ||
|
||
> Alerts display timely information in a thin banner across your site, just below the header or above the footer. | ||
![Screen Shot 2020-03-24 at 10.07.11 PM|690x67](upload://4xCXyDaACMFdZrLgm2X88iV7AEY.png) | ||
![An alert](alert--example.png) | ||
|
||
Unlike most content types in YMCA Website Services, you don't use Alert to create pages. Instead, Alerts display as a *rendered entity* or a section of content on other pages. | ||
|
||
Alerts also don't use paragraphs. By design, the layout of Alerts are rigid; however, text editor and the the color options listed below allow content editors some flexibility. | ||
|
||
## When Should You Use an Alert? | ||
|
||
* Timely updates for centers, such as when your hours change or facilities close. | ||
* Marketing promotions, such as for membership campaigns or even promotions. | ||
|
||
## How to Use an Alert | ||
|
||
Click on "Content" from your admin toolbar, and then click on the blue "Add Content" button." Select "Alert" on the next page. | ||
|
||
* **Title**: Displays as the headline for your alert. | ||
|
||
* **Description**: The main body of your alert. Sentences should be short and minimally styled in this section. Uses [the YMCA Website Services Text Editor](https://community.openymca.org/c/Resources-and-training-for-content-editors/Learn-how-to-use-the-basic-text-editing-functions-available-to-content-editors). | ||
* **Description**: The main body of your alert. Sentences should be short and minimally styled in this section. Uses [the Text Editor](../../text-editor). | ||
|
||
* **Color Fields**: These three dropdown fields control different aspects of color in your alert. All three dropdowns reference the [the YMCA Website Services color vocabulary](http://#). | ||
* **Color Fields**: These three dropdown fields control different aspects of color in your alert. All three dropdowns reference the [color vocabulary](../../taxonomy/#color). | ||
|
||
* ***Background Color***: The color of your alert. | ||
* ***Text Color***: Stick to using either black or white for accessibility. | ||
* ***Icon Color***: Changes the appearance of the icon to the left of the title. | ||
* ***Background Color***: The color of your alert. | ||
* ***Text Color***: Stick to using either black or white for accessibility. | ||
* ***Icon Color***: Changes the appearance of the icon to the left of the title. | ||
|
||
* **Link**: Adds a button with a call to action to the alert on the right. Button color defaults to black. [Learn more about the link field ⇒](http://#) | ||
* **Link**: Adds a button with a call to action to the alert on the right. Button color defaults to black. | ||
|
||
* **Placement**: Choose "Header" to show your alert above your main content or "Footer" to show below your main content. | ||
|
||
![admin__alert--dropdowns|662x396, 75%](upload://akUU32T0jawWJ1Q3y5ez8zDaQfT.gif) | ||
![The alert admin fields](alert--fields.gif) | ||
|
||
* **Visibility pages**: This is where you control where the alert displays on your site. In the large text field, you write the relative path of the pages where you want this to appear or not appear. Enter each path on a new line. | ||
|
||
You also have the option to use an asterisk character `*` as a wildcard so you don't have to enter in a large number of relative paths. For example, if you wanted to add an alert to a `/health-and-fitness` section, you would enter `/health-and-fitness*` in the text area. | ||
You also have the option to use an asterisk character `*` as a wildcard so you don't have to enter a large number of relative paths. For example, if you wanted to add an alert to a `/health-and-fitness` section, you would enter `/health-and-fitness*` in the text area. | ||
|
||
![admin__alert--visibility-pages|320x191](upload://epmNM8LN0t7cT4thANWpfOP0mge.gif) | ||
![The alert visibility dialog](alert--visibility.gif) | ||
|
||
> **What is a relative path?** | ||
> A *relative path* is the part of your url after your *domain name.* | ||
> | ||
> At https://ycloud.y.org/open-y-association-websites/community, for example, the *domain name* is **`openy.org`**, while the *relative path* is **`/community`**. | ||
> At `https://example.com/community`, for example, the *domain name* is **`example.com`**, while the *relative path* is **`/community`**. | ||
Using the **Alert visibility state** radio buttons at the bottom, you can either show or hide your alert from the page paths listed in the text area above. | ||
Using the **Alert visibility state** radio buttons at the bottom, you can either show or hide your alert from the page paths listed in the text area above. |
Binary file added
BIN
+108 KB
content/en/docs/user-documentation/content-types/alert/alert--example.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+1.58 MB
content/en/docs/user-documentation/content-types/alert/alert--fields.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+785 KB
content/en/docs/user-documentation/content-types/alert/alert--visibility.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file added
BIN
+21 KB
.../docs/user-documentation/content-types/blog-post/blog-post--carnation-color.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+21.8 KB
...n/docs/user-documentation/content-types/blog-post/blog-post--carnation-news.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+195 KB
.../docs/user-documentation/content-types/blog-post/blog-post--carnation-photo.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+25.4 KB
.../docs/user-documentation/content-types/blog-post/blog-post--carnation-story.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+459 KB
content/en/docs/user-documentation/content-types/blog-post/blog-post--category.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+389 KB
content/en/docs/user-documentation/content-types/blog-post/blog-post--example.jpeg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+19.8 KB
...nt/en/docs/user-documentation/content-types/blog-post/blog-post--lily-color.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+266 KB
...nt/en/docs/user-documentation/content-types/blog-post/blog-post--lily-photo.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+26.3 KB
...nt/en/docs/user-documentation/content-types/blog-post/blog-post--lily-story.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+82.1 KB
content/en/docs/user-documentation/content-types/blog-post/blog-post--style.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.