SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to say thank you Slackware, for giving the skills and ability to continue using this awesome distro. I have learned a lot during the years, and a lot of it is because of Slackware. There is something to be said about Slackware that keeps drawing me back to this distro, and sometimes I feel like the industry can be overwhelming with changes or other things just for the sake of it, but can always return to Slackware and still feel at home. That being said, I would like to propose a website for Slackware. As you know, the site has not changed for years, and it's OK, but more people and users of all kind are using smart devices, tablets, touch, etc. and having a responsive website would help the project a lot. Also, the reason I propose this is because of a few things.
- one I want to bring more users to the community and help it grow more as it could reach out to more users.
- I am trying to break into development and want to contribute my time to a project I care and has a lot of history.
- with more users, pat could get more support than he needs.
I can break the phase it creating this, of course, all of this will be pro-bono and opensource. I was. I am thinking of creating the site on Github and create a organization. Once Pat and others are happy, I can transfer ownership to him or his choosing. This way, someone can audit the code and know its opensource. Let me know your thoughts.
-
Welcome to LQ, joescript!
Great ideas! The best way that you can support Slackware is to help ensure that it survives with financial support. You can donate to Slackware if you wish. Please see the links in my signature.
Hasn't it been said that one of the reasons so much of the website is out of date because it is difficult to change it? From that perspective, I think a new website that is easier to manage is a great idea, but I have no idea if Pat would be receptive to it. It might be a good project to get started and then pitch it to Pat after the release of Slackware 15, with the understanding that he may say no.
There was a new website made, it wasn't accepted for some reason.
Quote:
Originally Posted by Alien Bob
We (Mark Post and myself with the help of others in the team) setup a whole new web site based on an off-the-shelf CMS back in 2012, with the possibility to post articles and looking almost identical in layout to the current site, but that was eventually not accepted by Pat for reasons I do not recall. I doubt that control over the web site will be delegated this time.
well if you did a new website please tell me your not going to use Wordpress. I've just written a light CMS system for somebody that can't code on top of https://fatfreeframework.com/3.6/home What i like about f3 is that i was able to write fairly clean native php classes and methods, which means anybody knowing native PHP could read and understand. Bosca at f3 is pretty open minded so i can see that if there was a web site maybe the core code could be gitlab or somewhere , where for instance contributors could add their contributions on classes that intercept spam etc
I did have capacity for comments then decided it was time consuming to keep going to admin to authorize or not. My approach would be post url of blog onto some social media where , there is room for response.
What would be your approach to a website based on ?
Perhaps it's just the way I was brought up but I would never join a forum and immediately start telling people who had been involved in the project for nearly 30 years how to improve things. Even if they did need improving.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Gerard Lally
Perhaps it's just the way I was brought up but I would never join a forum and immediately start telling people who had been involved in the project for nearly 30 years how to improve things. Even if they did need improving.
Perhaps it's just the way I was brought up but I would never join a forum and immediately start telling people who had been involved in the project for nearly 30 years how to improve things. Even if they did need improving.
Based on his post, he has used Slackware for many years, though perhaps not consistently. Presumably, he joined the forum for the very purpose of bringing this up. Considering that his idea was proposed in a constructive way, I don't have a problem with it.
1. Create a mockup.
2. Ask for opinions and feedback.
3. Make corrections.
4. Tell Pat.
My 2 cents:
* Keep some of the original design heritage, such as the background.
* Don't use a CMS or framework.
* Don't use JS.
* Don't use anything dependent upon other providers, such as Google.
* Use forms.
* KISS.
1. Create a mockup.
2. Ask for opinions and feedback.
3. Make corrections.
4. Tell Pat.
My 2 cents:
* Keep some of the original design heritage, such as the background.
* Don't use a CMS or framework.
* Don't use JS.
* Don't use anything dependent upon other providers, such as Google.
* Use forms.
* KISS.
And make sure you code the entire site only in Emacs or Vim.
I have always looked at Slackware as offering a simple and clean approach to Linux and it would be great if any rebuilt website could reflect this. I am not volunteering a sample but perhaps something along the lines of the slrn website would suit:
This is an HTML5 site, CSS structured, handwritten clean HTML, a very simple look and importantly the bottom right has a button that show the site has been Lynx inspected . It would be easy enough to develop from such a site and I am sure the current web developer would even provide a template.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.