Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions blog/members/perico-2fbbc543.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
blogpost: true
date: 03 Sep, 2025author: perico
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
Comment on lines +1 to +9
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix invalid YAML front matter (date/author concatenated).

Current line mixes two keys; this will break the build.

--- a/blog/members/perico-2fbbc543.md
+++ b/blog/members/perico-2fbbc543.md
@@
 blogpost: true
-date: 03 Sep, 2025author: perico
+date: 2025-09-03
+author: perico
 location: Lima
 category: members
 language: Español
 image: 1
 excerpt: 1
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
blogpost: true
date: 03 Sep, 2025author: perico
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
---
blogpost: true
date: 2025-09-03
author: perico
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
🤖 Prompt for AI Agents
In blog/members/perico-2fbbc543.md around lines 1 to 9 the YAML front matter has
the date and author concatenated on one line ("date: 03 Sep, 2025author:
perico"), which is invalid and breaks the build; fix it by placing each key on
its own line (e.g., "date: 03 Sep, 2025" then a newline, then "author: perico"),
ensure proper YAML spacing and punctuation, and verify the surrounding
front-matter delimiters remain intact.


# Perico Los Palotes

```{gravatar} perico@example.com
---
width: 200
class: "member-gravatar"
---
```

```{raw} html
<ul class="social-media profile">
<li>
<a class="external reference" href="https://github.com/perico">
<iconify-icon icon="simple-icons:github" style="font-size:2em"></iconify-icon>
</a>
</li>
</ul>
```

:Aliases: perico

:Ciudad: Lima

:Homepage: https://perico.com

## Sobre mí

### ¿Quién eres y a qué te dedicas?

blah

### ¿Cómo programas en Python?

blah

### ¿Tienes algún aporte a la comunidad de Python?

blah

### ¿Estás disponible para hacer mentoring, consultorías, charlas?

blah
Comment on lines +38 to +52
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Replace placeholder content (“blah”) before publishing or mark as draft.

User-facing placeholders degrade quality.

Options:

  • Fill real content for each subsection.
  • Or mark as draft until ready:
 blogpost: true
+draft: true

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~50-~50: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ... blah ### ¿Estás disponible para hacer mentoring, consultorías, charlas? blah

(AI_ES_GGEC_REPLACEMENT_ORTHOGRAPHY_SPELLING)

🤖 Prompt for AI Agents
In blog/members/perico-2fbbc543.md around lines 38 to 52, the four subsections
currently contain placeholder "blah"; replace each "blah" with actual,
user-facing content for "¿Quién eres y a qué te dedicas?", "¿Cómo programas en
Python?", "¿Tienes algún aporte a la comunidad de Python?", and "¿Estás
disponible para hacer mentoring, consultorías, charlas?", or if the content is
not ready set the post as a draft by updating the frontmatter (e.g., published:
false or draft: true) or move the file to the drafts folder so no placeholder
text is published.