Qoute of the day:
G&27y&^%$jksasd54325 87912 43y98ye1qhb cbueyrqwiugeq879 shdag987wyq9
After we've cool idea before in previous series π, we draw our mind-blowing freestyle.
The Grayprint
Are you ready to hear about our exciting project plan? We're thrilled to share it with you! Our team has been hard at work developing a game-changing solution that will revolutionize the industry.
We've got big ideas and even bigger goals, and we can't wait to bring them to life. Our plan is to create a cutting-edge platform that will streamline processes, enhance user experiences, and provide unparalleled value to our customers. From innovative features to state-of-the-art technology, we're pulling out all the stops to make this project a success. Get ready to join us on this thrilling journey!
π Argh... forget about 2 paragraph before. What I want to talk is our Bluprint Grayprint of our freestyle playground to documenting our freestlye trick and gain knowledge form other punk freestyler.
π€ What we need and what we'll do?
The Steps
This is not step by step, but the steps! π€£
GitHub Issue Template as Text Editor for Blogging
Oh my punk, have you heard about this amazing thing? It's called the "Github Issue Template as Text Editor for Blogging"! I mean, who would have thought that a simple Github feature could be used to create such a cool tool for bloggers?
Basically, with this feature, you can use the Github Issue Template to write your blog posts! How crazy is that? You can write and edit your posts just like you would with a regular text editor, but you can also take advantage of Github's amazing collaboration and version control features. It's like having a built-in editor for your blog, right there in Github!
And the best part? You can use all the familiar tools and shortcuts that you're used to, like Markdown syntax and keyboard shortcuts. Plus, you can easily collaborate with other bloggers or editors, leave comments and feedback, and keep track of changes over time. It's like the ultimate blogging tool, all in one place. I can't believe how cool this is!
Categorized The Metaphor Story
To simplify the distribution and management of content on the Metaphor Website, we need standardized labels to make it easier to process data from issues and pull requests that are made by members.
Content Indicators
-
metaphor [
#4A9A4D]: This label is used to indicate issues and pull requests related to the content on the Metaphor Website. -
need to review [
#C9636B]: This label is used to indicate issues and pull requests that need to be reviewed by the relevant team members before they can be merged or published. -
under review [
#A055A4]: This label is used to indicate issues and pull requests that are currently under review by the relevant team members. -
published [
#72D8C8]: This label is used to indicate issues and pull requests that have been published on the Metaphor Website.
Storyteller Indicators
-
new storyteller [
#F6A34E]: This label is used to indicate issues and pull requests related to new storytellers who have expressed interest in contributing to the Metaphor Website. -
storyteller verification [
#EB1ED6]: This label is used to indicate issues and pull requests related to the verification process of new storytellers. -
verified [
#5ABF7F]: This label is used to indicate issues and pull requests related to storytellers who have been verified and approved to contribute to the Metaphor Website.
Common labels used in Open Source repository issues are:
- bug: Indicates that there is a problem with the software that needs to be fixed.
- enhancement: Indicates that there is a feature request or improvement that can be made to the software.
- documentation: Indicates that there is a need for documentation to be created or updated.
- help wanted: Indicates that the project maintainers are looking for help with the issue.
- good first issue: Indicates that the issue is a good entry point for new contributors to the project.
- invalid: Indicates that the issue is not valid or relevant to the project.
- wontfix: Indicates that the issue will not be fixed or implemented.
- question: Indicates that the issue is a question that needs to be answered.
- duplicate: Indicates that the issue is a duplicate of another issue and can be closed.
- feature: Indicates that the issue is a feature request that could be implemented in the future.
Reviewing Metaphor Story from Our Punk Storyteller
At Metaphor, we believe that every story has the power to inspire, connect, and engage people. That's why we are always on the lookout for new and exciting stories that can be shared with our audience. Our process involves working closely with our punk storytellers, who bring their unique perspectives and experiences to the table.
To ensure the quality of our content, we have developed a set of standardized labels that categorize our issues and pull requests. These labels allow us to track the progress of each story, from the initial submission to the final publication. The labels also help us to identify any issues that need to be reviewed or revised before publication.
We have a dedicated team of reviewers who are responsible for ensuring that each story meets our high standards. Our reviewers are experienced storytellers themselves, and they have a keen eye for detail. They provide constructive feedback to our punk storytellers, helping them to refine their stories and make them even more engaging. By working closely with our punk storytellers, we are able to create stories that resonate with our audience and inspire them to take action.
In conclusion, at Metaphor, storytelling is at the heart of everything we do. We are constantly on the lookout for new and exciting stories that can inspire, connect, and engage people. By working closely with our punk storytellers and using standardized labels to categorize our content, we are able to create stories that are both impactful and meaningful. We look forward to continuing this journey with our punk storytellers and sharing their stories with the world.
π Aaaaargh too serious...
Source: Github Discussion
Publish Closed Issue After Review
When issue is closed...
Once upon a time, there was a clever developer named Sarah who wanted to streamline the documentation process for her project on Github. She created a Github Action that automatically generated a markdown file based on closed issues, using the issue title and body as the content for each section. This saved her countless hours of manually updating the documentation, allowing her to focus on more important tasks. Her fellow developers were amazed by her innovation and efficiency, and Sarah became known as the "Markdown Queen" in their community. The end.
Actually it's not Sarah story, it's me btw π€£
... Github action will triggered and generate a Markdown File that contain closed issue.
Trigger GitHub Action
In our action-collections (I will explain what going on that action in the next series) we cook and filter the closed issue (Metaphor Story) that have and match specific label categories in our requirement.
When issue match our requirement, then our GitHub Action will generate a Markdown File with this structure:
---
layout: post
title: A Dynamic Heroicons component for next.js
author: mkubdev
created_at: 2023-03-30T12:52:07Z
language: javascript
---
### The Back Story
...
### The Story
...
After the creation we also trigger the build on Vercel btw thanks Vercel!!! π
Create OG-IMAGE from REST API
When content serve on Metaphore SCP - Website we generate dynamic OG-IMAGE and Banner for each content by title, author, language/category of the contents. By this tools og-image-rest-generator
Content Published
The content published and live in our Metaphore SCP - Website and each content have comment section using Gigcus
π₯ Awesome right!!! That's it... no puncline!
Top comments (0)