Knowledge Commons

Wiki Page Properties: Difference between revisions

← Older edit
VisualWikitext
No edit summary
No edit summary
 
(17 intermediate revisions by the same user not shown)
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 properties assigned to every wiki page that will be used in workflows, alerts, reports, gamification, reminders, leaderboards, etc.  All of the notes from while I was developing the [[Page Type Uses]] was moved to the [[Page Type Brainstorming]] page.


=== Guiding Principles ===
=== ChatGPT Specs ===
* The page type should describe a page's purpose. 
Based on a conversation where we worked out the details, ChatGPT created this [[WikiFam Requirements and Specifications]]
* 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 ===
=== Wiki Mode ===
When new users create their wikis, they will have two options (perhaps more in the future):
 
* Standard Wiki: A flexible MediaWiki experience with optional starter content.
* PARA Wiki: A structured personal knowledge management system
 
=== Page Type and Status ===
The table below shows each of the six default Page Types, the allowable Statuses for each, and a description of the content.
{| class="wikitable"
{| class="wikitable"
|'''Page Type'''
|'''PageType'''
|'''Status'''
|'''PageStatus'''
|'''Description'''
|'''Description'''
|'''Notes and Examples'''
|'''Notes'''
|-
|-
|Study
|Study
|
|
|Notes derived from a source or structured learning
|Notes derived from a source or structured learning
|
|Knowledge I'm acquiring from a particular source.
|-
|-
|
|
Line 35: Line 36:
|
|
|Chronological experience or reflection
|Chronological experience or reflection
|
|What happened or what I experienced.
|-
|-
|
|
Line 50: Line 51:
|
|
|A concept, conclusion, insight, or synthesized thought
|A concept, conclusion, insight, or synthesized thought
|
|An understanding that I have developed
|-
|-
|
|
Line 65: Line 66:
|
|
|Information supporting an intended outcome
|Information supporting an intended outcome
|
|An outcome I'm working toward.
|-
|-
|
|
Line 85: Line 86:
|
|
|Ongoing parts of my life that I develop or maintain
|Ongoing parts of my life that I develop or maintain
|
|Something I maintain or develop over time.
|-
|-
|
|
Line 105: Line 106:
|
|
|Likely to have more use in the future than today
|Likely to have more use in the future than today
|
|Information I have collected that may be useful
|-
|-
|
|
Line 118: Line 119:
|}
|}


=== Topics and Tags ===
=== Guiding Principles for Page Properties. ===
Now that Page Types and Status are confirmed, I need to think about tags/topics.
* Every page has a Type and Status. Pages can also be connected to Areas, Projects, and Topics.
* Since capture notes will be in Cargo, on what type type will Capture exist?
** Type = How will I use this page?
* Projects and Areas could each be a Topic
** Status = Is it currently relevant/active?
* Hierarchical naming and duplicate page names
** Area = What ongoing part of my life does it support?
** Project = What outcome does it support?
** Topic = What is it about?
* There are six default page types; more may be added later.  Users cannot add new Types.
* PageStatus determines whether a page is included in default views, searches, selectors, reports, and workflows. Archived pages remain accessible but may be excluded by default. Every page is assigned one and only one Status.
* There are three default page statuses; more may be added later.  Users cannot add new Statuses.
* These guidelines are offered to new users to help them determine what to create for Areas and Topics.
*# An ''area'' is an ongoing responsibility, activity, or something you intentionally maintain or develop over time
*# A ''topic'' is a subject that can connect multiple pages but does not represent an ongoing responsibility or activity you maintain.
* Pages will also have type-specific metadata and may have topic-specific metadata.
* An Area may have zero or one Parent Area.
* Any page with a type other than Area may have zero or more Related Areas.
* Areas can have parent Areas.  Photography has Hobbies as a parent.  Yoga has Health & Fitness as a parent.
* A top-level Area has no ParentArea.
* When assigning an area to a page, the list of optional areas includes all pages of type: Area; status: Active.  Users can optionally check a box to include Archived pages in the list of available options.
* When assigning a project to a page, the list of optional projects includes all pages of type: Project; status: Active. Users can optionally check a box to include Archived pages in the list of available options.
* PageType and PageStatus are mandatory, and each has exactly one value.  Area and Topic are optional; we recommend a maximum of three each, but there is no restriction on the quantity.
* A hobby that the user actively practices or develops should be represented as an Area, optionally beneath the Hobbies Area.
* When a project is assigned to a page, the related areas of the project are also assigned to the page by default.  Users may remove them and/or add new Areas and/or Topics.
* Every non-Area page should normally have at least one Related Area, Related Project, or Related Topic. Pages that do not are considered unclassified and are flagged for review.


=== Tutorials ===
=== Default Pages and their Properties ===
Two important types of pages that need to be treated special:
The table below shows each of the optional pages (along with their properties) that the user may choose to import during the [[New User Onboarding]] process.
 
{| class="wikitable"
* Pages that help me improve a process or something about me or how I work (maybe Idea Pages)
|'''PageName'''
** How to choose an investment strategy
|'''PageType'''
** How to edit a video using DaVinci Resolve
|'''PageStatus'''
** How to get more exercise
|'''ParentArea'''
* Pages that are helpful guidelines
|'''RelatedAreas'''
** Things to consider when booking a hotel
|'''RelatedProjects'''
** Keyboard shortcuts in VS Code
|'''RelatedTopics'''
** Best practices, tips, tutorials
|-
|Personal
|Area
|Active
|
|
|
|
|-
|Long-term goals
|Resource
|Active
|
|Personal
|
|
|-
|Weekly tasks
|Resource
|Active
|
|Personal
|
|
|-
|Gift ideas
|Resource
|Active
|
|Personal
|
|
|-
|Daily Journal
|Journal
|Active
|
|Personal
|
|
|-
|Fitness & Nutrition
|Area
|Active
|
|
|
|
|-
|Tips for healthy eating
|Resource
|Active
|
|Fitness & Nutrition
|
|
|-
|Yoga
|Area
|Active
|Fitness & Nutrition
|
|
|
|-
|Why yoga helps me
|Idea
|Active
|
|Fitness & Nutrition
|
|
|-
|Household
|Area
|Active
|
|
|
|
|-
|Products
|Resource
|Active
|
|Household
|
|
|-
|Household Technology
|Resource
|Active
|
|Household
|
|
|-
|Subscriptions
|Resource
|Active
|
|Household
|
|
|-
|Family
|Area
|Active
|
|
|
|
|-
|Family traditions
|Resource
|Active
|
|Family
|
|
|-
|Family tree
|Resource
|Active
|
|Family
|
|
|-
|Friends & Social Activities
|Area
|Active
|
|
|
|
|-
|Poker night planning
|Resource
|Active
|
|Friends & Social Activities
|
|
|-
|Why Small Gatherings Are More Enjoyable
|Idea
|Active
|
|Friends & Social Activities
|
|
|-
|Volunteering
|Area
|Active
|
|
|
|
|-
|Past volunteering
|Resource
|Active
|
|Volunteering
|
|
|-
|Volunteering opportunities
|Resource
|Active
|
|Volunteering
|
|
|-
|Vehicles
|Area
|Active
|
|
|
|
|-
|Honda Accord 2025
|Resource
|Active
|
|Vehicles
|
|
|-
|Vehicles being considered for purchase
|Resource
|Active
|
|Vehicles
|
|
|-
|Learning
|Area
|Active
|
|
|
|
|-
|List of schools & courses attended
|Resource
|Active
|
|Learning
|
|
|-
|List of books I have read
|Resource
|Active
|
|Learning
|
|
|-
|Intro to Python
|Study
|Active
|
|Learning, Career
|Complete course on Python
|Programming, Python
|-
|Psychology 103
|Study
|Active
|
|Learning
|University Degree
|Freshman Courses
|-
|Music Theory 202
|Study
|Active
|
|Learning
|University Degree
|Freshman Courses
|-
|Travel & Vacations
|Area
|Active
|
|
|
|
|-
|Bucket list
|Resource
|Active
|
|Travel & Vacations
|
|
|-
|Past vacations
|Resource
|Active
|
|Travel & Vacations
|
|
|-
|Spain Vacation Journal
|Journal
|Active
|
|Travel & Vacations
|
|
|-
|Travel loyalty programs
|Resource
|Active
|
|Travel & Vacations
|
|
|-
|Entertainment
|Area
|Active
|
|
|
|
|-
|Concerts I might want to see
|Resource
|Active
|
|Entertainment
|
|
|-
|Concert Journal
|Journal
|Active
|
|Entertainment
|
|
|-
|Movies to rewatch
|Resource
|Active
|
|Entertainment
|
|
|-
|Hobbies
|Area
|Active
|
|
|
|
|-
|Photography
|Area
|Active
|Hobbies
|
|
|
|-
|Canon EOS R10
|Resource
|Active
|
|Photography
|
|
|-
|Understanding Exposure by Bryan Peterson
|Study
|Active
|
|Photography
|
|
|-
|Tips for Low Light Photography
|Resource
|Active
|
|Photography
|
|
|-
|Cooking
|Area
|Active
|Hobbies
|
|
|
|-
|Career
|Area
|Active
|
|
|
|
|-
|Skills development
|Area
|Active
|Career
|
|
|
|-
|Potential employers
|Resource
|Active
|
|Career
|
|
|-
|Create family vacation photo book
|Project
|Active
|
|Family, Photography
|
|
|-
|Replace kitchen floor
|Project
|Active
|
|Household
|
|
|-
|Plan Italy vacation
|Project
|Active
|
|Travel & Vacations, Family
|
|
|-
|Hotels in Rome
|Resource
|Active
|
|Travel & Vacations, Family
|Plan Italy vacation
|
|-
|Complete course on Python
|Project
|Active
|
|Career, Learning
|
|
|-
|University Degree
|Project
|Active
|
|Learning
|
|
|}


=== Choosing Page Titles ===
=== PARA Wiki ===
I think I need a tutorial on choosing a Page Title
Please create a new wiki based on demo.goalstriving.org that enforces page properties and uses dynamic content.  Assign each of the properties in the table above to the pages.  The slug should be para, and the users with demo access should have the same level of access to para.


* Benefits of adding hierarchy
Please remove the page histories from demo and para, and also the redirect links that were created when pages were renamed.
* 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"