Skip to content

Changed mangel-7368b4ac.md #112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jpchauvel merged 2 commits into from
Sep 3, 2025
Merged

Changed mangel-7368b4ac.md #112

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7322e04
Added mangel-7368b4ac.md
MangelRyujin Sep 2, 2025
0660a5c
Changed mangel-7368b4ac.md
MangelRyujin Sep 3, 2025
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
56 changes: 56 additions & 0 deletions blog/members/mangel-7368b4ac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
blogpost: true
author: Miguel Angel Fernández
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
Comment on lines +1 to +9
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 3, 2025

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Add required publish date in front matter

ABlog/JB posts typically need a date. Add it directly under blogpost to avoid build/runtime surprises.

 ---
 blogpost: true
+date: 2025-09-03
 author: Miguel Angel Fernández
 location: Lima
 category: members
 language: Español
 image: 1
 excerpt: 1
 ---

If this repo uses a different key (e.g., "published"), I can align it after scanning other member posts. Do you want a quick repo scan?

🏁 Script executed:

#!/bin/bash
# List all markdown files under blog/members
echo "Member post files:"
find blog/members -maxdepth 1 -type f -name "*.md"

# Search for 'date:' and 'published:' keys in front matter of member posts
echo -e "\nOccurrences of 'date:' in blog/members:"
rg -n '^[ \t]*date:' -C2 blog/members

echo -e "\nOccurrences of 'published:' in blog/members:"
rg -n '^[ \t]*published:' -C2 blog/members

Length of output: 3136

Add required date in front matter

Insert a date: field under blogpost: true to match other member posts. For example:

---
blogpost: true
+date: 3 September, 2025
author: Miguel Angel Fernández
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
author: Miguel Angel Fernández
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
---
blogpost: true
date: 3 September, 2025
author: Miguel Angel Fernández
location: Lima
category: members
language: Español
image: 1
excerpt: 1
---
🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around lines 1 to 9, the front matter is
missing the required date field; add a date: entry directly under blogpost: true
using the same format as other member posts (ISO-like YYYY-MM-DD or the
repository convention) so the metadata matches and publishing tooling recognizes
the post.

💡 Verification agent

🧩 Analysis chain

Optional: Align front matter and metadata with repo conventions

Validate keys (image/excerpt types, language value) against existing posts to avoid build quirks.

Also applies to: 32-36, 6-6

🏁 Script executed:

#!/bin/bash
# Scan existing members for keys and values to align conventions
fd -t f -a 'blog/members' | sort | tee /dev/stderr \
  | xargs -I {} rg -nH -C0 -e '^(---|\.\.\.)$|^blogpost:|^date:|^author:|^location:|^category:|^language:|^image:|^excerpt:' {}
echo
echo "Field-list usage:"
rg -nH -e '^:[A-Za-z]+:' blog/members || true
echo
echo "Distinct language values:"
rg -No '^\s*language:\s*\K.+$' blog/members | sort -u

Length of output: 2794

🏁 Script executed:

#!/bin/bash
# List first 5 markdown files in blog/members and display their YAML front matter
files=$(fd . blog/members -e md | head -n 5)
for f in $files; do
  echo "File: $f"
  sed -n '1,12p' "$f"
  echo
done

Length of output: 1716

Mandatory: Align front matter with repo conventions

  • Add a date: DD MMM, YYYY field to the front matter (e.g. date: 03 Sep, 2025)
  • Change author: Miguel Angel Fernández to your GitHub alias (author: mangel) and move the full name into the Markdown heading
  • Standardize location: Lima to location: Lima, Perú (with accent)

No changes needed for the metadata list at lines 32–36—it already matches existing posts.

🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around lines 1 to 9, update the front matter
to include a date field in the format "DD MMM, YYYY" (e.g. "date: 03 Sep,
2025"), change the author key from "Miguel Angel Fernández" to the GitHub alias
"mangel", and standardize the location value to "Lima, Perú" (with accent);
leave the existing metadata at lines 32–36 unchanged and move the full name
"Miguel Angel Fernández" into the Markdown heading inside the document body.


% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 3, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove in-document NOTE before publishing

User-facing reminder should not ship.

-% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
📝 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
% NOTA: No olvidar poner la fecha de publicación debajo de `blogpost: true`
🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around line 11, remove the in-document
reminder line "% NOTA: No olvidar poner la fecha de publicación debajo de
`blogpost: true`" so the user-facing NOTE does not ship; if the publication date
is still missing, add the proper date value under the existing "blogpost: true"
frontmatter instead of leaving an internal reminder.


# Miguel Angel Fernández

```{gravatar} mangelryujin@gmail.com
---
width: 200
class: "member-gravatar"
---
```

```{raw} html
<ul class="social-media profile">
<li>
<a class="external reference" href="https://github.com/MangelRyujin">
<iconify-icon icon="simple-icons:Select.BLANK" style="font-size:2em"></iconify-icon>
</a>
</li>
</ul>
```
Comment on lines +22 to +30
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 3, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Fix GitHub icon and improve accessibility

The icon name looks invalid. Use a known Iconify icon and add accessible labeling; optional: open in new tab with rel protection.

 ```{raw} html
 <ul class="social-media profile">
     <li>
-        <a class="external reference" href="https://github.com/MangelRyujin">
-            <iconify-icon icon="simple-icons:Select.BLANK" style="font-size:2em"></iconify-icon>
+        <a class="external reference" href="https://github.com/MangelRyujin" aria-label="GitHub de MangelRyujin" target="_blank" rel="noopener noreferrer">
+            <iconify-icon icon="simple-icons:github" style="font-size:2em"></iconify-icon>
         </a>
     </li>
 </ul>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **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.

```suggestion
🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around lines 22 to 30 the Iconify icon name
is invalid and the link lacks accessible labeling and safe new-tab attributes;
replace the invalid icon name with a valid one such as "simple-icons:github",
add an aria-label like "GitHub de MangelRyujin" to the anchor, and if opening in
a new tab add target="_blank" and rel="noopener noreferrer" to the anchor for
security and accessibility.


:Aliases: Mangel

:Ciudad: Lima

:Homepage: https://mangel-portfolio.vecel.app

## Sobre mí

Ingeniero informático dedicado al desarrollo de software.

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

Dedicado al desarrollo de software y construcción de sistemas escalables.

### ¿Cómo programas en Python?

Principalmente usando frameworks como django o fastapi para la construccion de apis o sistemas robustos y escalables . Usando pip, uv y poetry. Y aplicando los principios de SOLID y CLEAN CODE para mantener legibilidad y escalabilidad del código.
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 3, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Polish Spanish, casing, and spacing

Framework names and orthography; remove stray space before period.

-Principalmente usando frameworks como django o fastapi para la construccion de apis o sistemas robustos y escalables . Usando pip, uv y poetry. Y aplicando los principios de SOLID y CLEAN CODE para mantener legibilidad y escalabilidad del código.
+Principalmente usando frameworks como Django o FastAPI para la construcción de APIs o sistemas robustos y escalables. Usando pip, uv y poetry, y aplicando los principios de SOLID y Clean Code para mantener la legibilidad y la escalabilidad del código.
📝 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
Principalmente usando frameworks como django o fastapi para la construccion de apis o sistemas robustos y escalables . Usando pip, uv y poetry. Y aplicando los principios de SOLID y CLEAN CODE para mantener legibilidad y escalabilidad del código.
Principalmente usando frameworks como Django o FastAPI para la construcción de APIs o sistemas robustos y escalables. Usando pip, uv y poetry, y aplicando los principios de SOLID y Clean Code para mantener la legibilidad y la escalabilidad del código.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~48-~48: Probablemente falta un signo diacrítico.
Context: ...rameworks como django o fastapi para la construccion de apis o sistemas robustos y escalable...

(AI_ES_GGEC_MISSING_ORTHOGRAPHY_DIACRITIC)

[uncategorized] ~48-~48: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...obustos y escalables . Usando pip, uv y poetry. Y aplicando los principios de SOLID y ...

(AI_ES_GGEC_REPLACEMENT_OTHER)

🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around line 48, the sentence has casing,
spelling, spacing and orthography issues; correct Spanish accents and wording,
capitalize framework/product names properly, replace "uv" with "uvicorn",
capitalize "Django", "FastAPI" and "Poetry" (or keep "pip" lowercase), remove
the stray space before the period, and normalize "CLEAN CODE" to "Clean Code"
(or keep as desired) so the sentence reads fluently and follows Spanish
orthography and consistent casing.


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

He contribuido al módulo edit-python-pe. Esperemos por más.

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

¡Yeaaaaaaaaaaaaaaa!
Copy link
Contributor

@coderabbitai coderabbitai bot Sep 3, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Make availability sentence professional

The current exclamation looks too informal for a profile page.

-¡Yeaaaaaaaaaaaaaaa!
+Sí, disponible para mentoring, consultorías y charlas.
📝 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
¡Yeaaaaaaaaaaaaaaa!
Sí, disponible para mentoring, consultorías y charlas.
🤖 Prompt for AI Agents 
In blog/members/mangel-7368b4ac.md around line 56, the availability sentence
"¡Yeaaaaaaaaaaaaaaa!" is overly informal; replace it with a concise,
professional statement such as "Available for freelance work" or "Open to new
opportunities" (or a similarly appropriate professional phrasing) and ensure
punctuation and capitalization are correct to match the tone of the profile
page.