Style Guide - Revision history

KazVee: Add preferred server listing order & use H2 headers for better readability

2025-01-17T18:17:54Z

Add preferred server listing order & use H2 headers for better readability

← Older revision		Revision as of 18:17, 17 January 2025
Line 1:		Line 1:
	= Style Guide =		== Style Guide ==

	We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.		We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.

	= Writing Language =		== Writing Language ==

	American English is used for consistency, and the writing tone is friendly and professional.		American English is used for consistency, and the writing tone is friendly and professional.
Line 9:		Line 9:
	Please proofread for spelling, grammar, and capitalization before submitting a contribution for review.		Please proofread for spelling, grammar, and capitalization before submitting a contribution for review.

	= User-focused Guidance =		== User-focused Guidance ==

	Users may access the Wiki from desktop, mobile, or other devices. Where possible, providing guidance on a single page for a specific support topic is preferred, ensuring users do not have to click through to different pages unnecessarily.		Users may access the Wiki from desktop, mobile, or other devices. Where possible, providing guidance on a single page for a specific support topic is preferred, ensuring users do not have to click through to different pages unnecessarily.
Line 19:		Line 19:
	Wiki content is intended to be shared between users helping each other in line with our community powered support model. This means that tutorials for a specific Plesk feature or coding language should ideally be detailed on one page. This will create a single weblink with support or guidance that can easily be shared with users asking for help.		Wiki content is intended to be shared between users helping each other in line with our community powered support model. This means that tutorials for a specific Plesk feature or coding language should ideally be detailed on one page. This will create a single weblink with support or guidance that can easily be shared with users asking for help.

	= HelioHost and HelioNet Links =		== HelioHost and HelioNet Links ==

	Please use 'https' and no leading 'www' when linking to [https://heliohost.org/ https://heliohost.org] or [https://helionet.org/ https://helionet.org].		Please use 'https' and no leading 'www' when linking to [https://heliohost.org/ https://heliohost.org] or [https://helionet.org/ https://helionet.org].
Line 25:		Line 25:
	Older links that have the 'www' will still work with an extra redirect, but this format should no longer be used.		Older links that have the 'www' will still work with an extra redirect, but this format should no longer be used.

	= Users =		== Servers ==

			When listing servers, it's preferred to list the best one first, so the order would be: Morty, Tommy, then Johnny.

			== Users ==

	Generally, guidance would be targeted to 'users', which covers our free users and donor users.		Generally, guidance would be targeted to 'users', which covers our free users and donor users.
Line 31:		Line 35:
	For information specific to the Morty server or VPS services, the term 'customers' can be used however this is not a firm requirement.		For information specific to the Morty server or VPS services, the term 'customers' can be used however this is not a firm requirement.

	= Cron Job(s) =		== Cron Job(s) ==

	The agreed convention is to include a space between both words. Plesk calls them 'Scheduled Tasks', but users may be less familiar with this term.		The agreed convention is to include a space between both words. Plesk calls them 'Scheduled Tasks', but users may be less familiar with this term.

	= Screenshot Policy =		== Screenshot Policy ==

	Screenshots are a great addition where appropriate. When using screenshots taken from within your own account, please erase any personal data you do not want published.		Screenshots are a great addition where appropriate. When using screenshots taken from within your own account, please erase any personal data you do not want published.
Line 41:		Line 45:
	The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.		The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.

	= Brand Names =		== Brand Names ==

	Please follow brand preferences for name capitalization: Word'''P'''ress, Git'''H'''ub, Helio'''H'''ost, etc. If in doubt, refer to the brand website for guidance.		Please follow brand preferences for name capitalization: Word'''P'''ress, Git'''H'''ub, Helio'''H'''ost, etc. If in doubt, refer to the brand website for guidance.

	= Further Guidance =		== Further Guidance ==

	This guidance document is dynamic and will be updated as needed to ensure that everyone feels confident about adding contributions to our Wiki.		This guidance document is dynamic and will be updated as needed to ensure that everyone feels confident about adding contributions to our Wiki.

	= Thank You =		== Thank You ==

	We are community powered, which means everyone is welcome to contribute. Thank you for helping us keep improving!		We are community powered, which means everyone is welcome to contribute. Thank you for helping us keep improving!

KazVee: Remove note about Plesk 'Dynamic List' view as it is now deprecated

2024-12-18T15:55:20Z

Remove note about Plesk 'Dynamic List' view as it is now deprecated

← Older revision		Revision as of 15:55, 18 December 2024
Line 40:		Line 40:

	The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.		The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.

	~~Please ensure your screenshots reflect the 'Dynamic List' view since other Plesk views are being deprecated.~~

	= Brand Names =		= Brand Names =

KazVee: Add note about Morty customers in the language style guide

2024-12-18T15:54:17Z

Add note about Morty customers in the language style guide

← Older revision		Revision as of 15:54, 18 December 2024
Line 1:		Line 1:
	== Style Guide ==		= Style Guide =

	We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.		We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.

	== Writing Language ==		= Writing Language =

	American English is used for consistency, and the writing tone is friendly and professional.		American English is used for consistency, and the writing tone is friendly and professional.
Line 9:		Line 9:
	Please proofread for spelling, grammar, and capitalization before submitting a contribution for review.		Please proofread for spelling, grammar, and capitalization before submitting a contribution for review.

	== User-focused Guidance ==		= User-focused Guidance =

	Users may access the Wiki from desktop, mobile, or other devices. Where possible, providing guidance on a single page for a specific support topic is preferred, ensuring users do not have to click through to different pages unnecessarily.		Users may access the Wiki from desktop, mobile, or other devices. Where possible, providing guidance on a single page for a specific support topic is preferred, ensuring users do not have to click through to different pages unnecessarily.
Line 19:		Line 19:
	Wiki content is intended to be shared between users helping each other in line with our community powered support model. This means that tutorials for a specific Plesk feature or coding language should ideally be detailed on one page. This will create a single weblink with support or guidance that can easily be shared with users asking for help.		Wiki content is intended to be shared between users helping each other in line with our community powered support model. This means that tutorials for a specific Plesk feature or coding language should ideally be detailed on one page. This will create a single weblink with support or guidance that can easily be shared with users asking for help.

	== HelioHost and HelioNet Links ==		= HelioHost and HelioNet Links =

	Please use `https` and no leading `www` when linking to [https://heliohost.org/ https://heliohost.org] or [https://helionet.org/ https://helionet.org].		Please use 'https' and no leading 'www' when linking to [https://heliohost.org/ https://heliohost.org] or [https://helionet.org/ https://helionet.org].

	Older links that have the `www` will still work with an extra redirect, but this format should no longer be used.		Older links that have the 'www' will still work with an extra redirect, but this format should no longer be used.

	== Users ==		= Users =

	Generally, guidance would be targeted to 'users', which covers our free users and donor users.		Generally, guidance would be targeted to 'users', which covers our free users and donor users.

	For VPS~~-specific information~~, the term 'customers' can be used however this is not a firm requirement.		For information specific to the Morty server or VPS services, the term 'customers' can be used however this is not a firm requirement.

	== Cron Job(s) ==		= Cron Job(s) =

	The agreed convention is to include a space between both words. Plesk calls them 'Scheduled Tasks', but users may be less familiar with this term.		The agreed convention is to include a space between both words. Plesk calls them 'Scheduled Tasks', but users may be less familiar with this term.

	== Screenshot Policy ==		= Screenshot Policy =

	Screenshots are a great addition where appropriate. When using screenshots taken from within your own account, please erase any personal data you do not want published.		Screenshots are a great addition where appropriate. When using screenshots taken from within your own account, please erase any personal data you do not want published.
Line 41:		Line 41:
	The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.		The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.

	Please ensure your screenshots reflect the `Dynamic List` view since other Plesk views are being deprecated.		Please ensure your screenshots reflect the 'Dynamic List' view since other Plesk views are being deprecated.

	== Brand Names ==		= Brand Names =

	Please follow brand preferences for name capitalization: Word'''P'''ress, Git'''H'''ub, etc. If in doubt, refer to the brand website for guidance.		Please follow brand preferences for name capitalization: Word'''P'''ress, Git'''H'''ub, Helio'''H'''ost, etc. If in doubt, refer to the brand website for guidance.

	== Further Guidance ==		= Further Guidance =

	This guidance document is dynamic and will be updated as needed to ensure that everyone feels confident about adding contributions to our Wiki.		This guidance document is dynamic and will be updated as needed to ensure that everyone feels confident about adding contributions to our Wiki.

	== Thank You ==		= Thank You =

	We are community powered, which means everyone is welcome to contribute. Thank you for helping us keep improving!		We are community powered, which means everyone is welcome to contribute. Thank you for helping us keep improving!

KazVee: Remove 'Single Page Changes' section as this was only relevant for PRs on GitHub

2024-12-18T15:51:04Z

Remove 'Single Page Changes' section as this was only relevant for PRs on GitHub

← Older revision		Revision as of 15:51, 18 December 2024
Line 2:		Line 2:

	We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.		We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.

	~~== Single Page Changes ==~~

	~~Please keep contributions small and focused, ideally changing only 1 page per edit.~~

	~~Larger requests that change several files increase the risk of conflicts if multiple people are working on the same page at the same time.~~

	~~Additionally, contributions with many files changed take longer to review. An entire contribution can be delayed if changes are requested on a single file.~~

	== Writing Language ==		== Writing Language ==

KazVee: /* Cron Job(s) */

2024-10-31T21:14:45Z

Cron Job(s)

← Older revision		Revision as of 21:14, 31 October 2024
Line 41:		Line 41:
	== Cron Job(s) ==		== Cron Job(s) ==

	The agreed convention is to include a space between both words. Plesk calls them `Scheduled Tasks`, but users may be less familiar with this term.		The agreed convention is to include a space between both words. Plesk calls them 'Scheduled Tasks', but users may be less familiar with this term.

	== Screenshot Policy ==		== Screenshot Policy ==

KazVee: Created page with "== Style Guide == We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation. == Single Page Changes == Please keep contributions small and focused, ideally changing only 1 page per edit. Larger requests that change several files increase the risk of conflicts if multiple people are working on the same page at the same time. Additionally, contri..."

2024-10-04T01:00:56Z

Created page with "== Style Guide == We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation. == Single Page Changes == Please keep contributions small and focused, ideally changing only 1 page per edit. Larger requests that change several files increase the risk of conflicts if multiple people are working on the same page at the same time. Additionally, contri..."

New page

== Style Guide ==

We welcome contributions to our community powered Wiki. Please see our documentation style guidelines below, created to help maintain consistency across user guidance documentation.

== Single Page Changes ==

Please keep contributions small and focused, ideally changing only 1 page per edit.

Larger requests that change several files increase the risk of conflicts if multiple people are working on the same page at the same time.

Additionally, contributions with many files changed take longer to review. An entire contribution can be delayed if changes are requested on a single file.

== Writing Language ==

American English is used for consistency, and the writing tone is friendly and professional.

Please proofread for spelling, grammar, and capitalization before submitting a contribution for review.

== User-focused Guidance ==

Users may access the Wiki from desktop, mobile, or other devices. Where possible, providing guidance on a single page for a specific support topic is preferred, ensuring users do not have to click through to different pages unnecessarily.

Users will have varying levels of technical knowledge, so the guidance provided should be accessible to a wide audience.

Users may prefer to translate the Wiki content into a language they are more comfortable with, so slang or jargon should be avoided.

Wiki content is intended to be shared between users helping each other in line with our community powered support model. This means that tutorials for a specific Plesk feature or coding language should ideally be detailed on one page. This will create a single weblink with support or guidance that can easily be shared with users asking for help.

== HelioHost and HelioNet Links ==

Please use `https` and no leading `www` when linking to [https://heliohost.org/ https://heliohost.org] or [https://helionet.org/ https://helionet.org].

Older links that have the `www` will still work with an extra redirect, but this format should no longer be used.

== Users ==

Generally, guidance would be targeted to 'users', which covers our free users and donor users.

For VPS-specific information, the term 'customers' can be used however this is not a firm requirement.

== Cron Job(s) ==

The agreed convention is to include a space between both words. Plesk calls them `Scheduled Tasks`, but users may be less familiar with this term.

== Screenshot Policy ==

Screenshots are a great addition where appropriate. When using screenshots taken from within your own account, please erase any personal data you do not want published.

The existing convention for Plesk is to take screenshots in Light Mode and to use a red rectangle outline border to highlight important sections.

Please ensure your screenshots reflect the `Dynamic List` view since other Plesk views are being deprecated.

== Brand Names ==

Please follow brand preferences for name capitalization: Word'''P'''ress, Git'''H'''ub, etc. If in doubt, refer to the brand website for guidance.

== Further Guidance ==

This guidance document is dynamic and will be updated as needed to ensure that everyone feels confident about adding contributions to our Wiki.

== Thank You ==

We are community powered, which means everyone is welcome to contribute. Thank you for helping us keep improving!