i agree on a light weight system preferably one where code such as Class with method OOP php if you go down the road of using php.

i've elaborated further down

Why not make a page like "slackwarecommunity.com" then? The Slackware website is good and fine as it is. But sure, the community could also do their own thing and draw users to Slackware and make wiki pages and forums and all that.

Linuxquestions is the "official" Slackware support page. Maybe support/info from/top community can be more effectively done on a slackwarecommunity.com page? who knows.

2 members found this post helpful.

Ooh yes, finally someone who get it!

1 members found this post helpful.

The essentials to consider probably are:

Is probably is going to be something of a community based effort on say git lab where any contributor can join in?
Is it going to involve an established markup or language or is it going to be a fringe approach
Can it be adapted or easily ported down the line.
Is it going to need elaborate install for someone to clone from git and work on a local dev basis
Is there available documentation thats extensive.


Php is high up in being one of the most popular web languages. OOP php uses clean with a systematic class and their method approach.

So if Pat basically handed over work on slackware web to one person or in a direction thats narrow in scope its bound to end up in problems down the line.

I agree with a minimal approach. Sometimes though minimal means not re-writing the wheel that means say taking Bootsrap4 with scss where the heavy lifting has been by team connected to twitter and is probably going to be supported developed for a few yrs but it can be tweaked to suit. It does the job and is responsive.

Front end concerns have to be taken into account if you are appealing to a wide audience and don’t want to be penalized by Google search approach.

Does MySQL really have to be used or should sqlite3 be looked at for back-end ? Is a web really going to need more than 140 terabytes for its database

Whats wrong with a framework if it has community collaboration and doesn’t involve a lot of setup complicated for newbies(eh laravel)

on php theres codeigniter, slim, fatfree framework

python django, flask

Why not, actually? Seems that whatever offers to help with slackware.com have been ignored.

Because there is already a slackware.com page that works perfectly fine.

I'm all for making community pages though if you want to expand on what slackware.com offers. Go ahead, do it, and do it well!

1 members found this post helpful.

ok, let's stop the debate here.

2 members found this post helpful.

What doesn't work fine on it?

For me it's good on the eyes too. Those who use Lynx it works perfect too.

Worst websites around are those who don't really need javascript, but insist on not working if you don't load them.

ok, since you are eager to continue, I will state two reasons widely discussed here before:

slackware.com is severely outdated (1), not counting the ChangeLog, and it just needs tidying up (2). Users here have offered to help on several occasions, but nothing has happened. The older I get the more I realise how help is something very rarely offered just like that. So, completely ignoring these offers, not even reasoning why they are not considered, to me it seems strange to say the least. After all, Slackware depends on its users.

Otherwise, I love the design and the way slackware.com looks.

4 members found this post helpful.

I like the blog feature in slackalaxy since one purpose of as blog is to post new, interesting and current stuff . I guess one issue is that on a new web site who would post stuff since P. Volkerding seems as far as i can see from say twitter account in being fairly minimalist in out put (last post July)

Outdated? When someone tells everyone to jump down a cliff and most are dead below, it is "outdated" to stand on the top alive and not be at the bottom dead. Alot of websites are actually just getting worse and worse, and that's not even counting all the javascript crap loaded from external sites etc, just the way they look and are designed. More and more are just oversimplified mobile websites and no longer serve any valid purpose.

Changing just for the sake of changing is silly. If there is nothing wrong, then don't fix it. So many have gone the way of, there is nothing wrong, but let's fix it anyways, and then things just got worse and worse.

If I was Pat, I would stick with something I could keep control over and manage easily. I think for him the current Slackware page probably does exactly that.

Help and such is all fine, but why not try to do somethign useful instead? If you want to contribute to Slackware website and bringing more people to Slackware and bringing the community together, then make a slackwarecommunity.com page and make it great. We're all behind you on that.

4 members found this post helpful.

Don't forget that he has a life of his own too. Some people like to babble endlessly about all kind of stuff, and some people don't. Personally I don't. Just leave him alone and let him do his thing and be happy that we get Slackware. I think he is doing a great job, and the website is exactly the right kind of output for that. Nothing more is needed for me to use Slackware at least.

3 members found this post helpful.

I actually started handwriting a new Slackware sure using CSS Grid. I got pretty far into it, but there is a ton of stuff on Slackware.com. I have the basics of the site done. I only did it as an experiment to see if I could make the site mobile friendly. It is almost a mirror of the current site with a few minor style changes so it works better with CSS Grid.

Grid is super simple and easy to maintain. Does that sound like a good plan? I could upload it to a got repo when I'm done if you guys want.

I don't think it was intended to say that slackware.com needs to be more modern. I imagine there's a few out there that would like it, but to me, the "outdated" is based on the content, not the styling. The System Requirements page is an easy one to look at. 14.2 takes 8GB+ for a full install and 15.0 is expected to be even higher. Also, packages have been getting compiled with 586 extensions since 14.2's development, so it won't run on a 486 anymore. I think it was also determined that with the installer using the huge kernel, you need more than 64MB of RAM to boot (although, once installed and using an initrd, that requirement can be lowered). Also, Software Sets still includes GNOME and Root Disks still references /dev/hd* instead of /dev/sd*.

It's definitely not horrible, but there are some areas that seem like they haven't seen any updates for some time. I certainly don't blame Pat, because that's a lot to dig through every time a release is put out, and I'd rather him focus on Slackware directly, but it does provide incorrect information for the latest versions of Slackware.

8 members found this post helpful.

I would be interested in having a look at your work...