starshipwinepineapple

This is something that doesn't really need to be self hosted unless you're wanting the experience. You just need:

1. Static website builder. I use hugo but there's a few others like jekyll, astro
2. Use a git forge (github, gitlab, codeberg).
3. Use your forges Pages feature, there's also cloudflare pages. Stay away from netlify imo. Each of these you can set up to use your own domain

So for my website i just write new content, push to my forge, and then a pipeline builds and releases the update on my website.

Where self hosting comes into play is that it could make some things with static websites easier, like some comment systems, contact forms, etc. But you can still do all of this without self hosting. Comments can be handled through git issues (utteranc.es) and for a contact form i use 'hero tofu' free tier. In the end i don't have to worry about opening access to my ports and can still have a static website with a contact form. All for free outside of cost of domain.

Im not familiar with doku wiki but here's a few thoughts

• privacy policy is good to have regardless of what you do with rest of my comments
• your site is creating a cookie "dokuwiki" for user tracking.
• cookie is created regardless of user agreement, rather than waiting for acceptance (implied or explicit agreement). As in i visit the page, i click nothing and i already have the dokuwiki cookie.
• i like umami analytics for a cookieless google analytics alternative. They have a generous free cloud option for hobby users and umami is also self hostable. Then you can get rid of any banner.

So only good tutorials/ guides are allowed?

How does one get from shitty to good if they can't try to begin with?

Does this apply to other things, like coding, as well?

1. Site wasn't properly reflexive for mobile
2. If this is a portfolio then i would remove a lot of stuff like "watch list" and "current obsession". The focus should be on your work and future projects
3. Notes are ok for a start but can be improved. I think a "posts" or "blog" would be better section title, and the content should try to teach something you've learned rather than be the notes you took for a subject. The difference is that teaching reinforces your understanding of the topic. So pick something smaller from those topics and teach it. I wouldn't redo your current notes necessarily, but going forward i would pick a more focused topic and teach.
4. i would then move the "blog" or "posts" to your front page to show the most recent content and then link to /posts where the rest of it can be found. Or highlight projects on front page instead depending on what you want focus to be.
5. move your front page content to a more "resume" section that includes a section for the tools you know. And still think about the length/space of this page. Like a printed resume, too long is bad. So make sure it outlines things nicely

Overall if it was just a personal site id say its ok. But as a portfolio site you have some work to make it align with your goals. Good luck!

What is the point in being Archbased and only now supporting Btrfs out the box?

It sounds like ext4 is still an option during install, the change is just that the default filesystem is btrfs.

1. User devices (main workstations, phone photos, etc)
2. Local NAS (sync w/ #1, backup to #3)
3. Cloud backup w/ commercial provider

They added 2 weeks to it.

Here's a txt summary of the books

And a shorter txt summary

I have had the same experience. Have used all three at some point but mostly use nginx for new servers

It's also lots of work to make free and open source projects, which is why i say good bug reports are a valuable type of contribution. It is a type of contribution. Imo setting up a free account is the least thing someone can do if they use the project.

And anyone who cares about privacy can use junk data and one time email (this should just be standard practice for anyone that cares and why i didn't mention it). 2fa is a small issue too IMO.

I don't particularly care for github either but if a project is on github then that's how the maintainers are expecting contributions--if you want to help in some way, or want your bug fixed, then you'll need an account or try contacting them in other way.

No, but think of it this way-- creating good bug reports is a valuable type of contribution for open source projects. If you aren't able to fix the issue yourself then it is still appreciated to take the time to write up a good bug report (describe the issue, the expected result, the actual result, and steps to reproduce). So don't let a free account stand in your way 🙂

(Not an admin)

Do you mean blogging literally within lemmy, or linking to an external website? (Edit- i see you mean within lemmy to cross post to reddit. Leaving rest of my post for some thoughts anyway)

My advice would be to set up a static website and use that for your blog. like hugo but there's a few good options out there to generate static websites. This way if an instance ever does disappear then you still own your content. This also means you aren't limited to a specific community and could share a post where it most directly relates rather than just an individual community where you dump everything.

If you're wanting comments directly on your posts then some people have integrated comments into their blogs by using a federated platform (one example using mastodon). So for instance they make a post on lemmy or mastodon/etc and then in their blog they link the blogpost to it. Now there can be discussion on your blog/lemmy and you aren't at risk of losing so your posts. There's also other ways to do comments like utteranc.es or remark42 too.

tldr IMO if you're wanting to build your own blog/platform its better to have ownership of it and not keeping it only on someone else's server.