Skip to content

Latest commit

 

History

History
 
 

articles

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
title description draft
Readme
About article types for Pantheon Documentation
true

Documentation articles for the Pantheon website platform will initially be written in two types: Tools, which provide general information and step-by-step procedures for using different tools, and Guides, which explain how to solve website problems by breaking goals into phases and subphases, and providing rules-of-thumb as if-then statements.

Tool Articles

Using a tool on or to develop your Pantheon Site that isn't documented here? Write us a tool article and make up to $200. Tool articles must include the following information in their frontmatter:

---
title:
description:
link:
tool_image:

---
(do not add an h1 or h2 repeating the title of the article)

Describe the things you can do with this tool, and provide any other relevant information about it, including the publisher, support info, and any other significant details.

## Pantheon Considerations
Describe any pantheon-specific considerations


## Procedure Goal
Describe the goal in greater detail.

1. Instruction (imperative object with object)

![title](/assets/images/ "alt")

2. Instruction

![title](/assets/images/ "alt")

## Procedure 2 Goal
Describe the goal in greater detail.

1. Instruction

![title](/assets/images/ "alt")

2. Instruction

![title](/assets/images/ "alt")

Guide Articles

Know how to solve problems that aren't the same every time? Write us a guide and make up to $500. Guides are, in Instructional Design parlance, "Systematic Approaches to Problem Solving" (SAP's). The solutions that SAP's guide us toward vary in their complexity, breadth, and depth. They can tell how agencies should approach developing entire websites of varying types from start to finish with all details; they can explain how individual front-end developers should approach solving a specific non-recurrent type of problem; they can They are made of phases, which match sub-goals with rules-of-thumb and procedures for accomplishing them. You can start with the template below:

---
title:
description:
category:
  -

---
(do not add an h1 or h2 repeating the title of the article)

Explain the goal. What variables cause the problem to be solved differently in one case compared to the next case?  

## Phase 1 Goal

Explain the goal and identify variables

### If you (see, have, want to) (condition of the rule-of-thumb)
then you should:
  - Try doing this with that tool (include links and images where necessary)
  - Try doing this with that.

## Phase 2 Goal

Explain the goal and identify variables

### If you (see, have, want to) (condition of the rule-of-thumb)
then you should:
  - Try doing this with that tool (include links and images where necessary)
  - Try doing this with that.