├── .github
├── ISSUE_TEMPLATE
│ ├── bug.yml
│ ├── cli.yml
│ ├── custom.yml
│ └── documentation.yml
├── pull_request_template.md
└── workflows
│ └── greetings.yml
├── .gitignore
├── CLI_USAGE.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── SECURITY.md
├── astro.config.mjs
├── bun.lockb
├── package-lock.json
├── package.json
├── public
├── Screenshot.png
├── Screenshot_phone.png
├── favicon.ico
├── fonts
│ ├── Satoshi-Variable.woff2
│ └── hack-regular-subset.woff2
├── images
│ ├── avatar.jpeg
│ ├── clone.png
│ ├── continue.png
│ ├── forked.png
│ ├── newpost.png
│ ├── options.png
│ └── username.png
├── robots.txt
└── syntax-theme.json
├── src
├── components
│ ├── BaseHead.astro
│ ├── Blog.tsx
│ ├── BlogPosts.tsx
│ ├── Footer.astro
│ ├── Header.astro
│ ├── HeaderLink.astro
│ └── Project.astro
├── config.ts
├── content
│ ├── blog
│ │ ├── Contributing.mdx
│ │ ├── Utkarsh_ZemPost.mdx
│ │ ├── check_website_accessibility.mdx
│ │ ├── how_to_create_discord_bot.mdx
│ │ └── zaid's_post.mdx
│ └── config.ts
├── env.d.ts
├── layouts
│ ├── BlogPost.astro
│ └── Layout.astro
├── pages
│ ├── blog.astro
│ ├── blog
│ │ └── [slug].astro
│ ├── index.astro
│ └── rss.xml.js
├── styles
│ └── global.css
└── util
│ └── readingTime.mjs
├── tsconfig.json
└── uno.config.ts
/.github/ISSUE_TEMPLATE/bug.yml:
--------------------------------------------------------------------------------
1 |
2 | name: 🐞 Bug Report
3 | description: File a bug report
4 | title: '[Bug]: '
5 | labels: ['bug']
6 | body:
7 | - type: markdown
8 | attributes:
9 | value: |
10 | Thanks for taking the time to fill out this bug report!
11 | - type: textarea
12 | id: what-happened
13 | attributes:
14 | label: What happened?
15 | description: Also tell us, what did you expect to happen?
16 | placeholder: Add descriptions
17 | value: 'Briefly Describe the bug you found'
18 | validations:
19 | required: true
20 | - type: textarea
21 | id: screenshots
22 | attributes:
23 | label: Add screenshots
24 | description: Add screenshots to see the problems
25 | placeholder: Add screenshots
26 | value: 'Add screenshots'
27 | - type: dropdown
28 | id: browsers
29 | attributes:
30 | label: What browsers are you seeing the problem on?
31 | multiple: true
32 | options:
33 | - Firefox
34 | - Chrome
35 | - Safari
36 | - Microsoft Edge
37 | - Brave
38 | - Other
39 | - type: checkboxes
40 | id: self-grab
41 | attributes:
42 | label: Self - Grab
43 | description: By checking this box, you can fix this bug
44 | options:
45 | - label: I would like to work on this issue
46 | id: terms
47 | attributes:
48 | label: Code of Conduct
49 | description: By submitting this issue, you agree to follow our Code of Conduct
50 | options:
51 | - label: I agree to follow this project's Code of Conduct
52 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/cli.yml:
--------------------------------------------------------------------------------
1 |
2 | name: 🐞 CLI Issue
3 | description: Report an Issue with the CLI
4 | title: '[Bug]: '
5 | labels: ['bug']
6 | body:
7 | - type: markdown
8 | attributes:
9 | value: |
10 | Thanks for taking the time to fill out this CLI bug report!
11 | - type: textarea
12 | id: what-happened
13 | attributes:
14 | label: What happened?
15 | description: Also tell us, what did you expect to happen?
16 | placeholder: Add descriptions
17 | value: 'Briefly Describe the bug you found'
18 | validations:
19 | required: true
20 | - type: textarea
21 | id: screenshots
22 | attributes:
23 | label: Add screenshots
24 | description: Add screenshots to see the problems
25 | placeholder: Add screenshots
26 | value: 'Add screenshots'
27 | - type: dropdown
28 | id: browsers
29 | attributes:
30 | label: What terminal are you seeing the problem on?
31 | multiple: true
32 | options:
33 | - Git Bash
34 | - Powershell
35 | - Command Prompt
36 | - Windows Terminal
37 | - WSL
38 | - Other
39 | - type: checkboxes
40 | id: self-grab
41 | attributes:
42 | label: Self - Grab
43 | description: By checking this box, you can fix this bug
44 | options:
45 | - label: I would like to work on this issue
46 | id: terms
47 | attributes:
48 | label: Code of Conduct
49 | description: By submitting this issue, you agree to follow our Code of Conduct
50 | options:
51 | - label: I agree to follow this project's Code of Conduct
52 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/custom.yml:
--------------------------------------------------------------------------------
1 |
2 | ---
3 | name: Custom issue template
4 | about: Describe this issue template's purpose here.
5 | title: ''
6 | labels: ''
7 | assignees: ''
8 | ---
9 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/documentation.yml:
--------------------------------------------------------------------------------
1 | name: 🔖 Documentation update
2 | description: Improve Documentation
3 | title: '[Docs]: '
4 | labels: ['documentation']
5 | body:
6 | - type: markdown
7 | attributes:
8 | value: |
9 | Thanks for taking the time to fill out this documentation update template!
10 | - type: textarea
11 | id: improve-docs
12 | attributes:
13 | label: What's wrong with the current Documentation?
14 | description: What Issue are you facing?
15 | placeholder: Add descriptions
16 | value: 'Briefly Describe the Issue you are facing'
17 | validations:
18 | required: true
19 | - type: textarea
20 | id: screenshots
21 | attributes:
22 | label: Add screenshots
23 | description: Add Screenshots if Possible
24 | placeholder: Add screenshots
25 | value: 'Add Screenshots here'
26 | - type: checkboxes
27 | id: self-grab
28 | attributes:
29 | label: Self - Grab
30 | description: By checking this box, you acknowledge that you can fix this Documentation Error
31 | options:
32 | - label: I would like to work on this issue
33 | id: terms
34 | attributes:
35 | label: Code of Conduct
36 | description: By submitting this issue, you agree to follow our Code of Conduct
37 | options:
38 | - label: I agree to follow this project's Code of Conduct
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | ## Fixes Issue
4 |
5 |
6 |
7 |
8 |
9 | ## Changes proposed
10 |
11 |
12 |
13 |
14 |
20 |
21 | ## Check List (Check all the applicable boxes)
22 |
23 | - [ ] My Changes follow the [Code of Conduct](https://github.com/Zemerik/ZemPosts/blob/main/CODE_OF_CONDUCT.md) of this Project.
24 | - [ ] My Post or Change does not contain any **Plagarized** Content.
25 | - [ ] The title of the PR is a short description of the Changes made.
26 |
27 | ## Note to reviewers
28 |
29 |
--------------------------------------------------------------------------------
/.github/workflows/greetings.yml:
--------------------------------------------------------------------------------
1 | name: 'Greetings'
2 |
3 | on:
4 | fork:
5 | push:
6 | branches: [main]
7 | issues:
8 | types: [opened]
9 | pull_request_target:
10 | types: [opened]
11 |
12 | jobs:
13 | welcome:
14 | runs-on: ubuntu-latest
15 | steps:
16 | - uses: actions/checkout@v1
17 | - uses: EddieHubCommunity/gh-action-community/src/welcome@main
18 | with:
19 | github-token: ${{ secrets.GITHUB_TOKEN }}
20 | issue-message: 'Welcome, @${{ github.actor }}! Thanks for raising the issue!'
21 | pr-message: 'Great job, @${{ github.actor }}! Thanks for creating the pull request!'
22 | footer: 'Soon the maintainers/owner will review it and provide you with feedback/suggestions. 👍 Rember to leave a ⭐!'
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # build output
2 | dist/
3 | .astro
4 |
5 | # dependencies
6 | node_modules/
7 |
8 | # logs
9 | npm-debug.log*
10 | yarn-debug.log*
11 | yarn-error.log*
12 | pnpm-debug.log*
13 |
14 | # editor
15 | .vscode/
16 |
17 | # environment variables
18 | .env
19 | .env.production
20 |
21 | # macOS-specific files
22 | .DS_Store
23 |
--------------------------------------------------------------------------------
/CLI_USAGE.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 | ZemPosts
15 |
16 |
17 |
18 | Post & Connect with Developers
19 |
20 |
21 |
22 |
23 |
[!Note]
28 | > This CLI tool is currently in Beta. It is not fully complete and may contain bugs or issues. If you encounter any problems or need help, please open an [issue on the repository](https://github.com/Zemerik/ZemPosts). Your feedback is greatly appreciated and will help improve the tool for the final release.
29 |
30 | ## ⚡ Installation
31 |
32 | 1. Install the CLI via `NPM`:
33 |
34 | ```sh
35 | npm i zemposts
36 | ```
37 |
38 | 2. Run the CLI via `NPX`:
39 |
40 | ```sh
41 | npx zemposts
42 | ```
43 |
44 | 3. Enter your GitHub username when prompted.
45 |
46 | 
47 |
48 | ## 💻 Commands:
49 |
50 | You will be prompted a number of commands. Use your **Arrow Keys** to navigate between each option, and the **Enter** key to select a specific option. Below is an overview of each command:
51 |
52 |
53 |
54 |
55 | 1. Clone Repository:
56 |
57 |
58 | - Command: `👨💻 Clone`
59 | - Description: This command allows users to clone either the original ZemPosts repository from GitHub or their forked version. This is useful for users who want to explore and understand ZemPosts.
60 |
61 |
62 |
63 |
64 |
65 |
66 | 2. Create a New Post:
67 |
68 |
69 | - Command: `📘 New Post`
70 | - Description: Users can create a new blog post either via a local web interface (localhost) or directly in the terminal. This flexibility allows users to choose their preferred method for content creation.
71 |
72 |
73 |
74 |
75 |
76 |
77 | 3. Run Locally:
78 |
79 |
80 | - Command: `⚡Locally Running`
81 | - Description: This command provides instructions for running the project locally. It checks if the repository is already cloned and, if not, guides the user through the cloning process and sets up the local environment.
82 |
83 |
84 |
85 |
86 |
87 |
88 | 4. About:
89 |
90 |
91 | - Command: `💁♂️ About`
92 | - Description: Displays a brief overview of ZemPosts, including its purpose and key features. This helps users understand what ZemPosts is and what they can do with it.
93 |
94 |
95 |
96 |
97 |
98 |
99 | 5. Key Features:
100 |
101 |
102 | - Command: `✨ Key Features`
103 | - Description: Lists the key features of ZemPosts, highlighting what makes the platform unique and useful for users.
104 |
105 |
106 |
107 |
108 |
109 |
110 | 6. Links:
111 |
112 |
113 | - Command: `🌐 Links`
114 | - Description: Provides important links related to ZemPosts, including the GitHub repository, official website, and community support links.
115 |
116 |
117 |
118 |
119 |
120 |
121 | 7. Exit:
122 |
123 |
124 | - Command: `🔴 Exit`
125 | - Description: Exits the CLI tool. Users can choose this option when they are done using the CLI.
126 |
127 |
128 |
129 | ## 🤝 Cloning:
130 |
131 | > [!Caution]
132 | > [Git](https://git-scm.com/) needs to be installed on your device!
133 |
134 | You can easily clone either the original ZemPosts Repository or your forked version through our CLI.
135 |
136 | 1. Select the `👨💻 Clone` option and press `Enter`:
137 |
138 | 
139 |
140 | 2. You will now be prompted to clone either the original repository or your forked version. Use your **Arrow Keys** to choose, and press **Enter** to select:
141 |
142 | > [!Tip]
143 | > To clone your forked version, you need to first fork a copy of this repository on your github account. Click [here](https://github.com/Zemerik/ZemPosts/fork) to do so.
144 |
145 | 
146 |
147 | 3. A repository will automatically be cloned.
148 |
149 | - If you cloned the original repository, the destination will be `ZemPosts - Zemerik`
150 | - if you cloned your forked version, the destination will be `ZemPosts - [Your Github Username]`
151 |
152 | ## ➕ Adding your Post:
153 |
154 | > [!Caution]
155 | > You must have cloned your forked version of this repository. Refer to `Cloning` section for assistance.
156 |
157 | 1. Use your arrow keys to select the `📘 New Post` option:
158 |
159 | 
160 |
161 | 2. You will then be prompted to either continue in the terminal or open a webpage on localhost. Use your **Arrow Keys** to choose and press **Enter** to select
162 |
163 | - You will be asked to enter different information such as your Post Title, and Publication Date. Fill out all the required information as this will be showed on the website!
164 |
165 | 
166 |
167 | 3. After you have entered all the required information and submitted, a file would automatically created in the `ZemPosts - [Your Github Username]/src/content/blog` directory with the same title as your post title.
168 |
169 | - If necessary, make any changes.
170 |
171 | 4. After you are happy with your post (remember to check for spelling and grammar mistakes), use `git` to commit and push:
172 |
173 | ```sh
174 | cd ZemPosts - [Your Github Username]
175 |
176 | git add .
177 |
178 | git commit -m "New Post: ..."
179 |
180 | git push -u origin main
181 | ```
182 |
183 | 5. Open a [Pull-Request](https://github.com/Zemerik/ZemPosts/pulls) on this repository!
184 |
185 | > Your PR will be **merged**/**reviewed** as soon as possible!
186 |
187 | ## 🤖 Other Commands:
188 |
189 | - The remaining commands are straightforward and should be easy to use without additional instructions. If you need help with any specific command, please feel free to open an [issue](https://github.com/Zemerik/ZemPosts/issues) for detailed instructions.
190 |
191 | ## 💁 Support:
192 |
193 | For any kind of support or inforrmation, you are free to join our **Discord Server**,
194 |
195 |
196 |
197 |
198 |
199 |
208 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | zemerikY@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 | ZemPosts
15 |
16 |
17 |
18 | Post & Connect with Developers
19 |
20 |
21 |
22 |
23 |
24 |
25 | - Read our Official Docs on [ZemDocs](https://zemdocs.vercel.app/en/zemposts/introduction)
26 |
27 |
28 | ## 🏃♂️ Locally Running:
29 |
30 | - This project can be locally executed on your machine in 4 simple steps!
31 |
32 | > [!Tip]
33 | > [NodeJS](https://nodejs.org/) needs to be installed on your machine.
34 |
35 |
36 | 1. Make a `Copy` of this Repository on your machine by using the following `git command` in your terminal:
37 |
38 | ```
39 | git clone https://github.com/Zemerik/Posts
40 | ```
41 |
42 | 2. `Navigate` into the Project's `directory` by entering the following `command` in your terminal:
43 |
44 | ```
45 | cd ZemPosts
46 | ```
47 |
48 | 3. `Install` the required `Dependencies` by using `NPM`:
49 |
50 | ```nodejs
51 | npm i
52 | ```
53 |
54 | 4. Start the `Development Server` through the following `command`:
55 |
56 | ```nodejs
57 | npm run astro dev
58 | ```
59 |
60 |
61 | ## ➕ Adding your Post:
62 |
63 | > [!Note]
64 | > You can add your Post either manually, or use the CLI. See the [`CLI_USAGE`](https://github.com/Zemerik/ZemPosts/blob/main/CLI_USAGE.md) file for specific instructions.
65 |
66 | 1. Fork a copy of this Repository on your Github account by clicking below,
67 |
68 | - [Fork](https://github.com/Zemerik/ZemPosts/fork)
69 |
70 | 2. Head over to your **Forked** Repository, and locate the `src/content/blog` directory. Create a new file, and name it `[Post Title].mdx`
71 |
72 | > [!Note]
73 | > Remember to replace `[Post Title]` with your actual Post Title.
74 |
75 | 3. Add the following code snippet in the file,
76 |
77 | ```md
78 | ---
79 | layout: ../../layouts/BlogPost.astro
80 | title: POST TILE HERE
81 | description: POST DESCRIPTION HERE
82 | pubDate: Month/Day/Year
83 | ---
84 | ```
85 |
86 | >[!Note]
87 | > Keep the `POST TITLE` and `POST DESCRIPTION` short and concise!
88 |
89 | 4. Write your Post Content after the Code Snippet which you just copied using `Markdown` or `HTML`.
90 |
91 | 5. Save the file in which you have wrote your post content, and open a pull-request on this repository. Your PR will be **merged**/**reviewed** as soon as possible!
92 |
93 | ## 🐞Bug/Issue/Feedback/Feature Request:
94 |
95 | - If you would like to report a bug, a issue, implement any feedack, or request any feature, you are free to do so by opening a issue on this repository. Remember to give a detailed explanation of what you are trying to say, and how it will help the website.
96 |
97 | ## 💁 Support:
98 |
99 | For any kind of support or inforrmation, you are free to join our **Discord Server**,
100 |
101 |
102 |
103 |
104 |
105 |
114 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2025 Hemang Yadav
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 | ZemPosts
15 |
16 |
17 |
18 | Post & Connect with Developers
19 |
20 |
21 |
22 |
23 |
24 |
25 | ## ❗ About:
26 |
27 | ZemPosts stands as an open-source platform, providing users with the opportunity to write and read blogs seamlessly. This connectivity is fostered through the simple act of publishing one's blog to the platform, thus creating a digital hub where like-minded individuals can engage, collaborate, and share insights within the expansive realm of writing and blogging. With its user-friendly interface and inclusive community ethos, ZemPosts serves as a dynamic space where connections are forged, ideas are exchanged, and creativity thrives.
28 |
29 | - Read our Official Docs on [ZemDocs](https://zemdocs.vercel.app/en/zemposts/introduction)
30 |
31 | ## 🤖 CLI:
32 |
33 | ZemPosts has an official CLI that simplifies cloning, contributing, and displaying information. It makes contributing to the repository easier and can display all the information from the README. For more information, refer to the [CLI_USAGE.md](https://github.com/Zemerik/ZemPosts/blob/main/CLI_USAGE.md) file.
34 |
35 | - [Package Link](https://www.npmjs.com/package/zemposts)
36 |
37 | ## 🎥 Youtube Video:
38 |
39 | - Feel free to watch our Youtube Video by clicking below 👇
40 |
41 |
51 |
52 |
--------------------------------------------------------------------------------
/src/config.ts:
--------------------------------------------------------------------------------
1 | export const SITE_TITLE = "ZemPosts - ";
2 | export const SITE_DESCRIPTION = "Post & Connect with Developers";
3 |
--------------------------------------------------------------------------------
/src/content/blog/Contributing.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | layout: ../../layouts/BlogPost.astro
3 | title: How to Contribute to ZemPosts?
4 | description: Steps on how you can add your Post to ZemPosts
5 | pubDate: 07/06/24
6 | ---
7 |
8 | ## ➕ Adding your Post:
9 |
10 | 1. Fork a copy of this Repository on your Github account by clicking below,
11 |
12 | - [Fork](https://github.com/Zemerik/ZemPosts/fork)
13 |
14 | 2. Head over to your **Forked** Repository, and locate the `src/content` directory. Create a new file, and name it `[Post Title].mdx`
15 |
16 | > [!Note]
17 | > Remember to replace `[Post Title]` with your actual Post Title.
18 |
19 | 3. Add the following code snippet in the file,
20 |
21 | ```md
22 | ---
23 | layout: ../../layouts/BlogPost.astro
24 | title: POST TILE HERE
25 | description: POST DESCRIPTION HERE
26 | pubDate: Month/Day/Year
27 | ---
28 | ```
29 |
30 | >[!Note]
31 | > Keep the `POST TITLE` and `POST DESCRIPTION` short and concise!
32 |
33 | 4. Write your Post Content after the Code Snippet which you just copied using `Markdown` or `HTML`.
34 |
35 | 5. Save the file in which you have wrote your post content, and open a pull-request on this repository. Your PR will be **merged**/**reviewed** as soon as possible!
36 |
37 | ## 🐞Bug/Issue/Feedback/Feature Request:
38 |
39 | - If you would like to report a bug, a issue, implement any feedack, or request any feature, you are free to do so by opening a issue on this repository. Remember to give a detailed explanation of what you are trying to say, and how it will help the website.
40 |
41 | ## 💁 Support:
42 |
43 | For any kind of support or inforrmation, you are free to join our **Discord Server**,
44 |
45 |
46 |
47 |
48 |
49 |
50 | Thanks for Reading🙏
51 |
52 |
53 |
--------------------------------------------------------------------------------
/src/content/blog/Utkarsh_ZemPost.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | layout: ../../layouts/BlogPost.astro
3 | title: Utkarsh ZemPost
4 | description: This is my first post on ZemPost i am checking out how to use ZemPost.Its somewhat great.
5 | pubDate: 7/7/2024
6 | ---
7 |
8 |
9 | #
Utkarsh Post
10 |
11 |
This is my first post on ZemPost this platform is somewhat good it feels my developer skills are helping somewhere that's great.
12 |
13 | ###
Thank You
14 |
15 | ---
16 |
--------------------------------------------------------------------------------
/src/content/blog/check_website_accessibility.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | layout: ../../layouts/BlogPost.astro
3 | title: 5 sites to check website accessibility
4 | description: Check your site's accessibility with these tools
5 | pubDate: 8/17/2024
6 | ---
7 |
8 | Website accessibility is more important than ever nowadays. It can be a bit difficult to manually check if your site follows all of the standards or not. So, I've made a list of some services that will help you to ensure you follow all of the standards!
9 |
10 | And the best part? They are all FREE!!!
11 |
12 | ## Wave
13 |
14 | https://wave.webaim.org/
15 |
16 | 
17 |
18 | WAVE® is a suite of evaluation tools that help authors make web content more accessible to individuals with disabilities. It identifies many accessibility and WCAG errors and supports human evaluation of web content, focusing on issues that impact end users and promoting web accessibility education.
19 |
20 | ## Accessibilitychecker
21 |
22 | https://www.accessibilitychecker.org/
23 |
24 | 
25 |
26 | AccessibilityChecker provides a free ADA and WCAG compliance checker that identifies web accessibility issues and gives exact instructions for fixing them.
27 |
28 | ## Accessibe
29 |
30 | https://accessibe.com/accessscan
31 |
32 | 
33 |
34 | Accessibe allows you to find out if your site is accessible & ADA Compliant or not.
35 |
36 | ## Websiteaccessibilitychecker
37 |
38 | https://websiteaccessibilitychecker.com/checker/index.php
39 |
40 | 
41 |
42 | Their site looks very old. To be honest, it's probably the worst one in this list. They failed to detect any flaws in one of my sites (which has some accessibility issues).
43 |
44 | ## Deque
45 |
46 | https://www.deque.com/free-accessibility-test/
47 |
48 | 
49 |
50 | Find the accessibility issues you need to fix and meet your compliance goals. A quick automated scan, powered by axe, provides a summary report and an offer to book an in-depth consultation with a Deque expert.
51 |
--------------------------------------------------------------------------------
/src/content/blog/how_to_create_discord_bot.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | layout: ../../layouts/BlogPost.astro
3 | title: How to Create a Discord Bot?
4 | description: Learn how to create a simple discord bot
5 | pubDate: 10/20/2024
6 | ---
7 |
8 | # How to Code a Discord bot?
9 |
10 | ## 💻STEP 1 - Setting up your workspace:
11 |
12 | - Head over to the terminal of your project and type, `npm init` to set up a nodejs project.
13 |
14 | ## 😃Step 2 - Add the Code:
15 |
16 | - Copy Paste the following code in your entry point,
17 |
18 | ```js
19 | const express = require('express')
20 | const Discord = require('discord.js')
21 | const app = express();
22 |
23 | app.listen(3000, () => {
24 | console.log("Project is running!");
25 | })
26 |
27 | const client = new Discord.Client({ intents: 32767 })
28 |
29 | client.on('messageCreate', async (message) => {
30 | if (message.content === "hi") {
31 | message.channel.send('helllo')
32 | }
33 | })
34 |
35 | client.login('YOUR BOT TOKEN HERE')
36 | ```
37 |
38 | - Remember to replace **YOUR BOT TOKEN HERE** with the actual token of your bot which can be obtained from [the developer portal](https://discord.com/developers/applications)
39 |
40 | ## 🥇Step 3 - Running your project
41 |
42 | - You are now ready to run your project. As soon as your run your project, your discord bot should appear online and send `hello` whenever someone types `hi`.
43 |
44 |
--------------------------------------------------------------------------------
/src/content/blog/zaid's_post.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | layout: ../../layouts/BlogPost.astro
3 | title: Zaid's first Zempost
4 | description: Read about the journey of Zaid, a passionate student and volleyball player, who is working hard to make a big tech community that ever existed.
5 | pubDate: 7/8/24
6 | ---
7 |
8 | Zaid is a dedicated student pursuing a diploma in computer engineering. He has a passion for creating websites and has honed his skills in various web technologies. Beyond academics, Zaid excels as a A1 Zonal Level volleyball player, representing his college in numerous matches at both zonal and intercollege levels. His team has achieved remarkable success, winning multiple matches and earning recognition. Zaid's talent has brought him into the spotlight, with opportunities to play at the state level, proudly representing his college.
9 |
10 |
11 |
12 |
Founder the Impic Community
13 | Zaid is also one of the visionary founders of the Impic Community, alongside Divyanshu. This Discord community aims to create a centralized hub for like-minded individuals such as programmers, gamers, hackers, content creators, video editors, and more. The goal is to foster collaboration, support, and creativity among its members. Join the Impic Community on Discord now and be part of something great!
14 |
15 |
34 | ZemPosts stands as an open-source platform, providing users with the opportunity to write
35 | and read blogs seamlessly. This connectivity is fostered through the simple act of
36 | publishing one's blog to the platform, thus creating a digital hub where
37 | like-minded individuals can engage, collaborate, and
38 | share insights within the expansive realm of writing and blogging.
39 | With its user-friendly interface and inclusive community ethos, ZemPosts serves as
40 | a dynamic space where connections are forged, ideas are exchanged, and creativity thrives.
41 |