Content Calendar: Monthly Plan

Offen
#19 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
content

Rechercherichtung

This is a proposal for a four-week social media calendar, not a code change, and the payload names no files or tests. Start with the week-by-week tables and the LinkedIn, Slack and Twitter sample posts in the issue body, and check with the maintainers whether the calendar should be adopted and where it should live. Done means the team has agreed on the calendar and it is written up in the repository.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hello everyone, in response to the last workshop planning we discussed making our discussions more socially public. So here is a content calendar we can follow and cross post in our various social account with priority for LinkedIn, Twitter and Slack.

Using the upcoming worksop as a baseline by posting weekly on Wednesday about the workshop, and the posts format can be;

  • Participants application post.
  • General overview of the workshop.
  • Past workshop and how it went.
  • Call for sponsors? (if we are doing this, then it works).

For extras, you can switch the content format in the table and post about the content in the extras or make more post for the week.

Week 1
Monday New Month Post: Welcome + what’s coming this month
Wednesday Workshop post: choose any of the format above
Friday What’s one thing you wish you knew sooner about OpenMBEE

Extras:

  • The Friday when the community meeting falls, make a morning reminder post about the meeting.

  • GitHub spotlight: Pick one repository and show what someone can find there and how they could contribute.

Week 2
Monday Call for new contributors, implementer of MBSE and a join our community post
Wednesday Workshop post: choose any of the format above
Friday Project spotlight: either within OpenMBEE/ community project— Format: Meet the Projects: Introduce the Model Development Kits, What are they, what do they do, and why do they matter?

Extras:

  • Relevant community meeting video upload announcement and a call to watch it.

  • Blogpost/case study drop (if applicable).

Week 3
Monday Ask an Engineer/Ask the Steering Committee members: Short Q&A on slack.
Wednesday Workshop post: choose any of the format above
Week 4
Monday Education: We can start a series of topics i.e briefly write about topic A and share resources on it. A simple introduction for someone discovering the project for the first time: explain the problem it is trying to solve and the idea of connected engineering information.
Wednesday Community question: What is one thing you wish MBSE tools solve better.
Friday What’s one thing you wish you knew sooner about OpenMBEE

Extras:

  • Community engagement: What do you want to see next month?
  • Community poll/form: What would you like to see more of from OpenMBEE?
Message sample/ Framing content

Each social post should provide good context and welcoming. For example using the week 1 content idea;

LinkedIn

👋 Welcome to a new month with OpenMBEE! We are glad you are here, whether you have been part of the community for a while or are just discovering OpenMBEE.

Here's a little of what's coming this month:

📅 Community activities: [Upcoming events, workshops, or community sessions]

🛠️ Project updates: [What's happening across OpenMBEE projects and the ecosystem]

💡 Get involved: [Contribution opportunities, discussions, or ways to participate]

There is always something happening across the OpenMBEE community, and we would love for you to be part of it. Follow along, join a conversation, share what you're working on, and help us keep building together.

Here is to another month of learning, collaboration, and community!

Slack

👋 Hello @everyone! Welcome to a new month! We are looking forward to another month of learning, collaboration, and building together.

Here is what's coming up:
📅 Events & community activities: [Upcoming events]
🛠️ Project updates: [Updates to look out for]
💡 Ways to get involved: [Contribution opportunities or discussions]

Whether you'\ are contributing, exploring the projects, asking questions, or simply following along, we are happy to have you here!

Stay tuned, join in, and let's make this month a great one! 🚀

Twitter

👋 New month, new opportunities to connect and build with OpenMBEE!

Here is what's ahead:
📅 [Upcoming events]
🛠️ [Project updates]
💡 [Ways to contribute or get involved]

Whether you are new or already part of the community, there is a place for you here.

Let us build together! 🚀

#OpenMBEE #OpenSource

The idea is to use the calendar to guide you in creating various content at ease. You can see that one content is replicated in various platform to keep everyone informed.

Vorherrschende Sprache
HTML
Sterne
2
Forks
0
Ø Merge
15 Std. 17 Min.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Open-MBEE/opensysml.github.io

Alle Issues in Open-MBEE/opensysml.github.io

Ähnliche Issues

Weitere Issues zu Content

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.