I sometimes use a wrapper div, but only on more complex sites that I'm doing for a company it person. For myself, I try to keep things in no more than 5 tabs in the CSS Nav <nav>.

For the Slackware site I have made the navigation horizontal on desktop and a drop-down menu for mobile (CSS and HTML only). I don't have JS as much as say .... Bryan Lunduke does, but I about it where it is not needed. A site like Slackware doesn't need JS and should have that added complexity. Heck, I was surprised that it was a php site to be honest. I don't really know why, but I don't suppose it matters.

Eventually I'll have time to finish my version of slackware.com and let everyone see it. I'm not good at sharing before a product is at least presentable.

1 members found this post helpful.

Well I posted this is for a few reasons, As I mentioned before, I use open-source software for a while, and it helps me in many ways, and I wanted to accomplish a few things by starting to create websites and apps. I am going to be straight and tell everyone why.

- First, I want to break into development as a career, I love to code in many forms but like web technology. I work as Sysadmin by day (UNIX, Linux, etc ...)
- I want to contribute back to the OpenSource community and want to help promote it by creating an attractive and friendly site for people to visit (more people more promotion, more support for pat)
- explore my creative ways and share ideas, also I stick with the front-end side of things on these side projects for now
- create mobile-friendly for more exposed for everyone
Now if you like the site, I can transfer ownership and require just a little credit

I will start a process on which I will deliver future sites for any project.

- all my projects will be on GitHub for a practical and open reason, and code can be view.
- idea: it easy to link and share my code plus it offers an opportunity for others to contribute
- transfer ownership is easy here too, and if you like you can help project donation section on Github
- Create an open-source marketing model by providing websites or web apps to promote open-source. Marketing is not bad. Its a tool like anything else the same with any language I was created, there is a reason why somethings are still around. Lets us not be biased towards anything like CMS, JS, or any other thing related technology for improving the pat and Slackware community. not trying to start a war, it wastes time and energy.

I will post the code and link as a fan-base, and it will be open-source license so anyone can use it if they like, and if Pat likes, it would be awesome, and I will transfer ownership to him, if not I least I tried.

also, note that a good design site will take in consideration the blind, low resource and even people who use lynx. saying stuff about other technology and like JS or if not broken don't it fix causes thing to be left behind, in terms of collecting technical debt in the future. what I am purpose to help the community like Slackware to evolve. listen I love all things opensource, Linux, Unix, the web. look the Slackware, the web and open-source has giving us so much in many ways. I will make the website and label un-official and if Pat like it I will handover to him and adjust any request he wants. if not the code will be up and if some want to fork it, by all mean.

2 members found this post helpful.

joescript,

I like your enthusiasm.
The best way that you can help out is to answer technical questions here at LQ and establish yourself as a trusted member of the Slackware community. Also, I suggest that you consider funding the Slackware project with either a Patreon or Paypal contribution. Please see the links in my signature.
Mr. Volkerding and the Slackware Team of developers do read the posts here. If they're interested in your help they will let you know.

3 members found this post helpful.

how does one do that?

• Provide sound answers or solutions to questions asked and issues brought on LQ.
• When making suggestions or proposals of something that you think would benefit Slackware and/or Slackware users, bring something (even a draft) that people can try. For instance it's better to provide a patch to fix something that just say "something is wrong", or if it's something new do it first at least partially, so you have an actual thing to present to your peers instead of just an idea.

OP: In this case you could provide either a modification of the current website or a new one, which would not have to be complete or perfect. Just saying "what do you think" of something not existent yet won't to bring much attention or positive reactions in my humble opinion.

2 members found this post helpful.

I totally understand, short version, put in the work. ofcourse I have a few design options and concepts that I will provide the link in the future. I just wanted to psot a few things and approach on develierable for the project. Once I have a proto-type, I will link it here and let the community decided; either way, its good practice for me. I have just been a bit swamp at work, so the last few weeks were minimal.






"actions speak louder than words"

2 members found this post helpful.

I think it says more about (your) phones than the website, if it can't even properly load and show such a simple website as Slackware. And it can't possibly be because of some crazy requirements, because the page has been like that for decades.

Write a letter to your overlords at Apple or Google instead perhaps?

Ps. My "phone" from 2009 displayed Slackware website perfectly, and it lacked many pieces of "advanced" software.

This topic comes up occasionally because there are things on the website that are severely out of date. It has given some people (mostly outside the slackware community) the idea that the project is dead, which obviously isn't true.


All I'm going to add is that at some members of the core team have chimed in and mentioned that it's a known problem, but fixing it is a different matter. As I understand it, the current website is a custom mass of PHP that was written by someone who is no longer available to maintain it. The original goal was to make things easier for Pat, but years later the exact opposite has happened.


So here we are. The community wants to offer a solution, but a community offered solution is literally the problem right now. Keep that in mind when offering to build Pat a new CMS.

1 members found this post helpful.

Clearly the website is not very high on the list of priorities. And it's probably a PITA to have to maintain a website too.
I know BDFL updates the documentation in the distro, it's an interesting thought experiment to think of a website which self updates based on such available information. And obviously KISS is good in relations to making it easier to maintain a website, so perhaps removing some sections wouldn't hurt either.

The design of the website doesn't need to be updated. The content does, however, as some pointed out in this thread. IMO it would be great if we could update the slackware.com website's content to match the current affairs (Slackware 15.0), and leave redesigns to a community site (like slackwarecommunity.com as someone mentioned above).

-- ltlnx

I 100% agree. Although it will be a little bit sad that we'll lose the ability to follow direct links from "Slackware Support" to these sites:

https://www.steubentech.com/~talon/desktop/
https://www.steubentech.com/~talon/alice_flame.html

Just for my information, can someone clarify which content needs to be updated on the website?
At least with links

1 members found this post helpful.

I didn't proofread every sentence on slackware.com, but here is the stuff that always sticks out to me.

Overview section refers to an old kernel version.
http://www.slackware.com/info/

dead 3rd party links on the Support page
http://www.slackware.com/support/

About page has several issues..
http://www.slackware.com/about/

• Alumni page seems thin, Doesn't the core team have more than 2 members?
• Chris Lumens changed to a new domain name. I guess bangmoney.com was sending the wrong message LOL
• If you are going to have a page highlighting core contributors then you have to mention Eric. You just have to

As for the hardware running the website, I vaguely remember years ago Pat mentioning that The Box had been upgraded. Or I could be conflating that with something alienbob talked about.

Anyway that's the stuff that sticks out. I'm not including wishful thinking, since there are a lot of community projects/groups that could easily be referenced. e.g. SBo, and many of the regional groups.

2 members found this post helpful.

Oh looks like the install page is very out of date as well.
http://www.slackware.com/install/


I was not aware that we had a package series for GNOME and an experimental UMSDOS-based Slackware installer. Nice.