Skip to content

Commit df9a7fe

Browse files
authored
readme (#10)
1 parent bc7715f commit df9a7fe

1 file changed

Lines changed: 121 additions & 0 deletions

File tree

README.md

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
# Piney Data Website
2+
3+
This repository contains the source code for the Piney Data website, built using Pelican static site generator.
4+
5+
## Local Development Setup
6+
7+
1. **Clone the repository**
8+
```bash
9+
git clone https://github.com/pineydata/pineydata.github.io.git
10+
cd pineydata.github.io
11+
```
12+
13+
2. **Set up Python environment**
14+
```bash
15+
python -m venv venv
16+
source venv/bin/activate # On Windows: .\venv\Scripts\activate
17+
pip install -r requirements.txt
18+
```
19+
20+
3. **Run development server**
21+
```bash
22+
python serve.py
23+
```
24+
The site will be available at `http://localhost:5500`
25+
26+
## Development Workflow
27+
28+
### Branch Strategy
29+
1. **Create a feature branch**
30+
```bash
31+
git checkout -b feature/descriptive-name
32+
```
33+
Use prefixes to categorize your changes:
34+
- `feature/` for new features or content
35+
- `fix/` for bug fixes
36+
- `update/` for content updates
37+
- `design/` for theme changes
38+
39+
2. **Make your changes**
40+
- Keep commits focused and atomic
41+
- Write clear commit messages
42+
- Test changes locally using `serve.py`
43+
44+
3. **Create a Pull Request**
45+
- Push your branch to GitHub:
46+
```bash
47+
git push origin feature/descriptive-name
48+
```
49+
- Go to GitHub and create a PR
50+
- Fill out the PR template with:
51+
- Description of changes
52+
- Screenshots (if visual changes)
53+
- Any related issues
54+
- Testing steps
55+
56+
4. **PR Review Process**
57+
- Request review from team members
58+
- Address any feedback
59+
- Make sure GitHub Actions checks pass
60+
- Squash and merge when approved
61+
62+
5. **After Merge**
63+
- GitHub Actions will automatically deploy
64+
- Verify changes on the live site
65+
- Delete the feature branch
66+
67+
## Making Changes
68+
69+
### Content Structure
70+
- `content/pages/`: Markdown files for static pages
71+
- `themes/piney/`: Custom theme files
72+
- `static/`: CSS, JavaScript, and other static assets
73+
- `templates/`: Jinja2 HTML templates
74+
75+
### Configuration Files
76+
- `pelicanconf.py`: Development settings
77+
- `publishconf.py`: Production settings
78+
- `.github/workflows/deploy.yml`: Deployment automation
79+
80+
## Deployment
81+
82+
The site is automatically deployed using GitHub Actions whenever changes are merged to the `main` branch through a PR.
83+
84+
1. **Automatic Deployment**
85+
- GitHub Actions will automatically:
86+
- Build the site using `publishconf.py`
87+
- Deploy to GitHub Pages
88+
- Preserve CNAME for custom domain
89+
90+
2. **Verify Deployment**
91+
- Check the Actions tab in GitHub for build status
92+
- Visit [www.pineydata.com](https://www.pineydata.com) to see your changes
93+
94+
## Custom Domain Setup
95+
96+
The site uses a custom domain (www.pineydata.com) configured through:
97+
- `content/extra/CNAME` file
98+
- GitHub Pages settings
99+
100+
## Theme Development
101+
102+
The custom theme uses:
103+
- Tailwind CSS for styling
104+
- Bootstrap Icons for icons
105+
- Custom geometric patterns and animations
106+
107+
Brand Colors:
108+
- Primary: `#009477`
109+
- Secondary: `#2fa1ba`
110+
111+
112+
## Troubleshooting
113+
114+
If the site isn't updating:
115+
1. Check GitHub Actions for any build errors
116+
2. Verify PR was properly merged to `main` branch
117+
3. Check that CNAME file is present in the deployed site
118+
119+
## Need Help?
120+
121+
Contact [hello@pineydata.com](mailto:hello@pineydata.com) for support.

0 commit comments

Comments
 (0)