Replies: 6 comments 19 replies
-
I'd honestly not like to roll our own, but I personally have a few sticking points that need to be met for an alternative platform:
It may be that we do want our own blog system, but perhaps not for non-technical people. Primary example is marcom team. To be clear, we can have a blog system external to the app that is really just used by the marcom team for sharing news, etc. while we have a way for working groups and contributors, etc to add posts directly on the site as well. I have most of the feature done as far as working groups go, I put it on pause while I dealt with lots of operational on-goings last week. I also put it on pause per thinking about the complexity of dealing with permissions outside the scope of working groups (i.e., if someone from marcom adds an announcement, how do we simply implement a system that will allow anyone else from marcom edit the post as needed). I'm not for reinventing the wheel by any means, but I've also been bitten too many times in the past gluing disparate systems together and have seen where the growing pains of having to get away from glue can almost kill an organization. @benoitc I believe you were suggesting ghost? Do you have an example or can you example in simple terms how we would set this up, maintain, etc? |
Beta Was this translation helpful? Give feedback.
-
Before talking about the implementation we must fix the requirements needed
for the blog. Is anything missing in the list above? Are there tickets
already created about it?
On Fri 5 Mar 2021 at 01:19, Bryan Paxton ***@***.***> wrote:
I'm not completely opposed to ghost, but I do not want to host it. It
would be nice if there was something like ghost, but more lightweight.
Regardless, it has to be evaluated (time box).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIQBS2XOJUBDS4H6ACDTCAPPVANCNFSM4YNA4ZIQ>
.
--
Sent from my Mobile
|
Beta Was this translation helpful? Give feedback.
-
Well zotonic should fit our needs imho. But let’s point the bullet in front
of its features :)
On Tue 9 Mar 2021 at 17:34, Bryan Paxton ***@***.***> wrote:
I think most everything you bullet pointed above is what i see as general
requirements.
- be able to preview a blog
- allows private view of a post
- scheduling (allows an author to plan when a post will be published)
- allow a group of author to participate to a blog or a post
- allows multiple author on a blog post
- store history of edits to ease the dition
- support RSS/ATOM and other media format
- can support the addition of of media to a post
- support templating
- can easily be binded to our member database
Let me add a couple to that list :
- Easy to setup (relative, but it shouldn't take an entire day to get
going)
- Easy to interface with the api (for integrating into main site)
- Easy to make seamless (more or less) style wise with the main site.
As for my comment on slack, I was simply stating it would be nice if there
were something that existed in our ecosystem that fulfills the above so we
can support out ecosystem, but there is no such tool to my knowledge. That
said, AFAIK ghost seems like the best fit and no one else has put forth any
other suggestions. I like the idea of forestry, but I think it's a better
fit when you're entire website is made with forestry, not just a part.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIWDVYCDYOE6QMSJG7TTCY5YZANCNFSM4YNA4ZIQ>
.
--
Sent from my Mobile
|
Beta Was this translation helpful? Give feedback.
-
We can contract them for it’s maintenance. Until we handle the design and
the customization that should enter in the wg budget. If we want that we
should set our requirements for it and the 99 we want.
Benoît
On Tue 9 Mar 2021 at 17:44, Bryan Paxton ***@***.***> wrote:
Does zontonic offer a hosted solution? I figured it was self-hosted, etc.
That one is very important to me. I do not want us to host this nor
maintain it in any form short of maintaining the content, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAADRIXZTKK3A3O4DSEYLOTTCY66XANCNFSM4YNA4ZIQ>
.
--
Sent from my Mobile
|
Beta Was this translation helpful? Give feedback.
-
Adding my 2c here, as the initiator of Zotonic. I checked your list, and Zotonic does all that and much more. And, of course, it has a wysiwyg editor. It is used by many people to edit content. For hosting, we can discuss that, as we do host quite some ourselves and also work with other parties. |
Beta Was this translation helpful? Give feedback.
-
In Principle Zotonic could be a good choice. There might be resistance at the board level though: we spent a substantial amount on the Erlang Central porting to Zotonic (that was as IEUG) only to at the end throw it away because we didn't get the data transferred at a reasonable cost. What exactly happened and who's fault that was I have no idea. Just mentioning that they might be resistance with those who still remember that we (as in our precursor, but the money would be in EEFs bank account if we hadn't) thrown some money in the direction of Zotonic and had nothing usable. Therefore if is to be done it needs to be well prepared: clear comparison of alternatives. All cost estimates. |
Beta Was this translation helpful? Give feedback.
-
Let's discuss alternatives to rolling our own blog solution. Let's discuss the pros and cons of each alternative solution and the pros and cons of rolling our own.
Beta Was this translation helpful? Give feedback.
All reactions