A centralized repository for showcasing UI/UX design prototypes and feature implementations. This repository enables rapid feedback from stakeholders and serves as a reference for developers.
Visit the live site: https://care-ecosystem.github.io/Designs
This repository hosts interactive HTML prototypes of various features being developed for Care. Each feature includes:
- Interactive UI prototypes
- Design specifications
- Implementation notes for developers
- Responsive layouts for all devices
Designs/
├── index.html # Main landing page (auto-generated)
├── features.json # Configuration file listing all features
├── features/ # Feature prototypes directory
│ └── example-feature/ # Example feature (use as template)
│ ├── index.html
│ ├── styles.css
│ └── script.js
├── assets/ # Shared assets
│ ├── css/
│ │ └── main.css # Global styles
│ └── js/
│ └── main.js # Shared JavaScript
└── .github/
└── workflows/
└── deploy.yml # GitHub Actions deployment
- Git
- A GitHub account
- Basic knowledge of HTML/CSS/JS
- Clone the repository:
git clone https://github.com/care-ecosystem/Designs.git
cd designs- Open
index.htmlin your browser:
open index.html # macOS
# or
start index.html # Windows
# or just double-click index.html- For better local development, use a local server:
# Using Python
python3 -m http.server 8000
# Using Node.js
npx serve
# Using PHP
php -S localhost:8000Then visit http://localhost:8000
Create a new directory under features/:
mkdir -p features/your-feature-nameUse the example feature as a template:
cp features/example-feature/index.html features/your-feature-name/
cp features/example-feature/styles.css features/your-feature-name/
cp features/example-feature/script.js features/your-feature-name/Edit the files in features/your-feature-name/:
index.html- Update content, structure, and feature demonstrationstyles.css- Add feature-specific stylesscript.js- Add interactive functionality
Add your feature to features.json:
{
"features": [
{
"id": "your-feature-name",
"name": "Your Feature Display Name",
"description": "Brief description of what this feature does",
"status": "In Progress",
"dateAdded": "2026-05-20",
"path": "features/your-feature-name/index.html",
"tags": ["tag1", "tag2"]
}
]
}git add .
git commit -m "Add new feature: Your Feature Name"
git push origin mainThe site will automatically deploy via GitHub Actions.
{
"features": [
{
"id": "unique-identifier", // Required: Unique ID (use kebab-case)
"name": "Display Name", // Required: Human-readable name
"description": "Brief description", // Required: What this feature does
"status": "Status Badge", // Required: e.g., "Draft", "Review", "Final"
"dateAdded": "YYYY-MM-DD", // Required: Date added
"path": "features/id/index.html", // Required: Relative path to feature
"tags": ["tag1", "tag2"] // Optional: Searchable tags
}
]
}- Go to your repository settings on GitHub
- Navigate to Pages in the left sidebar
- Under Source, select GitHub Actions
- The workflow will automatically deploy on every push to
main
The deployment happens automatically via GitHub Actions:
- Push changes to the
mainbranch - GitHub Actions workflow triggers
- Site builds and deploys to GitHub Pages
- Available at
https://your-username.github.io/designs
You can also trigger deployment manually:
- Go to Actions tab in GitHub
- Select Deploy to GitHub Pages workflow
- Click Run workflow
- Keep it simple: Focus on the core feature interaction
- Be responsive: Test on mobile, tablet, and desktop
- Document decisions: Use the implementation notes section
- Show all states: Include loading, error, and empty states
- Gather feedback early: Share the link before implementation
- Reference designs: Use these prototypes as implementation reference
- Check specifications: Review design specs for colors, spacing, typography
- Ask questions: Use GitHub Issues for clarifications
- Update as built: Keep designs in sync with actual implementation
- Keep feature files self-contained in their directory
- Use relative paths for linking to shared assets
- Name files descriptively:
user-profile.html, notpage1.html - Add comments in code for complex interactions
The main stylesheet (assets/css/main.css) provides:
- CSS variables for consistent colors and spacing
- Reusable component classes
- Responsive utilities
- Common layout patterns
Reference these in your feature styles:
/* Use CSS variables */
.my-component {
color: var(--primary-color);
padding: var(--spacing-md);
border: 1px solid var(--border);
}Keep feature-specific styles in the feature's styles.css:
<link rel="stylesheet" href="../../assets/css/main.css">
<link rel="stylesheet" href="styles.css">- Check
features.jsonsyntax is valid (use a JSON validator) - Ensure the
pathfield points to the correct location - Check browser console for JavaScript errors
- Verify relative paths are correct (
../../assets/css/main.css) - Clear browser cache
- Check file names match exactly (case-sensitive on some systems)
- Check Actions tab for deployment status
- Ensure GitHub Pages is enabled in repository settings
- Wait 1-2 minutes for CDN cache to clear
- Hard refresh browser (Cmd+Shift+R or Ctrl+Shift+R)
- Create a new branch for your feature:
git checkout -b feature/your-feature-name- Make your changes and commit:
git add .
git commit -m "Add feature: description"- Push and create a pull request:
git push origin feature/your-feature-name- Request review from team members
- Issues: Use GitHub Issues for bugs or feature requests
- Discussions: Use GitHub Discussions for questions
- Urgent matters: Contact the design team directly
Internal use only - Care Team
- Design Team
- Development Team
Last updated: 2026-05-20