Jump to content

Rou Dalagurr Food Sovereignty Lab Indigenous garden stairs

From Appropedia
Placeholder image. Replace with a photo of your final project.
Replace with a photo of your final project.
Project data
Authors Niko Zurek
Michael Martin
Lbob
Location Arcata, California, United States
Status "In progress" is not in the list (Idea, Designed, Modelled, Prototyped, Verified, Deployed) of allowed values for the "Project status" property. In progress
Made No
Replicated No
OKH Manifest Download

This paragraph appears in search results and previews for this page. In three to five sentences, summarize the whole project from background to result: what you designed, for whom, where and when, why it matters, and how it turned out. Write this last. It should make sense to someone who has never heard of your project, your client, or Humboldt County.

Background

[edit | edit source]
Before Image
An image of the Rou Dalagurr FSL garden staircase before the commencement of our project

Describe the background of the project, covering who, what, when, why, and where: the client, the site, the course (Engr205 Introduction to Design at Cal Poly Humboldt), the semester, and your team. This page will be read by people around the world and in the future, so give enough context that a stranger understands it. Refer to your images in the text, e.g., Figure 1 shows the site before the project.

The Rou Dalagurr Food Sovereignty Lab (FSL) at Cal Poly Humboldt was in need of a new staircase for safe travel through their steep garden. The design and construction of the garden stairs was designated to be a Engr205 Introduction to Design project. The Indigenous Garden where the staircase was built is often used by older members of the indigenous communities that use the garden. A sturdy, safe, accessible construction was necessary.

Images uploaded to Appropedia must be free to share and uniquely named. Start each file name with your project name, e.g., CCAT_compost_bin_background.jpg. Use File:Default.png as a placeholder until you have the real image. Give every image alt text (alt=) that describes it for readers using screen readers; the caption is what everyone reads, the alt text is what the image shows.

Problem statement

[edit | edit source]

The goal of this project is to develop, construct, and test an outdoor stairway for the Indigenous Food Sovereignty Lab located on the campus of Cal Poly Humboldt. This stairway will allow users of the area a safer route than walking down the existing dirt hillside. Upon completion, the stairway will be able to withstand the elements as well as be safe for users and meet the needs of both the clients and the surrounding environment.

Problem analysis

[edit | edit source]

The problem analysis in this area identifies those things which may limit or direct the stairway to be built for the Indigenous Food Sovereignty Lab. Elements include; user considerations, site conditions, safety, building material selection, environmental considerations, building construction specifications, etc.

Constraints

[edit | edit source]

The specifications for this project define the requirements and limitations that the staircase design must meet. These include the client, project location, available budget, size limitations, and requirements of the site.

  • Client: Indigenous Food Sovereignty Lab (FSL)
  • Client contact person: Julian Jensen
  • Project location: Indigenous Food Sovereignty Lab at Cal Poly Humboldt
  • Maximum budget: [TBD]
  • Source of funding: [TBD]
  • Size: [TBD]
  • Site characteristics: The staircase design must fit into the dirt slope/pathway in such a way as to protect the surrounding vegetation and other structures.
  • Safe passage: The staircase should provide a safe means of traveling down the dirt path.
  • Weather/Outdoor Conditions: The design/materials chosen for the staircase must be durable enough to withstand local weather conditions such as rain and moisture
  • Client needs/preferences: Final design product must meet all client needs/preferences they identify.

Considerations

[edit | edit source]

A few of these considerations for the project are:

  • The angle of the dirt hillside on which you're going to build your staircase
  • The physical characteristics of the soil (drainage, erosion, etc.) in addition to other factors such as ground instability
  • Space to allow enough room for both a staircase and an accessible walkway around it
  • Safety issues regarding the comfort of individuals climbing the staircase
  • Building codes related to accessibility
  • The climate of the area where the staircase will be built (rain or wet weather conditions)
  • Durable materials suitable for long-term exposure to the outdoors and heavy use
  • How well the new staircase fits with the pre-existing lab structure and garden at the Indigenous Food Sovereignty Lab
  • Reducing disruption to plants, soil, and general surroundings
  • Maintenance needs and how well the staircase will hold up over time
  • Accessibility to the construction site and the ease with which tools, equipment, and building supplies may be transported into the construction zone

Criteria

[edit | edit source]

Introduce criteria and constraints in a sentence or two, and refer to the table, e.g., Table 1 lists the criteria, constraints, and weights for this project. Criteria are the basis for judging solutions; constraints are the limits each criterion must meet. Table captions go above the table. Keep this sortable.

Table 1: Example criteria and constraints for purchasing a chocolate bar. Replace with your project's criteria.
Criterion Definition Weight (0–10, 10 highest)
Materials Sustainable materials and natural alternatives to chemicals often used in modern construction required. (e.g. no pressure-treated lumber, no concrete, etc) 10
Aesthetics Overall look of staircase must mesh well with the surrounding garden layout and aesthetic. (e.g. designs redwood planters) 9
Safety Meets state and local codes for outdoor staircase construction. 10
Location Fit Must remain cognizant of factors such as the steep hill on west side of staircase, water line running directly beneath staircase, etc. 8

Usage and production volume

[edit | edit source]

Describe how the design will be used, for how long, how often, and by whom. State how many will be made and whether others are expected to replicate it.

Literature review

[edit | edit source]

This literature review is an annotated bibliography. Introduce it in one to two sentences that name the topics covered and why they matter for this project. Group entries under topic headings (Client first, then 4-12 topics relevant to your design, such as materials, similar projects, local climate, or user needs).

Minimum sources per team member: one peer-reviewed journal article, one book, and two credible web sources, plus the client sources your team needs. More credible sources are welcome.

Each entry has three parts:

  1. The citation in ASCE format. Either place it inside a named footnote, as in the examples below, so it appears under References and can be reused elsewhere on the page with <ref name="Smith2020" />, or write it out in full at the start of the entry. Pick one approach and use it for the whole page.
  2. Summary (two to three sentences): what the source is and what it says. Write it in your own words.
  3. Relevance (one to two sentences): how it informs this design, e.g., a criterion, a constraint, an alternative, or a decision.

Aim for 75-150 words per entry. No plagiarism: summarize, do not copy. Quote sparingly and always in quotation marks with a citation.

**** ^^^^ **** ^^^^ TEMPLATE / RUBRIC

Client

[edit | edit source]

Describe the client and what matters to them for this project. Sources here are often the client's website, documents, and interviews.

Client interview[1]

Summary: Who you interviewed, their role, and the key points they shared.
Relevance: Which criteria, constraints, or considerations came from this interview.
Interview

Client website[2]

Summary: This website is the home page of the Rou Dalagurr Food Sovereignty Lab & Traditional Ecological Knowledges Institute. The page offers a brief introduction on the history, purpose, and cultural relevance of the FSL.
Relevance: The information provided by this website offers a foundational base of knowledge relating to our client that will fundamentally influence our design decisions.

Rou Dalagurr Food Sovereignty Magazine[3]

Summary: This magazine, published through the FSL, provides a variety of academic papers and articles authored by members of the indigenous community.

Relevance: The perspectives and information gleaned from this magazine serve as a means to educate ourse

Materials & Design

[edit | edit source]

Alexander Koutamanis. (2024). "Stair Design and User Interaction." Faculty of Architecture & the Built Environment, Delft University of Technology, 2628 BL Delft, The Netherlands.

Summary: In this paper, the researchers address the high rate of stair related injuries by suggesting a human centered approach to replace building codes. The researchers show that a stairs physical dimensions, such as riser height and tread depth directly affecting diverse user capabilities, particularly during descent when fall risks are highest. The paper concludes that designers and architects can improve safety greatly by including deep treads, lowering the heights of risers, creating edges with sharper contrast in material so the eye is drawn to them.

Relevance: This resource discusses safety limitations and necessities of staircases regarding design and Color/Design/Material choices. This would help guide our project with common sense safety decisions that will bleed into our design and material selections.

Source Type: Architecture Journal Article

Materials & Design

[edit | edit source]

Engel, A. (2007). Building stairs. Taunton Press.

Summary: In this book the author uses pictures and labeled diagrams as well as long bodies of text to describe how to build stairs. the book is packed full of usable and specific information about building stairs. this also includes a very nice outdoor building section at the end of the book that discusses the ins and outs of building a set of stairs outdoors.

Relevance: This will be a important resource as we discuss the design and construction in finer detail and in practice.

Source Type: Reference book

Materials & Design

[edit | edit source]

DoItYourself.com. (2022). “How to build outdoor stairs.” https://www.doityourself.com/stry/h2buildoutdoorstairs (Oct. 11, 2026).

Summary: This article helps you become familiar with the vocabulary, design process, and construction of outdoor staircases. They also cover a wide array of topics including the deign and building practices of all the different components of a set of stairs.

Relevance: this Article specifically covers outdoor staircases which is very important for its application in our project. the article also discusses important details like water proof materials and slope for outdoor stair cases

Source Type: Web References

Work Site[4]

[edit | edit source]

Summary: In this paper, the researchers studied how trail gradient (the steepness), slope alignment, drainage, and trail tread composition (how much rock or gravel) impact erosion on natural-surfaced trails at three protected sites in the United States. As expected, they concluded that both trail grade/gradient and slope alignment are primary factors influencing erosion. They observed increased erosion when trail gradients become greater than their current steepness. Additionally, the researchers identified two secondary factors contributing to trail resistance to erosion: adequate drainage and sufficient rock/gravel content in the trail tread composition.

Relevance: This resource will be useful for examining the FSL Staircase Site path because it currently exists as a dirt slope. Therefore, the researchers' conclusions regarding evaluating the grade, direction of the slope, drainage, and ground composition of an existing dirt trail may help assess the potential for erosion and long term integrity of the land surrounding the path.

Source type: Peer-reviewed journal article.

Work Site[5]

[edit | edit source]

Summary: This resource discusses how factors including slope of hillside, trail grade, type of soil, and drainage affect the building and long term structural integrity of trails. Additionally it describes how to measure grade, and that soil texture affects drainage and durability; in this case clays behave very poorly when wet, silts are intermediate when wet, sands behave well when wet but poorly under repeated loading. The resource also states that understanding how water flows over sloping land is important due to erosion potential from surface runoff of water to both the tread surface and the underlying soil structure.

Relevance: This resource will be helpful in assessing the FSL site prior to construction of the proposed dirt staircase since the staircase is being constructed on an unimproved dirt hillside.

Source type: Reference book.

Work Site[6]

[edit | edit source]

Summary: In this chapter, there is information regarding how the landscape and long-term performance of trails is influenced by the characteristics of landform; the strength of soils; and both rainfall and drainage. It also points out that weak, wet or unstable soils have a higher risk of being damaged and that the grade of the trail needs to be considered with regard to the slope (and physical) characteristics of the site. Additionally, it identifies field reconnaissance as an essential tool to assess the topography; soil; and water; and other site conditions at the time of construction.

Relevance: As the FSL staircase will be built upon a dirt hillside in California, this resource can help evaluate the sites' steepness; the condition of its soils; and the ability to drain off water from the site prior to building.

Source type: Credible web reference.

Key takeaways

[edit | edit source]

In three to six bullets, synthesize what the literature means for your design. Cite the entries above, e.g., <ref name="Author2020" />.

  • Takeaway that shaped a criterion or constraint.
  • Takeaway that shaped an alternative or the final decision

^^^^^^^ GOAL FOR THE END OF WEEK TO FINISH UP TO THIS POINT

Alternative solutions

[edit | edit source]

Introduce this section in one to two sentences specific to your project.

Alternatives

[edit | edit source]

Describe four to eight alternatives, each under its own 'step template' as shown below and each with a catchy, descriptive name.

1
Figure 2: Labeled sketch of the Name design.
Alternative 1 Name

Start each one with the sentence "The Name design..." and explain how it addresses the specifications and criteria. Write in present tense and active voice, e.g., "The light sits three feet above the desk," not "We placed the light three feet above the desk."

For each sketch: use all capitals, name and date the sketch, label parts with arrows, include a key if helpful, and refer to the labels in your text.

Continue this for the four to eight alternatives you have.

Decision

[edit | edit source]

Introduce this section in one to two sentences specific to your project.

Criteria definitions

[edit | edit source]

Define each criterion from Table 1 as it is used to judge the alternatives. These are definitions, not constraints. For example, the constraint on cost is the budget, but cost might be defined as the cost of materials only, or as materials plus operation and maintenance. If your criteria changed, update Table 1 so the two match.

Cost
Definition...
Taste
Definition...

Decision process

[edit | edit source]

Explain the decision process your team used (e.g., decision matrix, Pugh chart). First person is appropriate here. Refer to the table, e.g., Table 2 summarizes the decision matrix.

Table 2: Decision matrix. Scores are 0-10; weighted totals are the sum of weight × score.
Criterion Weight Alternative A Alternative B Alternative C
Cost 10 7 5 9
Taste 7 8 9 4
Weighted total 126 113 118

Final decision

[edit | edit source]

Name the chosen solution and justify it with reference to the criteria and Table 2.

Prototyping

[edit | edit source]

Show your most impactful prototypes from earliest to final. Include at least one prototype for function (does it work? e.g., testing a mechanism, material, or dimension) and at least one prototype for desire (will people want to use it? e.g., a mockup shown to the client or users for feedback). Each caption should say what the prototype is, whether it tested function or desire, and what you learned from it. Early sketches, failed attempts, and photos of materials and hands at work all help tell the story.

Final design

[edit | edit source]

Describe the final design, starting with the big picture and then going into detail. Use labeled images and refer to them in the text. This is usually a big section.

Describe the final design.
Figure # (replace with figure number): The final design with labeled parts.

Construction

[edit | edit source]

Give a complete description of how the final design is built, with lots of images, so someone else could replicate it. Use one {{Step}} per step. This is much easier to write as descriptive (what you did) instead of prescriptive (what another person should do), but you can take either approach.

1
What the reader should see.
Do this first

Longer description of the step, with measurements and tools.

2
What the reader should see.
Do this next

Longer description of the step.

Timeline

[edit | edit source]

Introduce the timeline in one to two sentences, then show it as a table with columns for date, description, and status. Post a proposed timeline early in the semester and update it at the end to show the actual timeline. Say how well your team met it and why dates changed.

Table 3: Project timeline.
Date Description Status
Month Day, 2026 Background and problem statement posted Complete
Month Day, 2026 Literature review posted Complete
Month Day, 2026 First prototype built In progress
Month Day, 2026 Final design installed and tested Not started

Costs

[edit | edit source]

Introduce the three kinds of cost below in one to two sentences.

Design cost

[edit | edit source]

Show the total human hours your team spent outside of class, grouped into categories (e.g., research, brainstorming, prototyping, construction, documentation). Three teammates working for one hour is three human hours. Include a pie chart image and refer to it, e.g., Figure # shows...

Describe the chart, including the largest categories.
Figure #: Design time by category, in human hours (total: ___).

Implementation cost

[edit | edit source]

Introduce the costs to build the design, including donations and reused materials. Note whether costs are actual or proposed. If replication would cost a different amount, say so.

Item Amount Cost per unit Total
Thing - from the thing store — Purchased 3 USD 5.75 USD 17.25
Another thing - 3' x 2', yellow — Donated by ... 1 USD 0.00 USD 0.00
PrintGrand total USD 17.25EUR 14.84 <br />GBP 12.59 <br />CAD 21.39 <br />MXN 359.66 <br />INR 1,291.16 <br />

Maintenance cost

[edit | edit source]

Introduce the ongoing costs in time and money, usually per year.

Table 4: Yearly maintenance cost.
Task Frequency Time per year (hours) Cost per year (USD)
Example task Monthly 2 0.00
Total 2 0.00

Operation

[edit | edit source]

Introduce how to use the design, then give step-by-step instructions with labeled images. Use {{Step}} if the process has more than a few steps. A short video is a great addition:

House wren in JBWR

One sentence describing the video

Keywords: birds
Date: 2020-07-05
Language: English (en)
License: CC BY 4.0
Annotations:
  • 0:10 Birdie coming in
  • 0:16 Birdie is watching you
  • 1:19 Imma head out
  • 1:30 Bye

Maintenance

[edit | edit source]

Introduce this maintenance section. Answer these questions:

  • Are there any needed actions for maintenance?
  • How often?
  • Who should perform maintenance?

Maintenance schedule

[edit | edit source]

This is when to maintain what. Please keep the format the same as it can be used to auto-populate maintenance tables.

Daily
  • A daily task
  • A daily task
Weekly
  • a weekly task
  • a weekly task
Monthly
  • a monthly task
  • a monthly task
Yearly
  • a yearly task
  • a yearly task
Every __ years
  • task
  • task

Maintenance instructions

[edit | edit source]

Give step-by-step maintenance instructions, using {{Step}} if helpful.

Conclusion

[edit | edit source]

Testing results

[edit | edit source]

Describe how you tested the final design and what the results were. Compare the results to your criteria, e.g., in a table like Table 5.

Table 5: Final design performance against criteria.
Criterion Constraint Result Met?
Cost Less than or equal to $3 per ounce $2.50 per ounce Yes

Discussion

[edit | edit source]

Discuss what the testing results mean.

Lessons learned

[edit | edit source]

Discuss what your team learned and what you would do differently next time.

Next steps

[edit | edit source]

Discuss next steps for the project as it goes on into the future.

Troubleshooting

[edit | edit source]

Cover basic operating problems only. For complex issues, the suggestion might be to contact ________.

Problem Suggestion
Example issue Example solution or suggestion
Does not turn on Make sure it is plugged in.
Another issue Etc.

Inspirational Video

[edit | edit source]

Include an inspirational video for sharing.

Introduce the team and semester, e.g., This project was completed in SEMESTER YEAR by Team TEAMNAME:

References

[edit | edit source]
Page data
Part of Engr205 Introduction to Design
License CC-BY-SA-4.0
Organizations Cal Poly Humboldt
Language English ()
Related 0 subpages, 0 pages link here
Views 50 page views (analytics)
Created September 23, 2026 by Lonny Grafman
Last edit October 11, 2026 by StandardWikitext bot
Cookies help us deliver our services. By using our services, you agree to our use of cookies.