The best way i found was obsidians import which was what i was trying to avoid. I was making standalone markdown files and after the import i needed to do some cleaning since obsidian or onenote did OCR on the images to create alt text but quotes in the alt text broke image links.
starshipwinepineapple
joined 9 months ago
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?
- Site wasn't properly reflexive for mobile
- 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
- 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.
- 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.
- 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.
Is Arch Linux the right fit for a newbie to Linux? The right answer is "it depends", not "never". Would I recommend Arch to my mom? No. Would I recommend it to my programmer colleague who already lives in the Powershell? Sure, why not.
Yup, i had a lot of people tell me that arch wasn't a good beginner distribution, and had some friends try to talk me out of it. But i was planning to move to Linux for over a year and had set up Linux servers in the past. Just hadn't used one for my main PC. I've been on arch for over a month and it's been fine. I still wouldn't recommend it to every beginner but I'm not going to say it's never appropriate.
- User devices (main workstations, phone photos, etc)
- Local NAS (sync w/ #1, backup to #3)
- Cloud backup w/ commercial provider
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 🙂
Im not familiar with doku wiki but here's a few thoughts