mirror of
https://github.com/bramses/bramses-highly-opinionated-vault-2023.git
synced 2025-02-26 07:53:55 +00:00
vault backup: 2022-12-12 23:05:21
This commit is contained in:
@@ -1,5 +1,17 @@
|
||||
{
|
||||
"recentFiles": [
|
||||
{
|
||||
"basename": "2022-Q4",
|
||||
"path": "Calendar/Quarterly/2022-Q4.md"
|
||||
},
|
||||
{
|
||||
"basename": "2022-W51",
|
||||
"path": "Calendar/Weekly/2022-W51.md"
|
||||
},
|
||||
{
|
||||
"basename": "2022-12-11",
|
||||
"path": "Calendar/Daily/2022-12-11.md"
|
||||
},
|
||||
{
|
||||
"basename": "README",
|
||||
"path": "README.md"
|
||||
@@ -10,7 +22,7 @@
|
||||
},
|
||||
{
|
||||
"basename": "2022-12-12",
|
||||
"path": "Daily/2022-12-12.md"
|
||||
"path": "Calendar/Daily/2022-12-12.md"
|
||||
},
|
||||
{
|
||||
"basename": "Test Project",
|
||||
@@ -72,10 +84,6 @@
|
||||
"basename": "2022-12-11--12-00-00",
|
||||
"path": "Inbox/Computer Capture/2022-12-11--12-00-00.md"
|
||||
},
|
||||
{
|
||||
"basename": "2022-12-11",
|
||||
"path": "Daily/2022-12-11.md"
|
||||
},
|
||||
{
|
||||
"basename": "Daily",
|
||||
"path": "Templates/Daily.md"
|
||||
|
||||
18
.obsidian/workspace.json
vendored
18
.obsidian/workspace.json
vendored
@@ -13,7 +13,7 @@
|
||||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"file": "Calendar/Quarterly/2022-Q4.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
}
|
||||
@@ -102,7 +102,7 @@
|
||||
"state": {
|
||||
"type": "backlink",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"file": "Calendar/Quarterly/2022-Q4.md",
|
||||
"collapseAll": false,
|
||||
"extraContext": false,
|
||||
"sortOrder": "alphabetical",
|
||||
@@ -119,7 +119,7 @@
|
||||
"state": {
|
||||
"type": "outgoing-link",
|
||||
"state": {
|
||||
"file": "README.md",
|
||||
"file": "Calendar/Quarterly/2022-Q4.md",
|
||||
"linksCollapsed": false,
|
||||
"unlinkedCollapsed": true
|
||||
}
|
||||
@@ -142,7 +142,7 @@
|
||||
"state": {
|
||||
"type": "outline",
|
||||
"state": {
|
||||
"file": "README.md"
|
||||
"file": "Calendar/Quarterly/2022-Q4.md"
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -185,15 +185,15 @@
|
||||
},
|
||||
"active": "382c94a56533417c",
|
||||
"lastOpenFiles": [
|
||||
"Calendar/Weekly/2022-W51.md",
|
||||
"Calendar/Daily/2022-12-11.md",
|
||||
"README.md",
|
||||
"Computed/Tasks.md",
|
||||
"Daily/2022-12-12.md",
|
||||
"Calendar/Daily/2022-12-12.md",
|
||||
"_PARA/Projects/Test Project/Test Project.md",
|
||||
"_PARA/Projects/Test Project/Scratchpad.md",
|
||||
"_PARA/Projects/Test Project/Resources.md",
|
||||
"_PARA/Projects/Test Project 2/Resources.md",
|
||||
"_PARA/Projects/Test Project 2/Test Project 2.md",
|
||||
"202212090136.md",
|
||||
"202212122239.md",
|
||||
"202212120002.md"
|
||||
"_PARA/Projects/Test Project 2/Test Project 2.md"
|
||||
]
|
||||
}
|
||||
@@ -376,7 +376,7 @@ In BHOV-2023, Antifragility means that as your vault evolves you shouldn't feel
|
||||
|
||||
## Version Control Systems
|
||||
|
||||
*Version Control Systems* like Git and SVN are specialized programs that track in history what happened to a particular file. For example, click this link to see a secret sentence that used to live right here:
|
||||
*Version Control Systems* like Git and SVN are specialized programs that track in history what happened to a particular file. For example, click this link to see a secret sentence that used to live right here: https://github.com/bramses/bramses-highly-opinionated-vault-2023/commit/bbb68cbfd5e224f3a2a4b3022afc73364c236233?diff=split
|
||||
|
||||
These changes are particularly useful to software engineering teams who need to trace the history of a working block of code. For our case in BHOV-2023, Git is mainly used for two things: file versioning and light publishing capability.
|
||||
|
||||
@@ -558,6 +558,7 @@ Great! Now that that's out of the way, we can finally get to running the vault,
|
||||
2. Download into your local machine
|
||||
3. Open the vault and rename it to whatever you want and open it in Obsidian
|
||||
4. Before you commit anything to GitHub, make sure you edit `.gitignore` to match what you want to publish. Doing this early will save you headaches down the road if you decide to publish (*part*) of your vault
|
||||
5. Depending on when you clone this repo, you may want to check plugins for updates. In the bottom right corner, the plugin Plugin Update Tracker will alert you if any plugins in BHOV-2023 need to be updated
|
||||
|
||||
|
||||
## After You're Up and Running
|
||||
@@ -637,6 +638,8 @@ In the creation of BHOV-2023, the author was in the middle of his own migration
|
||||
|
||||
First, the the questions you should ask yourself is: what about your current vault is necessary, what you'd like to change, and where you ideally want to be after migrating. Keep in mind, many of the tricks and strategies used in BHOV-2023 can be inserted into existing vaults, so you might not even need to make a full move!
|
||||
|
||||
After following the traditional [installation section above](#installation), the first thing you're probably going to want to do is start migrating a few notes you already have into the correct buckets. Once you get a feel for that manually, try to move your outside vault workflows (Alfred, Readwise, etc) to point to BHOV-2023. This will help facilitate the transition without a drastic switch over as new notes will be placed into BHOV-2023 and your existing workflows will be maintained in your old vault.
|
||||
|
||||
## Settings
|
||||
|
||||
`todo`
|
||||
|
||||
Reference in New Issue
Block a user