Skip to content
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.

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

[ LEARN MORE ] We are always looking for writers to write posts about Strapi Dev Best Practices. #1155

Closed
PaulBratslavsky opened this issue Feb 16, 2023 · 1 comment

Comments

@PaulBratslavsky
Copy link
Contributor

PaulBratslavsky commented Feb 16, 2023

If you're interested in sharing your knowledge and expertise in Strapi development, the Strapi team is always looking for writers to contribute to their blog. They are specifically looking for posts that cover best practices for Strapi development, and they encourage potential writers to watch their best practices videos on their Discord channel to get ideas.

You can also participate during the best practices live sessions that happen every third Wednesday of every month at 1:00 PM CST.

You can find all prerecorded videos on Discord where you can ask questions. https://discord.gg/strapi
2023-02-16_11-30-37

You can also find the videos on YouTube: Best Practices Playlist

To submit an article, simply choose a topic from one of the best practices videos and create an outline for your proposed post. The Strapi team will review your outline and provide feedback before you start writing.

It's important to note that the team is looking for content that is focused on Strapi development and customization, as opposed to basic implementation. This is what the Strapi community has been asking for, so they want to prioritize content that will be the most beneficial for our community.

Overall, if you're a Strapi developer with experience in best practices, this is a great opportunity to share your insights with a wider audience and help others improve their Strapi development skills.

@PaulBratslavsky PaulBratslavsky pinned this issue Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title test NOTICE: WE ARE ALWAYS LOOKING FOR WRITERS TO MAKE POSTS ABOUT STRAPI DEV BEST PRACTICES [ SEE MORE ] Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title NOTICE: WE ARE ALWAYS LOOKING FOR WRITERS TO MAKE POSTS ABOUT STRAPI DEV BEST PRACTICES [ SEE MORE ] NOTICE: We are always looking for writers to write posts about Strapi dev best pracitces. [ SEE MORE ] Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title NOTICE: We are always looking for writers to write posts about Strapi dev best pracitces. [ SEE MORE ] NOTICE: We are always looking for writers to write posts about Strapi dev best pracitces. [ LEARN MORE ] Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title NOTICE: We are always looking for writers to write posts about Strapi dev best pracitces. [ LEARN MORE ] [ LEARN MORE ] We are always looking for writers to write posts about Strapi dev best pracitces. Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title [ LEARN MORE ] We are always looking for writers to write posts about Strapi dev best pracitces. [ LEARN MORE ] We are always looking for writers to write posts about Strapi dev best practices. Feb 16, 2023
@PaulBratslavsky PaulBratslavsky changed the title [ LEARN MORE ] We are always looking for writers to write posts about Strapi dev best practices. [ LEARN MORE ] We are always looking for writers to write posts about Strapi Dev Best Practices. Feb 16, 2023
@hana75 hana75 unpinned this issue Oct 3, 2023
@hana75 hana75 pinned this issue Dec 15, 2023
@hana75 hana75 unpinned this issue Jan 23, 2024
@hana75 hana75 pinned this issue Feb 14, 2024
@vcoisne
Copy link
Contributor

vcoisne commented Mar 13, 2024

Closing in favor of this one #1276

@vcoisne vcoisne closed this as completed Mar 13, 2024
@vcoisne vcoisne unpinned this issue Mar 13, 2024
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

No branches or pull requests

2 participants