re-work file/folder layout slightly ; add more detail to organizers page ; add bujo/gtd sub pages
This commit is contained in:
parent
1938167450
commit
072e8e223d
|
@ -11,4 +11,4 @@ categories:
|
|||
- blog
|
||||
---
|
||||
|
||||
We have published guidelines on submitting contributions to the site [here]({{< ref "/tips/faq/_contributing" >}})
|
||||
We have published guidelines on submitting contributions to the site [here]({{< ref "/tips/faq-contributing" >}})
|
|
@ -96,7 +96,7 @@ We have tried to keep tags to a well curated list that help tie many different `
|
|||
|
||||
Given how many words have large numbers of synonyms (alternatives), we have tried to stick to single tags for single concepts.
|
||||
|
||||
Please review the main tag list [here](/tags) prior to creating a new tag. If one is missing, please add it.
|
||||
Please review the main tag list [here](/tags) (warning: this list can be large and take awhile to load) prior to creating a new tag. If one is missing, please add it.
|
||||
|
||||
Long term we hope to build a tag glossary to enhance discovery, search and synonym management. If/when this glossary is created, we will update our guidelines related to tagging.
|
||||
|
||||
|
@ -106,7 +106,7 @@ Long term we hope to build a tag glossary to enhance discovery, search and synon
|
|||
|
||||
If you are cross referencing information you can use the following code.
|
||||
|
||||
<code>[Link Text]]({{< ref "[category]/[file].md" >}})</code> where `[category]` is the category you defined and `[file]` is the markdown file name with the content you would like to reference.
|
||||
<code>[Link Text]]({{< ref "[category]-[file]" >}})</code> where `[category]` is the category you defined and `[file]` is the markdown file name with the content you would like to reference.
|
||||
|
||||
Please use this format for cross references between content pages. It helps us better manage cross references between content pages over time.
|
||||
|
||||
|
@ -118,10 +118,10 @@ Files and folders are setup with the following overall layout.
|
|||
|
||||
``` txt
|
||||
/content/
|
||||
tips/category/
|
||||
index.md
|
||||
topic_1.md
|
||||
topic_2.md
|
||||
tips/
|
||||
category-topic_1.md
|
||||
category-topic_2.md
|
||||
category-topic_3/index.md
|
||||
posts/yyyy-MM-dd-title.md
|
||||
yyyy-MM-dd-title/index.md
|
||||
```
|
||||
|
@ -130,7 +130,7 @@ Files and folders are setup with the following overall layout.
|
|||
|
||||
### Tips Directory
|
||||
|
||||
The `tips` directory contains the main knowledge base data. Each folder is a dedicated `Category` an the `index.md` file is the `Stub` with links out to the topics (`topic_1.md`, `topic_2.md`, etc).
|
||||
The `tips` directory contains the main knowledge base data. Each file represents a different page on the site and they are named using the format `[category]-[title].md` with `[category]` being the category set in the page metadata and `[title]` being the title set in the page metadata.
|
||||
|
||||
This allows us to easily cross reference information within a category (see [here]({{< ref "#cross-references" >}}) for how to cross reference pages) and keep the topic file names from colliding if there is any overlap between categories.
|
||||
|
||||
|
@ -138,6 +138,8 @@ This rigid, tree'd structure is imposed by Hugo and we have adapted our file and
|
|||
|
||||
This is also why we can have *only one* primary category for content currently.
|
||||
|
||||
We will also use `Page Bundles` ([Hugo docs](https://gohugo.io/content-management/page-bundles/)) for content that includes non-textual content or download links. `Page Bundles` are just folders with an `index.md` file and related assets. The `index.md` file is the main content and any files stored next to `index.md` can be easily referenced directly from `index.md`. This is particularly helpful for managing image assets and keeping them organized.
|
||||
|
||||
{{< back_to_top >}}
|
||||
|
||||
### Posts Directory
|
41
content/tips/organizers-bujo.md
Normal file
41
content/tips/organizers-bujo.md
Normal file
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
title: Bullet Journal
|
||||
author:
|
||||
- KemoNine
|
||||
publishDate: 2023-03-20
|
||||
lastMod: 2023-03-20
|
||||
toc: true
|
||||
draft: false
|
||||
categories:
|
||||
- tips
|
||||
- organizer
|
||||
tags:
|
||||
- bujo
|
||||
---
|
||||
|
||||
## Changelog
|
||||
{{< back_to_top >}}
|
||||
|
||||
{{< changelog >}}
|
||||
{{< change 2023-03-20 "Initial creation" >}}
|
||||
{{< /changelog >}}
|
||||
|
||||
{{< end_section >}}
|
||||
|
||||
## Considerations
|
||||
{{< back_to_top >}}
|
||||
|
||||
When it comes to [Bullet Journals](https://bulletjournal.com/) the biggest and only consideration is: "does it work for you?".
|
||||
|
||||
There are many bullet journal examples readily available for review and inspiration. The hard part is figuring out which elements work best for you, the individual.
|
||||
|
||||
{{< end_section >}}
|
||||
|
||||
## Learning Curve
|
||||
{{< back_to_top >}}
|
||||
|
||||
Due to the open ended nature of analog organizers there can be a steep learning curve. Bullet Journal doesn't have a super steep learning curve but the sheer volume of different approaches can be a big problem for getting under way.
|
||||
|
||||
It may be wise to start with a pre-made, mass produced Bullet Journal instead of trying to forge your own path from the start.
|
||||
|
||||
{{< back_to_top >}}
|
32
content/tips/organizers-gtd.md
Normal file
32
content/tips/organizers-gtd.md
Normal file
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: Getting Things Done (GTD)
|
||||
author:
|
||||
- KemoNine
|
||||
publishDate: 2023-03-20
|
||||
lastMod: 2023-03-20
|
||||
toc: true
|
||||
draft: false
|
||||
categories:
|
||||
- tips
|
||||
- organizer
|
||||
tags:
|
||||
- gtd
|
||||
---
|
||||
|
||||
## Changelog
|
||||
{{< back_to_top >}}
|
||||
|
||||
{{< changelog >}}
|
||||
{{< change 2023-03-20 "Initial creation" >}}
|
||||
{{< /changelog >}}
|
||||
|
||||
{{< end_section >}}
|
||||
|
||||
## Considerations
|
||||
{{< back_to_top >}}
|
||||
|
||||
[Getting Things Done](https://gettingthingsdone.com/) is a well known, highly utilized organizational system by many humans.
|
||||
|
||||
Instead of dedicating a space here on the topic, we recommend heading to the main GTD website as well as looking for paper notebooks or applications that implement the GTD organizational system.
|
||||
|
||||
{{< back_to_top >}}
|
|
@ -47,6 +47,7 @@ Please keep this in mind as you review organizational systems. Use what works fo
|
|||
- Very flexible or rigid based on how much of the standard system you use
|
||||
- Can be overhwelming as there is a lot of published info and ideas on the internet
|
||||
- Best results seen when a loose structure is preferred
|
||||
- [Additional Reading]({{< ref "organizers-bujo" >}})
|
||||
|
||||
{{< back_to_top >}}
|
||||
|
||||
|
@ -58,6 +59,7 @@ Please keep this in mind as you review organizational systems. Use what works fo
|
|||
- Difficult to adapt
|
||||
- Easy to start using but can quickly overhwelm due to the rigid and structured workflow
|
||||
- Best results seen when a rigid structure and workflow are preferred
|
||||
- [Additional Reading]({{< ref "organizers-gtd" >}})
|
||||
|
||||
{{< back_to_top >}}
|
||||
|
Loading…
Reference in a new issue