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.

Sign up for GitHub

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

Jump to bottom

Write blog posts for backdropcms.org #158

Open
jenlampton opened this issue Jan 5, 2016 · 33 comments
Open

Write blog posts for backdropcms.org #158

jenlampton opened this issue Jan 5, 2016 · 33 comments
Labels
audience - outreach content - blog post

Comments

@jenlampton
Copy link
Member

jenlampton commented Jan 5, 2016 •
edited
Loading

Topic ideas:

  • Becoming a core contributor by @klonos
  • Why support Backdrop CMS by @jackaponte
  • Config management in version control on Pantheon
  • QA environments - GitHub automation improvements by @Gormartsen (?)
  • Long term support for Drupal 6 by @DrupalWizards
  • Event recaps (by whoever attended said events)
  • New core committers / PMC announcements
  • Community spotlights
  • How-Tos / Tutorials
  • New releases of Backdrop CMS

I would love to see posts from as many people in the community as possible! If anyone has anything please add a comment here and we'll get you on the list :)
@jenlampton jenlampton mentioned this issue Jan 5, 2016
Closed
3 tasks
@klonos
Copy link
Member

klonos commented Jan 7, 2016

https://backdropcms.org/news/happy-new-year-backdrop-cms gives me "Access denied". I guess because the post is not published yet. If we could have accounts over at bdcms.org and have some of us given the permission to view unpublished content (for the purpose of reviewing), that'd be great.

Perhaps also permit posting comments for the reviewers so we can communicate things to the author via comment notifications?

@jenlampton
Copy link
Member Author

@klonos The post will be published tomorrow. I'd be happy to give you editor access on backdropcms.org so you can peep the posts ahead of time. I'm hesitant to enable comments for review purposes, I'm leaning toward using comments as usual. But we would need a volunteer to watch the comment threads, answer questions when needed, or ping the appropriate people to answer those questions if they need to be roped in.

@klonos
Copy link
Member

klonos commented Jan 9, 2016

Sorry for the late reply ...back to almost no time in my life. Nevertheless, I would love to be granted whatever permission would allow me to review posts before they get published (not that I would have to approve or anything before going live - simply as a second pair of eyes).

Any idea of how I would be notified of the existence of such to-be-published posts?

...and are you saying that if I see something that might need to be corrected, I should then file an issue here? Not a huge problem, but not very convenient/intuitive. Much better if I could do that straight on the node. That's why I proposed comments.

@sutibun
Copy link

sutibun commented Jan 10, 2016

Are there any guidelines for what we can write on the blog?

  • What topics to stay away from? (e.g. Don't mention/criticize Drupal)
  • Can we write in our personal style?
  • No curses? slang?
  • Only English posts?
  • What images not to include?
  • Don't link to certain sites?
  • etc

Will there be a statement along the lines: the opinions of this blog post may or may not be officially supported by Bd cms...

@jenlampton
Copy link
Member Author

@sutibun i'd say for the most part you can use your judgement on all those things. We'll review and critique if we feel something needs to be changed, but for the most part we trust our people :)

if I see something that might need to be corrected...

Hm, good point @klonos I still don't think comments are the way to go (since we may be using them as actual comments after release). We usually draft these things in google docs. How about using annotations there? Here's the blog post folder: https://drive.google.com/folderview?id=0B_lmQRaaidbnWjJMOElpRWlQZWs&usp=sharing If you request edit access I'd be happy to grant it to you.

Any idea of how I would be notified of the existence of such to-be-published posts?

Realistically, I don't think we can automate any kind of notification system. But you should go by the blog schedule outlined here. In general the post should be up on the site at least the day before the scheduled date for review, and a google doc should be under way before that.

@mikemccaffrey
Copy link
Member

I'd be happy to write a blog post documenting the development and release workflow that I've been using for managing configuration in version control and hosting on pantheon.

@biolithic
Copy link

and I'd be happy to learn a new way to do that!

On Thu, Jan 21, 2016 at 3:25 PM, Mike McCaffrey notifications@github.com
wrote:

I'd be happy to write a blog post documenting the development and release
workflow that I've been using for managing configuration in version control
and hosting on pantheon.

—
Reply to this email directly or view it on GitHub
#158 (comment)
.

@docwilmot
Copy link
Contributor

Can we rename this from 'News' to 'Blog' then? I considered wrting a howto type thing, but it isn't news!? I think calling it news limits what can go on there.

@jenlampton
Copy link
Member Author

@docwilmot I would love to include a how-to from you in the news section!

I chose news because I thought thought news was more inclusive than blog since we'd be able to have tweets, videos, calendar events, announcements, and a ton of other stuff under news too - a blog just being a single sub-set of news items. It also sounds a little more formal (I prefer news for company sites, and blog for personal sites).

I don't think it really matters much what we call it, most howtos are likely news to someone :)

@docwilmot
Copy link
Contributor

At the risk of bike-shedding, http://blog.spinweb.net/-the-difference-between-blog-and-news, FYI. But if its OK with everyone, "News" it is then.

@jenlampton
Copy link
Member Author

A good read :) But, what do you call the section of your site when you mix those two different kinds of things together? (since that's what we're doing on b.org) How about Blews?!

@jenlampton
Copy link
Member Author

I don't have strong feelings one way or the other on what to call it, but it does seem that neitherblog or news is a great fit, maybe something like Updates, or no, people will think it's just software updates - release information.... it's a toughie one.

@docwilmot
Copy link
Contributor

I don't either, but I just was a bit put off by the idea of doing a how-to post and calling it "news". One site recommended call it "blog" but have a "news" tag for posts that are news.

@mikemccaffrey
Copy link
Member

It might require less coordination if we allow all users on backdropcms.org to publish blog posts to their own profile. Then we can just review the posts that are published, and promote the ones that are good to the main news/blog section.

Personally, I'd like a place to publish some smaller, more casual notes as I learn things about building with backdrop.

@klonos
Copy link
Member

klonos commented Feb 14, 2016

It might require less coordination if we allow all users on backdropcms.org to publish blog posts to their own profile. Then we can just review the posts that are published, and promote the ones that are good to the main news/blog section.

I really like this idea. Would be great to (eventually, when we have a proper workflow in place) have it so that the original author is shown as well as any contributors/proofreaders too.

Personally, I'd like a place to publish some smaller, more casual notes as I learn things about building with backdrop.

👍 blog posts will do. We can have tags like "news", "tips & tricks", "how-to's" and general "articles" that can be added to those blog posts and that people can use to filter the list by (or have dedicated sections for each if that is preferred).

I personally would like to have a "Contrib news" section where I present new modules to the public as they are being ported or created (or merged into core) and new features/improvements of already existing modules based on their commit history and/or changelog.

@jenlampton
Copy link
Member Author

It might require less coordination if we allow all users on backdropcms.org to publish blog posts to their own profile. Then we can just review the posts that are published, and promote the ones that are good to the main news/blog section.

I really like this idea too. Only, backdropcms.org would then become a site where anyone could have their own personal blog... Are we ready for the implications of that? In some ways it will be great, as we'll be getting all the kinds of requests people would provide in the "real world" as we really will be eating our own dogfood! But there will also be a lot more at stake. We'll now be responsible for keeping everyone's personal blogs online too...

An interesting idea, for sure!

@jackaponte
Copy link

As I mentioned during today's community outreach meeting, I'm going to bottom-line the writing and posting of a blog post on Backdrop + CiviCRM. Aiming to make this happen by mid-September.

@serundeputy
Copy link
Member

i wrote a post about site local drush on pantheon; pending approval and proof read: https://backdropcms.org/news/pantheon-terminus-drush-backdrop-cms-development-workflow

@jenlampton
Copy link
Member Author

I think it's fantastic @serundeputy and you should publish that post whenever you are ready :)

@jenlampton
Copy link
Member Author

jenlampton commented Nov 3, 2016 •
edited by klonos
Loading

@jackaponte @wesruv @mikemccaffrey @tomgrandy @thejimbirch would one of you be willing to write up a blog post about BADCamp?

@thejimbirch
Copy link
Contributor

thejimbirch commented Nov 3, 2016 •
edited by jenlampton
Loading

I could write, but would need bullet points from all of you. Most of my
badcamp was spent selling tshirts!

@jackaponte
Copy link

jackaponte commented Nov 3, 2016 via email

@jenlampton
Copy link
Member Author

@jackaponte do you have time to write up bullet points for @thejimbirch ? That might be a win-win for everyone :)

@jackaponte
Copy link

jackaponte commented Nov 3, 2016 via email

@wesruv
Copy link
Member

wesruv commented Nov 3, 2016

  • The 2.0 version conversation was great! We found that our development strategy is able to introduce new features without breaking API so far, so there might not be a technical reason to have a 2.0. We think we'll release a 2.0 before long because of how many awesome features we've been adding and it'd be a way to recognize that.
  • Great discussion around our community culture and what that means to us, @jackaponte had a great talk explaining how our specific governance, goals, and audience is helping set us up for a great community. Plus we're clearly wonderful people.
  • Thoughts around the future of how entity's view modes are laid out and improvements to the layout system. We're thinking about replacing the Manage Display tab's tabledrag interface with a layout interface that will probably very similar.
  • Discussion of a custom layout builder that works through the UI, decide how many rows/columns are in a layout and how that works and save it to config for reuse.
  • Discussed creating content around demo workflows and implementations for 'real world' use cases. We think example workflows and integrations with systems that our target audience is using now would help make Backdrop feel more real as a solution for them.

@wesruv
Copy link
Member

wesruv commented Nov 3, 2016

Drinking on a mountain can get you "plant dermititis".

@ghost
Copy link

ghost commented Sep 28, 2017

If I want to write a blog post about how I built a particular website in Backdrop, and would like it featured on BackdropCMS.org somewhere, how do I do that? Do I need to ask permission, draft something up first, just post it online (I think I can add content to BDcms.org), ...?

@serundeputy
Copy link
Member

@BWPanda yes just write a draft right on backdropcms.org and then request a proofread and then publish.

@ghost
Copy link

ghost commented Sep 29, 2017

Thanks @serundeputy. I've added my blog post, but am not sure if I did the whole Draft thing properly (didn't see an option for that). My post seems to be live already: https://backdropcms.org/news/building-pandaidau-backdrop-cms

@jenlampton
Copy link
Member Author

jenlampton commented Sep 30, 2017 via email

@backdrop-ops backdrop-ops deleted a comment from klonos Oct 4, 2018
@jenlampton jenlampton mentioned this issue Jul 18, 2021
Open
@irinaz
Copy link

irinaz commented Oct 28, 2021

@jenlampton Did you consider writing blog posts for other websites as well? I am thinking of posts on Pantheon giving more details on Backdrop migrations

@jenlampton
Copy link
Member Author

jenlampton commented Oct 28, 2021 •
edited
Loading

@irinaz yes I think that's even more important than doing it on our own site. I think we have an issue...

edit: I found this? #122

@irinaz
Copy link

irinaz commented Oct 28, 2021

@irinaz yes I think that's even more important than doing it on our own site. I think we have an issue...

edit: I found this? #122

Still valid in 2021, though post is from 2015 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
audience - outreach content - blog post
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests