[opensuse-web] [web dev] What cms to use for (potential) opensuse.org website?
I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description. -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Hi, Just some personal experience. Static web page is the safest option. Any CMS can be hacked easily by some guys. I remember the news.opensuse.org (WordPress) was hacked a few times. And it is slow. So if you don't have much content to manage, static web page is pretty okay. To make some dynamic content, you can use JavaScript and fetch API of existing sites. For example, you can get latest news and wiki activities through REST API of WordPress and MediaWiki. If you do have to create some content, static website generator like Jekyll can be a good choice. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2019年6月24日 下午3:42 来自 zerocon.opensource@gmail.com:
I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description. -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On 24/06/2019 22:12, Imad Aldoj wrote:
I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description.
Personally I think the wiki would likely be the best spot, but the two main issues / things to deal with that have blocked adding further sites in the past are 1. Translation support - most CRM's don't do this all that well and we have people willing to translate most things. 2. hosting is hard at the moment, the hero's might be able to sort out something but currently most of openSUSE's websites are hosted by microfocus still and until they are transferred to SUSE IT accessing them is not that simple. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
I kinda expect that but not gonna give up on it. I didn't tell the backstory to avoid making the post longer and thought better save it till the website is ready so people can see problem-proposal side by side and discuss improvement in a single thread. The idea of the website came to mind after struggling myself with the wiki while trying to find my way around the project, pages are separated and hidden(not linked together), information flow is all over the place. When you're just starting out, you end up opening more than 20 tabs and then reach a dead end (like inactive irc channel, no junior jobs, etc) and then you forget what page contained what, or whether this was the right mailing list to begin with or why no one is answering. Maybe it's due to a gap between employees/members who worked on this for years and new people. I agree that it's possible to improve the wiki but I think no one is there to do what it takes (I know there're wiki admins), a wiki is a mess by design [not just en.opensuse.org] but our wiki lacks an active team who go after individual contributions and put it together in one piece [or there's a team but just not taking this part seriously]. The wiki would work only if the pages have a standard, constancy, and someone is assigned (and responsible in front of the board for the quality of the wiki) similar to packages, everyone can contribute but there's a need for a team with accountability keep it updated, organized, meet people needs and only then people will start filling the gaps on their own. So to sum it up, the problem is bigger than me I can't control that in the long run but I struggled myself and I found a webpage would help other people. I know it might never come to light but I'll do what I can. Maybe host it on Github or separate domain and link people to it. If the page can't be hosted and how the wiki operates will stay the same I don't know what else I can do to improve it. Can you think of alternatives? On Tue, Jun 25, 2019 at 12:08 PM Simon Lees <sflees@suse.de> wrote:
On 24/06/2019 22:12, Imad Aldoj wrote:
I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description.
Personally I think the wiki would likely be the best spot, but the two main issues / things to deal with that have blocked adding further sites in the past are 1. Translation support - most CRM's don't do this all that well and we have people willing to translate most things. 2. hosting is hard at the moment, the hero's might be able to sort out something but currently most of openSUSE's websites are hosted by microfocus still and until they are transferred to SUSE IT accessing them is not that simple.
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Can you expand a little more about standard and constancy problem? Maybe with some examples? Also I'm curious if you have some vision how the wiki should operate. How you see team putting contributions in one piece? best regards, Patryk "Sanchez" Zera W wtorek, 25 czerwca 2019, 12:29:47 CEST, Imad Aldoj <zerocon.opensource@gmail.com> napisał(-a): Thewiki would work only if the pages have a standard, constancy, andsomeone is assigned (and responsible in front of the board for thequality of the wiki) similar to packages, everyone can contribute butthere's a need for a team with accountability keep it updated,organized, meet people needs and only then people will start fillingthe gaps on their own.
Hi, No offense, but this thread isn't related to the wiki, Simon simply suggested the wiki and explained current challenges with the website so I gave a bit of background about my own experience and what motivated me to make the website and why I think is necessary and will try to overcome those challenges. Maybe we can make a different thread to ask for feedback. I hope you see things from my perspective. On Wed, Jun 26, 2019 at 1:45 PM Patryk Zera <patryk.zera@opensuse.org> wrote:
Can you expand a little more about standard and constancy problem? Maybe with some examples? Also I'm curious if you have some vision how the wiki should operate. How you see team putting contributions in one piece?
best regards, Patryk "Sanchez" Zera
W wtorek, 25 czerwca 2019, 12:29:47 CEST, Imad Aldoj <zerocon.opensource@gmail.com> napisał(-a):
Thewiki would work only if the pages have a standard, constancy, andsomeone is assigned (and responsible in front of the board for thequality of the wiki) similar to packages, everyone can contribute butthere's a need for a team with accountability keep it updated,organized, meet people needs and only then people will start fillingthe gaps on their own.
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Hi, No problem. I think that most of your reasoning behind website is quite valid but as you mentioned problems with wiki I was just curious if you have already some thoughts on this. I agree, there is no need to include wiki feedback in this thread. Patryk W środa, 26 czerwca 2019, 13:51:47 CEST, Imad Aldoj <zerocon.opensource@gmail.com> napisał(-a): Hi, No offense, but this thread isn't related to the wiki, Simon simply suggested the wiki and explained current challenges with the website so I gave a bit of background about my own experience and what motivated me to make the website and why I think is necessary and will try to overcome those challenges. Maybe we can make a different thread to ask for feedback. I hope you see things from my perspective. On Wed, Jun 26, 2019 at 1:45 PM Patryk Zera <patryk.zera@opensuse.org> wrote:
Can you expand a little more about standard and constancy problem? Maybe with some examples? Also I'm curious if you have some vision how the wiki should operate. How you see team putting contributions in one piece?
best regards, Patryk "Sanchez" Zera
W wtorek, 25 czerwca 2019, 12:29:47 CEST, Imad Aldoj <zerocon.opensource@gmail.com> napisał(-a):
Thewiki would work only if the pages have a standard, constancy, andsomeone is assigned (and responsible in front of the board for thequality of the wiki) similar to packages, everyone can contribute butthere's a need for a team with accountability keep it updated,organized, meet people needs and only then people will start fillingthe gaps on their own.
You can first use GitHub Pages as hosting service. I would say go ahead and keep people posted. We always welcome new contribution. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2019年6月26日 下午2:50 来自 zerocon.opensource@gmail.com:
Hi, No offense, but this thread isn't related to the wiki, Simon simply suggested the wiki and explained current challenges with the website so I gave a bit of background about my own experience and what motivated me to make the website and why I think is necessary and will try to overcome those challenges. Maybe we can make a different thread to ask for feedback. I hope you see things from my perspective.
On Wed, Jun 26, 2019 at 1:45 PM Patryk Zera <patryk.zera@opensuse.org> wrote:
Can you expand a little more about standard and constancy problem? Maybe with some examples? Also I'm curious if you have some vision how the wiki should operate. How you see team putting contributions in one piece?
best regards, Patryk "Sanchez" Zera
W wtorek, 25 czerwca 2019, 12:29:47 CEST, Imad Aldoj <zerocon.opensource@gmail.com> napisał(-a):
Thewiki would work only if the pages have a standard, constancy, andsomeone is assigned (and responsible in front of the board for thequality of the wiki) similar to packages, everyone can contribute butthere's a need for a team with accountability keep it updated,organized, meet people needs and only then people will start fillingthe gaps on their own.
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On 25/06/2019 19:58, Imad Aldoj wrote:
I kinda expect that but not gonna give up on it. I didn't tell the backstory to avoid making the post longer and thought better save it till the website is ready so people can see problem-proposal side by side and discuss improvement in a single thread. The idea of the website came to mind after struggling myself with the wiki while trying to find my way around the project, pages are separated and hidden(not linked together), information flow is all over the place. When you're just starting out, you end up opening more than 20 tabs and then reach a dead end (like inactive irc channel, no junior jobs, etc) and then you forget what page contained what, or whether this was the right mailing list to begin with or why no one is answering. Maybe it's due to a gap between employees/members who worked on this for years and new people.
I agree that it's possible to improve the wiki but I think no one is there to do what it takes (I know there're wiki admins), a wiki is a mess by design [not just en.opensuse.org] but our wiki lacks an active team who go after individual contributions and put it together in one piece [or there's a team but just not taking this part seriously]. The wiki would work only if the pages have a standard, constancy, and someone is assigned (and responsible in front of the board for the quality of the wiki) similar to packages, everyone can contribute but there's a need for a team with accountability keep it updated, organized, meet people needs and only then people will start filling the gaps on their own.
So to sum it up, the problem is bigger than me I can't control that in the long run but I struggled myself and I found a webpage would help other people. I know it might never come to light but I'll do what I can. Maybe host it on Github or separate domain and link people to it. If the page can't be hosted and how the wiki operates will stay the same I don't know what else I can do to improve it. Can you think of alternatives?
Personally I don't think its all as bad as it seems, while you have found a lot of the less well maintained parts of the wiki there are other parts of the wiki that are in decent shape, like the ones immediately off the front page, the board stuff and the packaging guidelines etc. I think ideally having a top level how to contribute page, that contains all the content you wanted to put on the other website linked from the main wiki page for visibility is probably the best way forward. Googling "opensuse how to report a bug" gives you https://en.opensuse.org/openSUSE:Submitting_bug_reports so having a similar https://en.opensuse.org/openSUSE:contributing probably makes sense. The other thing that might make sense is starting to take some of those other outdated pages and archiving them. But I think with the way the project has evolved, removing a bunch of the older team wiki pages and replacing them with one contributing page might make sense and will still be less effort then trying to setup and maintain another CRM.
On Tue, Jun 25, 2019 at 12:08 PM Simon Lees <sflees@suse.de> wrote:
On 24/06/2019 22:12, Imad Aldoj wrote:
I'm working on a new webpage as a contribution guide all in one place. I know about chameleon and bootstrap but I don't have experience with the back end stuff (mostly ruby here) So... The content of www.opensuse.org is hardcoded, right? in this case, what do you recommend for managing this webpage in order to integrate well with the rest of the site? the webpage is fairly simple, this "dynamic" functionality might be used to add a new team and its description.
Personally I think the wiki would likely be the best spot, but the two main issues / things to deal with that have blocked adding further sites in the past are 1. Translation support - most CRM's don't do this all that well and we have people willing to translate most things. 2. hosting is hard at the moment, the hero's might be able to sort out something but currently most of openSUSE's websites are hosted by microfocus still and until they are transferred to SUSE IT accessing them is not that simple.
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
participants (4)
-
Guo Yunhe -
Imad Aldoj -
Patryk Zera -
Simon Lees