46
devNews
6y

+++ Thank you for 1000+'s! +++

So guys we did it! We've reached our first big milestone!
This account was created about a month ago, and we are already this far!

Thanks to all authors (@DLMousey, @filthyranter, @baewulff) who are putting a lot of work and time into their articles and help this account to further grow in size!

To make this article at least a bit informative, here's how we publish our posts:
When I started this account, I hadn't thought of how articles were going to be published. Should I give the password to all writers? Should I post the articles manually?
Well, after I've started the devNews Discord Server, @olback suggested making a Discord Bot, that helps us to publish our stuff.
After surprisingly few hours, @olback already got a prototype working.
We have a special channel and whoever writes stuff in it, updates the current article. Later, I took on the work, @olback has done and switched to LowDB, to be able to let multiple users have their own articles they are working on and much more. (Like special signatures)
And that's how it is now.
We have a channel for draft, where we write our stuff and a channel for publishing, where the bot listens to what we write and then publishes the articles with a command.
That's all of it.

Thank you for reading!

Comments
  • 5
    Here the people that were mentioned:
    @filthyranter
    @Mousey
    @olback
    @baewulff (sorry I don't know your devRant Username)
  • 2
  • 3
    Congrats!

    It's good to know how the posting works and the bot is cool but wouldn't it have been better to make an articles repo?

    When a pull request (article) is merged to master it could post the rant as the build. Just seems more natural to me
  • 2
    <@kurtr>
    I also write articles on my smartphone sometimes, so no, that would just make it hella complicated
  • 1
    @Skayo surely you don't write them directly in a messaging client? Bitbucket, git lab and github have great mobile sites as well as their desktop versions - in my eyes it would be just as easy to copy it from my writing app of choice and paste it into a website form input as it would be to paste it into discord. Anyway that's just my view, i might have the wrong idea in my head about the publishing workflow and I don't even write articles - I just enjoy reading them so feel free to share your writing anyway you want!
  • 2
    <@kurtr>
    Yeah sure but that doesn't sound less complicated than a Discord Bot to me.
    Maybe in the future, we will have a little website to publish posts, but we definitely wont use git. I'm happy with the bot at the moment.

    The thing is, the discord bot also posts notifications to Discord, welcomes new users, and so on. So why not also handle posting articles?
    Also how do you want to handle tags and images using git? How do you want to let every user have their own signature ("Written by @Skayo")?

    Thanks anyways for you suggestion! Great to hear that you like the articles!
  • 0
    @Skayo what ever works best. Just an fyi - git has tag support. Tags apply to individual commits and are usually used to automate builds for triggering tests rollbacks and package version releases. Username can either be associated with the users email or an alias. To post an article the build trigger would literally be a one line curl command with env vars for the content.
Add Comment