I am waiting for your answers to the following clarification questions regarding the blog feature specification:

## Question 1: `jq` Dependency Handling

**Context**:
```markdown
- What happens when `jq` is not installed on the system where `posodobi_blog.sh` is run? The script should ideally check for `jq` and provide a user-friendly error message if it's missing. [NEEDS CLARIFICATION: Should the script check for `jq` and exit with an error if not found, or assume `jq` is always available?]
```
**What we need to know**: Should the `posodobi_blog.sh` script explicitly check for the presence of `jq` and handle its absence?

**Suggested Answers**:

| Option | Answer | Implications |
|--------|--------|--------------|
| A      | **Check for `jq` and exit with an error if not found.** | The script will be more robust and provide clear feedback to the user if `jq` is missing. This adds a small amount of complexity to the script. |
| B      | **Assume `jq` is always available.** | The script will be simpler, but might fail with cryptic errors if `jq` is not installed, requiring manual debugging. |

**Your choice**: _[Please respond with A or B]_

## Question 2: Malformed JSON Metadata Handling

**Context**:
```markdown
- How does the system handle malformed JSON metadata in an article file? The script should ideally skip the problematic article and log an error, rather than failing entirely. [NEEDS CLARIFICATION: Should malformed JSON cause the script to fail or skip the article with a warning?]
```
**What we need to know**: How should the `posodobi_blog.sh` script behave if it encounters malformed JSON metadata in an article file?

**Suggested Answers**:

| Option | Answer | Implications |
|--------|--------|--------------|
| A      | **Skip the problematic article and log a warning.** | The script will continue processing other articles, ensuring the blog is mostly updated. The user will be informed about the issue with the specific article. |
| B      | **Fail the script entirely.** | The script will stop execution, forcing the user to fix the malformed JSON before any blog updates can proceed. This ensures data integrity but might be less user-friendly. |

**Your choice**: _[Please respond with A or B]_

## Question 3: Invalid Article Filename Convention

**Context**:
```markdown
- What happens if an article file does not follow the `YYYY-MM-DD-` naming convention? The script should ideally ignore such files or log a warning.
```
**What we need to know**: How should the `posodobi_blog.sh` script handle article files that do not adhere to the `YYYY-MM-DD-` naming convention?

**Suggested Answers**:

| Option | Answer | Implications |
|--------|--------|--------------|
| A      | **Ignore such files and log a warning.** | The script will only process correctly named article files, and the user will be informed about any files that were skipped. This allows for flexibility but might hide issues if the user expects all files to be processed. |
| B      | **Fail the script entirely.** | The script will stop execution, forcing the user to rename incorrectly named files. This ensures strict adherence to the naming convention but might be less user-friendly. |

**Your choice**: _[Please respond with A or B]_
