Today I Learned
What did you learn today? Share it with us!
We learn something new every day. This is a community dedicated to informing each other and helping to spread knowledge.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with TIL. Linking to a source of info is optional, but highly recommended as it helps to spark discussion.
** Posts must be about an actual fact that you have learned, but it doesn't matter if you learned it today. See Rule 6 for all exceptions.**
Rule 2- Your post subject cannot be illegal or NSFW material.
Your post subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-TIL posts.
Provided it is about the community itself, you may post non-TIL posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you vocally harass or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Partnered Communities
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
view the rest of the comments
Yeah, I noticed that when you choose a format, it's that format or delete and start over with the new format. That would be a neat feature at least, but I can see the troubles of properly reformatting the file into the new format you want. Luckily, I'm just using it for giggles and a little bit of learning! Haha!
Keep on using it, it's pretty but, as a developer, I always prefer solutions like GitLab where the markdown is stored in a git repository.
I've never developed or anything like that. Just fiddled around with HTML, CSS, and markdown before. Can you explain the upsides to the git structure? I've never used it, so I'm interested to know from someone who has used it!
Git is what's known as "Version Control Software" which basically means that it keeps track of the changes you make.
It's primarily used for software development, and where it shines is when multiple people are collaborating on a project which will receive many changes. You can create a "branch" of the project with the changes you want to "commit" and then after they're reviewed in a "pull request" you can "merge" them back inyo the main branch. If at any point in the process you discover that the changes cause issues, a history allows you to "revert" those changes back to what you had previously.
As you can probably see, there's a fair bit of terminology in git. It's a powerful tool that has a learning curve in order to use it.
While git is primarily used in software development, it doesn't have to be. In fact, you could use it for any collection of files that receive changes. It's not uncommon to see it used for technical writing , wikis, or large collaborative documents. I recall seeing a compelling argument that it could be used for drafting legislation, although I'm not aware of any government which uses it for that purpose.
Some people argue about whether or not you should use git with non-text files because the changes are much larger, but you don't have to rigidly follow dogma.
I knew a guy who liked to use git for his RPG campaign notes. The main branch held his setting info, and when he'd run a game he'd create a new branch. If he was pleased with the game and wanted to enshrine it in canon, he'd merge it into main. Otherwise, he could leave the branch alone, but he'd still always be able to go back and look at the adventure with the details of the setting as it was at that time. I thought it was overkill, but he had fun.