kisslinux / kisslinux.github.io Goto Github PK

Hi,
i love this approach of minimal site generation.

And i have a suggestion, i guess the .www folder should be copied to the webspace as it is,
so for me it makes no sense that the templates folder is in there too.

Solutions to this that came to my mind are :
(cd ../src; find . -type f -a -not -path '/.' -not -path 'templates/')
or simply move the templates folder out of the site folder.

It redirects to https://github.com/kisslinux/repo/releases/download/1.10.0, wich gives a 404 error. Github supports automatic redirect to the latest release, with the folowing format: https://github.com/user-name/repo/releases/latest/download/package, so it should be something like this: https://github.com/kisslinux/repo/releases/latest/download/kiss-chroot.tar.xz (you had the wrong format)

Your site's template footer is now obsolete :)

Now that you've re-activated, so did I re-activate my Patreon membership. But the information is a bit out-of-date.

I am a Greek/Australian developer working on a myriad of projects. Most notably the upcoming Linux distribution called KISS.

KISS Linux: https://getkiss.org

GitHub pages:

• https://github.com/dylanaraps
• https://github.com/kisslinux

Maybe something like

I am a Greek/Australian developer working on a myriad of projects. Most notably the KISS Linux distribution.

KISS Linux: https://kisslinux.org

GitHub pages:

• https://github.com/dylanaraps
• https://github.com/kisslinux

Also, it links to a Discord. Personally, I like the idea of a Discord for people sharing when they code, but that should probably be removed.

I've noticed the guidestones page has disappeared from kiss linux's website. Are the guidestones being changed? If so, what are the new ones and are there any plans on bringing them back on the website?

The webpage I'm talking about is still viewable on Dilyn's website https://k1sslinux.org/guidestones.

https://github.com/kisslinux/website/blob/4f9254fa6b6049ba747d3077c4e128f792529bba/docs/package-system.txt#L209
This line is formatted such that the edges of the box line up correctly when containing the 8 characters '&lt;&lt;', but when the page is rendered as html, those are replaced with '<<', which messes up the alignment. (https://kisslinux.org/package-system#7.0)

Mention:

• Setting up timezones.
• Setting up Xorg.
• Setting up Sound.
• System optmization.
• Fonts.
• ...

Add this to css file/embed inline using <style> tag. This will not make your site bloated and will enable auto dark mode.

@media(prefers-color-scheme:dark){html{background:#000;color:#c2c2c2}a:link{color:#8fd9f7}a:visited{color:#bea4fa}a:active{color:#f7ef51}}

Closed because of this pull request:
#30

Image hosting for the website's blog.

See #52 for rationale.

Does KISS have an IRC channel, if so, can some info be added to the website, if not, can one possible be created?

Under the 'SETTING UP DISKS' section, the text mentions to use the below links but there is only two bullet points.

Currently the website says that the second parameter is used to differentiate between a compile time dependency and a runtime one.

You can guess that a compile time dependency is marked by when the second field is filled, but it doesn't say what the second field is actually used for.

I've been browsing the new website (which btw, looks amazing and was a much needed improvement over the old one), and I noticed both the community section of the wiki and the the community repo from the install guide have been removed.

I think it's important to have at least a few links in the wiki about the existing community so new users don't feel lost after completing the initial installation. What is your opinion on this? Would you be open to this?

Just a heads up.
It's been down for a couple days.

There is a dead link to the wiki in the Bootloader section of the install guide. The link used to lead to a section on mounting UEFI variables, but has been removed.

On a fresh install, gnupg1 doesn't know about any key servers yet, so running gpg --recv-key 46D62DD9F1DE636E results in this error:

gpg: no key server known (use option --keyserver)
gpg: keyserver receive failed: bad URI

I was able to import the key by specifying the pgp.mit.edu key server

Hi, great website!

On the screenshot page, there are some images showing a variety of unique setups. I believe it might be helpful to share details about the setup to help any users who wish to quickly create similar setups or adapt components they like.

This could be achieved by replacing the hyperlink to https://github.com/dylanaraps/ with a link to https://github.com/dylanaraps/dotfiles and requesting something similar from other contributors.

It seems that after article 20200114a (in news feed) and article 20200224a (in blog feed), <guid> in feed item contains trailing slash.
When you open an article it opens link from <guid> field and it returns 404.
Previous articles did not contain it and they work fine.

I don't know about other clients, but even if they work it seems weird to have this slash when <link> doesn't.

As I understand it, kiss_path.sh was removed due to kisslinux/repo#209.

There's one or two references still hanging around to it in the docs, e.g in the install instructions: https://github.com/kisslinux/website/blob/master/site/install.txt#L852

This issue will be used for the sole purpose of hosting images for the website. The number of screenshots is growing and I'd rather not let git slow to a crawl trying to handle them.

Feel free to reply below with your own screenshots, just make sure that they're compressed so we don't slow down the website too much. :)

In here, under KISS_HOOK

In the install page of the website, the links for the kiss-chroot are dead.
I've tested it in two computers.

https://github.com/kisslinux/website/blob/master/site/package-manager.txt#L679

Issue:

After the redesign of the website, inline-code segments have a contrast of 1.16 and are almost illegible.

Example:

Fix:

Increase the contrast of inline-code to at least 7 per WCAG guidelines.

Other implications:

I didn't see any exampled of preformatted code blocks, but these elements often share styles. Check the contrast for these styles as well.

The description of fff in site/pages/projects.md is not correct.

kiss-chroot-2020.7.tar.xz.sha256 not found file : kiss-chroot.tar.xz, De correct file name are kiss-chroot-2020.7.tar.xz.

% ver=2020.7
% url=https://github.com/kisslinux/repo/releases/download/$ver
% wget "$url/kiss-chroot-$ver.tar.xz"
kiss-chroot-2020.7.tar.xz        100%[=========================================================>]  35.27M  9.25MB/s    in 4.3s

2020-08-03 18:22:39 (8.26 MB/s) - ‘kiss-chroot-2020.7.tar.xz’ saved [36978988/36978988]

% wget "$url/kiss-chroot-$ver.tar.xz.sha256"
kiss-chroot-2020.7.tar.xz.sha256 100%[=========================================================>]      85  --.-KB/s    in 0s

2020-08-03 18:22:47 (4.32 MB/s) - ‘kiss-chroot-2020.7.tar.xz.sha256’ saved [85/85]

% sha256sum -c < kiss-chroot-$ver.tar.xz.sha256
sha256sum: kiss-chroot.tar.xz: No such file or directory
kiss-chroot.tar.xz: FAILED open or read
sha256sum: WARNING: 1 listed file could not be read

Edit the page https://k1ss.org/style

https://website.com/fix-build.patch
=>
https://example.com/fix-build.patch

rationale:

example.com, example.net, example.org, and example.edu are second-level domain names reserved for documentation purposes and examples of the use of domain names.
-- https://en.wikipedia.org/wiki/Example.com

(Sorry, I don't know how to use git or github well enough to do a pull request.)

In the third bullet point you use the work 'packages' instead of 'files'

I could just be missing the doc page or scripts for building the initial tarball, but I think it would be useful to see how it's built and would allow people to fork the distro much more easily.

The liberation fonts are the ones used in the official install instructions https://k1ss.org/install#13.0 yet there seems to be an issue with using this font on the website:

BTW, I love the website and kiss is the best distro I've used :]

All wiki links intended as absolute links are interpreted as relative links by line 14 in the make script. For example, on https://k1ss.org/wiki/software/git there is a "@/help/adding-a-page" that should be linking to "/wiki/help/adding-a-page" but is instead linking to "/wiki/software/help/adding-a-page".

The simplest solution I can think of is treating a link as absolute if the page name is preceded by a directory name, and as relative otherwise. But this would limit the directory depth on the wiki.

The links are broken to kiss-chroot and chroot helper on https://k1ss.org/install