Knowledge Commons

Wiki Page Properties: Difference between revisions

← Older editNewer edit →
VisualWikitext
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
* Areas can have parent Areas.  Photography has Hobbies as a parent.  Yoga has Health & Fitness as a parent.
** Use this sparingly; about 10-20 active areas is a good quantity.
* A parent Area page (Household) does not have any areas assigned.
* When assigning an area to a page, the list of optional areas include all pages of type: Area; status: Active; Area: <none>
* When assigning a project to a page, the list of optional projects includes all pages of type: Project; status: Active
* All Areas (except child areas) gets a top level section in the Main Page
* 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
* Projects and Areas created, they create matching identities, but those identities are not associated with the page for the Project or Area its self
* Pages assigned to the project will automatically have the areas of that project assigned to each page by default
* Project should have at least one Area


=== August 25 Decision ===
=== August 25 Decision ===
Line 124: Line 108:
|
|
|}
|}
=== 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
* Areas can have parent Areas.  Photography has Hobbies as a parent.  Yoga has Health & Fitness as a parent.
** Use this sparingly; about 10-20 active areas is a good quantity.
* A parent Area page (Household) does not have any areas assigned.
* When assigning an area to a page, the list of optional areas include all pages of type: Area; status: Active; Area: <none>
* When assigning a project to a page, the list of optional projects includes all pages of type: Project; status: Active
* All Areas (except child areas) gets a top level section in the Main Page
* 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
* Projects and Areas created, they create matching identities, but those identities are not associated with the page for the Project or Area its self
* Pages assigned to the project will automatically have the areas of that project assigned to each page by default
* Every page that is not type: Area should have at least one Parent Area assigned.


=== August 26 Decision ===
=== August 26 Decision ===
Line 459: Line 458:
|}
|}


=== 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
Retrieved from "https://wiki.goalstriving.org/Wiki_Page_Properties"