Skip to content

Add blog post about church transportation website - #5

Merged
codetricity merged 2 commits into
Oppkey:mainfrom
Gilaze:Gilaze-patch-1
Jul 9, 2026
Merged

Add blog post about church transportation website#5
codetricity merged 2 commits into
Oppkey:mainfrom
Gilaze:Gilaze-patch-1

Conversation

@Gilaze

@Gilaze Gilaze commented Feb 18, 2026

Copy link
Copy Markdown
Contributor

Added a blog post detailing the development of a church transportation website, including features, system architecture, and relation to skills learned at Fastopp.

Added a blog post detailing the development of a church transportation website, including features, system architecture, and relation to skills learned at Fastopp.
@codetricity codetricity self-assigned this Feb 18, 2026
@codetricity

codetricity commented Feb 18, 2026

Copy link
Copy Markdown
Contributor

Thanks for the submission — great project and write-up. This is a strong real-world application.

However, this PR does not follow the blog post structure required for our Quarto site. It will be good practice to update the structure so you get comfortable with both pull requests and Quarto conventions.

Please make the following required changes before we can merge:


✅ Required Changes

1️⃣ Structure Requirement

Blog posts must follow this folder structure:

posts/<post-slug>/index.qmd

Example:

posts/ai-washing/index.qmd

Please:

  • Create a folder named after your post (kebab-case, lowercase)
  • Move the file into that folder
  • Rename it to index.qmd

2️⃣ Frontmatter Requirement

The post is missing required Quarto YAML frontmatter.

Please add frontmatter at the top of index.qmd using the same format as existing posts.

Example:

---
title: "Your Post Title Here"
author: "Your Name"
date: "2026-02-18"
categories: [python]
---

Reference:
posts/ai-washing/index.qmd


3️⃣ Folder Naming Convention

Folder names must be lowercase and use hyphens instead of spaces.

Example:

church-transportation-system


Recommended Improvements (Optional for This PR)

These are not blockers for merge, but will significantly improve the post:

  • Convert the raw URL into a proper Markdown link.
  • Add a clear “Tech Stack” section.
  • Specify which SQL database was used.
  • Clarify what “real-time” means technically.
  • Include at least one screenshot in a local assets/ folder using Quarto figure syntax.
  • Clarify the GitHub Actions architecture (scheduled workflows, triggers, etc.).
  • Refine technical phrasing around ORM and Leapcell deployment.

Our blog posts aim to be production-quality technical writing suitable for a hiring manager or engineering audience.

Once these required changes are made, I’ll review again and merge.

Thanks!

@codetricity
codetricity merged commit d352df5 into Oppkey:main Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants