Wiki Page Properties: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
This page contains notes about the idea of categorizing every wiki page with a type that will be used in workflows, alerts, reports, gamification, reminders, leaderboards, etc. It would add the most value if I made a mandatory rule that every page must have one and only one type classification. [[Page Type Uses]]. All of the notes from while I was developing the [[Page Type Uses]] was moved to the [[Page Type Brainstorming]] page. | This page contains notes about the idea of categorizing every wiki page with a type that will be used in workflows, alerts, reports, gamification, reminders, leaderboards, etc. It would add the most value if I made a mandatory rule that every page must have one and only one type classification. [[Page Type Uses]]. All of the notes from while I was developing the [[Page Type Uses]] was moved to the [[Page Type Brainstorming]] page. | ||
Guiding Principles | |||
* The page type should describe a page's purpose. | |||
* If it isn't an ongoing responsibility or something that is actively maintained, it is a Resource. If you frequently go 2 weeks without thinking about this, then it is a Resource. | |||
* In general, if you spend more than an hour per week doing or thinking about something, then it is probably an Area | |||
* Every Area gets a top level section in the Main Page, except Hobbies | |||
* Every Hobby gets its own area; the page for the Hobby is type: Area; area: Hobbies | |||
** A page within the Hobby will probably have a type: Reference; area: Photography | |||
* Pages assigned to the project will automatically have the areas of that project assigned to each page by default | |||
=== August 25 Decision === | === August 25 Decision === | ||
| Line 6: | Line 16: | ||
|'''Status''' | |'''Status''' | ||
|'''Description''' | |'''Description''' | ||
|'''Notes and Examples''' | |||
|- | |- | ||
|Study | |Study | ||
| | | | ||
|Notes derived from a source or structured learning | |Notes derived from a source or structured learning | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Currently being studied | |Currently being studied | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|No longer actively studied | |No longer actively studied | ||
| | |||
|- | |- | ||
|Journal | |Journal | ||
| | | | ||
|Chronological experience or reflection | |Chronological experience or reflection | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Normal journal content | |Normal journal content | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|Historical content no longer considered active | |Historical content no longer considered active | ||
| | |||
|- | |- | ||
|Idea | |Idea | ||
| | | | ||
|A concept, conclusion, insight, or synthesized thought | |A concept, conclusion, insight, or synthesized thought | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Idea currently considered relevant | |Idea currently considered relevant | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|Idea retained but no longer considered relevant | |Idea retained but no longer considered relevant | ||
| | |||
|- | |- | ||
|Project | |Project | ||
| | | | ||
|Information supporting an intended outcome | |Information supporting an intended outcome | ||
| | |||
|- | |- | ||
| | | | ||
|Inception | |Inception | ||
|Being considered/researched but not yet committed | |Being considered/researched but not yet committed | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Currently being pursued | |Currently being pursued | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|Completed, abandoned, cancelled, or dormant | |Completed, abandoned, cancelled, or dormant | ||
| | |||
|- | |- | ||
|Area | |Area | ||
| | | | ||
|Ongoing parts of my life that I develop or maintain | |Ongoing parts of my life that I develop or maintain | ||
| | |||
|- | |- | ||
| | | | ||
|Inception | |Inception | ||
|Potential Area being considered/developed | |Potential Area being considered/developed | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Ongoing responsibility or interest | |Ongoing responsibility or interest | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|No longer actively maintained | |No longer actively maintained | ||
| | |||
|- | |- | ||
|Resource | |Resource | ||
| | | | ||
|Likely to have more use in the future than today | |Likely to have more use in the future than today | ||
| | |||
|- | |- | ||
| | | | ||
|Active | |Active | ||
|Available for reference | |Available for reference | ||
| | |||
|- | |- | ||
| | | | ||
|Archived | |Archived | ||
|Retained but unlikely to be useful currently | |Retained but unlikely to be useful currently | ||
| | |||
|} | |} | ||
Revision as of 11:59, 26 August 2026
This page contains notes about the idea of categorizing every wiki page with a type that will be used in workflows, alerts, reports, gamification, reminders, leaderboards, etc. It would add the most value if I made a mandatory rule that every page must have one and only one type classification. Page Type Uses. All of the notes from while I was developing the Page Type Uses was moved to the Page Type Brainstorming page.
Guiding Principles
- The page type should describe a page's purpose.
- If it isn't an ongoing responsibility or something that is actively maintained, it is a Resource. If you frequently go 2 weeks without thinking about this, then it is a Resource.
- In general, if you spend more than an hour per week doing or thinking about something, then it is probably an Area
- Every Area gets a top level section in the Main Page, except Hobbies
- Every Hobby gets its own area; the page for the Hobby is type: Area; area: Hobbies
- A page within the Hobby will probably have a type: Reference; area: Photography
- Pages assigned to the project will automatically have the areas of that project assigned to each page by default
August 25 Decision
| Page Type | Status | Description | Notes and Examples |
| Study | Notes derived from a source or structured learning | ||
| Active | Currently being studied | ||
| Archived | No longer actively studied | ||
| Journal | Chronological experience or reflection | ||
| Active | Normal journal content | ||
| Archived | Historical content no longer considered active | ||
| Idea | A concept, conclusion, insight, or synthesized thought | ||
| Active | Idea currently considered relevant | ||
| Archived | Idea retained but no longer considered relevant | ||
| Project | Information supporting an intended outcome | ||
| Inception | Being considered/researched but not yet committed | ||
| Active | Currently being pursued | ||
| Archived | Completed, abandoned, cancelled, or dormant | ||
| Area | Ongoing parts of my life that I develop or maintain | ||
| Inception | Potential Area being considered/developed | ||
| Active | Ongoing responsibility or interest | ||
| Archived | No longer actively maintained | ||
| Resource | Likely to have more use in the future than today | ||
| Active | Available for reference | ||
| Archived | Retained but unlikely to be useful currently |
Topics and Tags
Now that Page Types and Status are confirmed, I need to think about tags/topics.
- Since capture notes will be in Cargo, on what type type will Capture exist?
- Projects and Areas could each be a Topic
- Hierarchical naming and duplicate page names
Tutorials
Two important types of pages that need to be treated special:
- Pages that help me improve a process or something about me or how I work (maybe Idea Pages)
- How to choose an investment strategy
- How to edit a video using DaVinci Resolve
- How to get more exercise
- Pages that are helpful guidelines
- Things to consider when booking a hotel
- Keyboard shortcuts in VS Code
- Best practices, tips, tutorials
Choosing Page Titles
I think I need a tutorial on choosing a Page Title
- Benefits of adding hierarchy
- Duplicate name issue
- Title case versus only FLFW caps
- Long versus short
- When to use acronyms