Hugoifier
fix(readme): and docker
Commit
d7e63ec2fc43982fd89e53b3175578a1b279d220c81ec41ec0413b8098b094b2
Parent
48176db5e8915bc…
2 files changed
+1
-1
+5
-3
+1
-1
| --- Dockerfile | ||
| +++ Dockerfile | ||
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # Use an official Python runtime as a parent image |
| 2 | -FROM python:3.9-slim | |
| 2 | +FROM python:3.11.4-slim | |
| 3 | 3 | |
| 4 | 4 | # Set the working directory in the container |
| 5 | 5 | WORKDIR /app |
| 6 | 6 | |
| 7 | 7 | # Copy the requirements file into the container |
| 8 | 8 |
| --- Dockerfile | |
| +++ Dockerfile | |
| @@ -1,7 +1,7 @@ | |
| 1 | # Use an official Python runtime as a parent image |
| 2 | FROM python:3.9-slim |
| 3 | |
| 4 | # Set the working directory in the container |
| 5 | WORKDIR /app |
| 6 | |
| 7 | # Copy the requirements file into the container |
| 8 |
| --- Dockerfile | |
| +++ Dockerfile | |
| @@ -1,7 +1,7 @@ | |
| 1 | # Use an official Python runtime as a parent image |
| 2 | FROM python:3.11.4-slim |
| 3 | |
| 4 | # Set the working directory in the container |
| 5 | WORKDIR /app |
| 6 | |
| 7 | # Copy the requirements file into the container |
| 8 |
+5
-3
| --- README.md | ||
| +++ README.md | ||
| @@ -19,11 +19,11 @@ | ||
| 19 | 19 | - Identify partials (e.g., `header.html`, `footer.html`) and reusable elements. |
| 20 | 20 | - Convert hardcoded links, images, and text into Hugo-friendly components. |
| 21 | 21 | |
| 22 | 22 | ### Phase 2: Decap CMS Integration |
| 23 | 23 | |
| 24 | -- Extract site structure elements (navigation, hero sections, footers) into YAML/JSON files in Hugo’s `data/` directory. | |
| 24 | +- Extract site structure elements (navigation, hero sections, footers) into YAML/JSON files in Hugo's `data/` directory. | |
| 25 | 25 | - Generate a Decap CMS `config.yml` file with proper collections for pages, posts, and layout elements. |
| 26 | 26 | - Ensure the generated theme is fully editable via Decap CMS. |
| 27 | 27 | |
| 28 | 28 | ### Phase 3: Automation & Deployment |
| 29 | 29 | |
| @@ -34,11 +34,11 @@ | ||
| 34 | 34 | |
| 35 | 35 | ## Getting Started |
| 36 | 36 | |
| 37 | 37 | ### Prerequisites |
| 38 | 38 | |
| 39 | -- Python 3.7 or higher | |
| 39 | +- Python 3.11.4 | |
| 40 | 40 | - Hugo extended version |
| 41 | 41 | - OpenAI API key |
| 42 | 42 | - Cloudflare account (for deployment) |
| 43 | 43 | |
| 44 | 44 | ### Installation |
| @@ -56,7 +56,9 @@ | ||
| 56 | 56 | ``` |
| 57 | 57 | |
| 58 | 58 | ## Usage |
| 59 | 59 | |
| 60 | 60 | Run the CLI tool to start the conversion process: |
| 61 | -bash | |
| 61 | + | |
| 62 | +```bash | |
| 62 | 63 | python cli.py convert --input theme.html --output hugo-theme |
| 64 | +``` | |
| 63 | 65 |
| --- README.md | |
| +++ README.md | |
| @@ -19,11 +19,11 @@ | |
| 19 | - Identify partials (e.g., `header.html`, `footer.html`) and reusable elements. |
| 20 | - Convert hardcoded links, images, and text into Hugo-friendly components. |
| 21 | |
| 22 | ### Phase 2: Decap CMS Integration |
| 23 | |
| 24 | - Extract site structure elements (navigation, hero sections, footers) into YAML/JSON files in Hugo’s `data/` directory. |
| 25 | - Generate a Decap CMS `config.yml` file with proper collections for pages, posts, and layout elements. |
| 26 | - Ensure the generated theme is fully editable via Decap CMS. |
| 27 | |
| 28 | ### Phase 3: Automation & Deployment |
| 29 | |
| @@ -34,11 +34,11 @@ | |
| 34 | |
| 35 | ## Getting Started |
| 36 | |
| 37 | ### Prerequisites |
| 38 | |
| 39 | - Python 3.7 or higher |
| 40 | - Hugo extended version |
| 41 | - OpenAI API key |
| 42 | - Cloudflare account (for deployment) |
| 43 | |
| 44 | ### Installation |
| @@ -56,7 +56,9 @@ | |
| 56 | ``` |
| 57 | |
| 58 | ## Usage |
| 59 | |
| 60 | Run the CLI tool to start the conversion process: |
| 61 | bash |
| 62 | python cli.py convert --input theme.html --output hugo-theme |
| 63 |
| --- README.md | |
| +++ README.md | |
| @@ -19,11 +19,11 @@ | |
| 19 | - Identify partials (e.g., `header.html`, `footer.html`) and reusable elements. |
| 20 | - Convert hardcoded links, images, and text into Hugo-friendly components. |
| 21 | |
| 22 | ### Phase 2: Decap CMS Integration |
| 23 | |
| 24 | - Extract site structure elements (navigation, hero sections, footers) into YAML/JSON files in Hugo's `data/` directory. |
| 25 | - Generate a Decap CMS `config.yml` file with proper collections for pages, posts, and layout elements. |
| 26 | - Ensure the generated theme is fully editable via Decap CMS. |
| 27 | |
| 28 | ### Phase 3: Automation & Deployment |
| 29 | |
| @@ -34,11 +34,11 @@ | |
| 34 | |
| 35 | ## Getting Started |
| 36 | |
| 37 | ### Prerequisites |
| 38 | |
| 39 | - Python 3.11.4 |
| 40 | - Hugo extended version |
| 41 | - OpenAI API key |
| 42 | - Cloudflare account (for deployment) |
| 43 | |
| 44 | ### Installation |
| @@ -56,7 +56,9 @@ | |
| 56 | ``` |
| 57 | |
| 58 | ## Usage |
| 59 | |
| 60 | Run the CLI tool to start the conversion process: |
| 61 | |
| 62 | ```bash |
| 63 | python cli.py convert --input theme.html --output hugo-theme |
| 64 | ``` |
| 65 |