Framework Gospel Project
In this assignment, you will choose either Bootstrap or Tailwind CSS and use it to build a small, gospel-themed project. Your content must be drawn from the New Testament or the Book of Mormon. This gives you hands-on practice with a modern CSS framework while creating something meaningful and shareable.
Assignment Overview
You will create a single page or a small multi-page site (e.g., a scripture study page, a topical guide, or a character/place overview) using one framework only. The focus is on using the framework's grid, components, and utilities effectively; the theme keeps the content consistent and appropriate for a BYU-Idaho course.
Learning Objectives
- Use either Bootstrap or Tailwind to build a complete page or small site
- Apply the framework's grid, components, and utilities appropriately
- Customize the framework (Bootstrap variables/overrides or Tailwind config/utilities) so the result does not look like a default template
- Host the project in your WDD 331R portfolio with the required file structure
- Submit your work via the required portfolio and Canvas steps
Content Guidelines
Your project must be gospel-related and use content from at least one of these sources:
- New Testament: stories, teachings, parables, people, or themes
- Book of Mormon: stories, teachings, people, places, or themes
You may combine both (e.g., a comparison or topical page), but the primary content must come from these scriptures. Use accurate references and avoid altering the meaning of the text. You do not need to use every verse verbatim; summaries, quotes, and references are fine.
Ideas: A "Come Follow Me" style study page, a character or place profile, a topical list with short commentary, a simple scripture gallery with cards, or a small multi-page site (e.g., one page per book or topic). Choose something that fits the framework and your time.
Framework Choice and Requirements
Choose One Framework
- Bootstrap: Use the grid, at least two components (e.g., cards, nav, modal, accordion), and customize via CSS overrides or custom properties so the page does not look like an untouched Bootstrap template.
- Tailwind: Use the utility-first approach with the grid, spacing, typography, and at least two distinct UI patterns (e.g., cards, nav, tabs). Use Tailwind's theming (e.g.,
tailwind.config.js) or@applywhere it improves clarity, and avoid a generic "default" look.
Technical Requirements
- Valid, semantic HTML (headings, sections, lists, links, etc.)
- Responsive layout that works on narrow (mobile) and wide (desktop) viewports
- No unstyled or broken layout; framework assets (or build output) must load correctly on your live site
- If you use a build step (e.g., Tailwind CLI), the built CSS must be included so the live GitHub Pages site works
Portfolio Setup and File Structure
Use the same portfolio repository you set up in the GitHub Portfolio Setup assignment. Create a dedicated folder for this project so the structure matches other prove assignments.
Required Directory Structure
In your portfolio repository root, create:
portfolio/
└── unit-4/
└── framework-gospel-project/
├── index.html
└── (other assets: CSS, images, or built files as needed)
Your main entry point for this assignment must be unit-4/framework-gospel-project/index.html. If you add more pages (e.g., topics.html, about.html), keep them inside framework-gospel-project/ and link from index.html.
Submission
Once you have completed your project and tested it in your portfolio, document your work using the form below. Download the PDF and submit it to Canvas along with your portfolio repository link.
Why did you choose Bootstrap or Tailwind for this project? How did you customize the framework so the result does not look like the default theme? Reference specific techniques (e.g., Bootstrap CSS overrides or custom properties, Tailwind theme/config or @apply, custom components).
What was the most challenging part of this assignment, and how did you solve it?
Evaluation Criteria
Your work will be evaluated on:
- Framework use: Correct and effective use of your chosen framework's grid, components, and utilities
- Customization: The page does not look like an uncustomized default theme
- Content: Gospel-related content from the New Testament and/or Book of Mormon, used appropriately
- Responsiveness: Layout and content work on different viewport sizes
- Structure and submission: Correct portfolio path (
unit-4/framework-gospel-project/), working live site, and submission of the documentation PDF and portfolio link via Canvas
Tips for Success
- Pick one framework and stick with it; do not mix Bootstrap and Tailwind on the same page for this assignment.
- Start with a simple scope (e.g., one well-designed page) rather than many pages with little content.
- Test your portfolio page in an incognito window to confirm assets and links work.
- If using Tailwind with a build step, commit the built CSS (or use a GitHub Actions workflow) so Pages can serve the site.
- Use real scripture references and avoid altering doctrine; keep content respectful and accurate.