Knowledge Commons - User contributions [en]

Default Wiki Pages

2026-07-28T19:53:34Z

Mshell:

This page shows the default pages for all newly created wikis:

Welcome note at the top.

=== Tutorials ===

* [[Wiki Formatting Examples]]
* [[Creating and editing pages]]
* [[Advanced Topics]]

=== Notes ===

* Household
** [[Products]]
** [[Technology]]
* Vacations
** [[Vacation Bucket List|Bucket List]]
** [[Vacations Upcoming|Upcoming]]
* Entertainment
** [[Books]], [[Theatrical Performances|Theater]], [[Concerts & Live Events|Concerts]]
* Hobbies
** [[Photography]]
* Learning
** [[High School]]
** [[University]]
** [[Self Learning]]
* Career Development
** [[Skills Development]]
** [[Job Search]]

Possible Names

2026-07-22T22:57:10Z

Mshell:

I built this proof-of-concept design using the name goalstriving.org, because I already owned that domain. Before I build the production system, we need to pick a name, register the domain, and form the nonprofit. Realistically, that could all happen within two or three months.

I am open to name suggestions. Here are a few of mine:

* myknowledgetree.org
* everknowledge.org
* goalstriving.org
* KnowledgeGarden.net
* knowledgetree.wiki
* gardenofknowledge.net, gardenofknowledge.info, gardenofknowledge.wiki
These names need to be added to the voting on the home page.
* LifeAndLearning.wiki
* Mywiki.life
* Lifenotes.wiki
* myKnowledge.org (available for $4,000)
* webOfKnowledge.wiki
* wokwiki.org (wok = web of knowledge)
* wok.wiki ($150/yr)
* mywok.org
* mywok.wiki

Default Wiki Pages

2026-07-22T19:36:30Z

Mshell: Created page with "This page shows the default pages for all newly created wikis: Welcome note at the top. === Tutorials === * Examples of many features * Creating and editing pages * Advanced Topics === Notes === * Household ** Products ** Technology * Vacations ** Bucket List ** Upcoming * Entertainment ** Books, Theater, Concerts * Hobbies ** Photography * Learning..."

This page shows the default pages for all newly created wikis:

Welcome note at the top.

=== Tutorials ===

* Examples of many features
* Creating and editing pages
* Advanced Topics

=== Notes ===

* Household
** [[Products]]
** [[Technology]]
* Vacations
** [[Vacation Bucket List|Bucket List]]
** [[Vacations Upcoming|Upcoming]]
* Entertainment
** [[Books]], [[Theatrical Performances|Theater]], [[Concerts & Live Events|Concerts]]
* Hobbies
** [[Photography]]
* Learning
** [[High School]]
** [[University]]
** [[Self Learning]]
* Career Development
** [[Skills Development]]
** [[Job Search]]

Main Page

2026-07-22T19:26:11Z

Mshell: /* Project Details */

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Invite People to Create a Wiki]]
** Define the [[Default Wiki Pages]]
* Future Enhancements
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Usage Notes
** [[MediaWiki Extensions]]
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Board of Directors]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Community Restrictions]]
** [[Timeline]]

Possible Names

2026-07-21T22:41:21Z

Mshell:

Higher Education

2026-07-20T23:36:04Z

Mshell:

[[File:DukeWEMBAnotes.jpg|alt=A stack of all my notebook binders from my MBA courses at Duke University.|thumb|A stack of all my notebook binders from my MBA courses at Duke University.]]
'''REMINDER: I will not communicate to anyone (including Steve & Erin) about any of this until we have over 100 users and are on the production platform. I don't mention anything to Steve & Erin about transparency. For now, limit to Gavin, Elias, and their friends.'''

In 2011, I graduated from the Executive MBA program at Duke University. For each course, students were given a three-ringed binder notebook with the reading and assignments. We were not allowed to have laptops in class, so all my notes were hand written right on the pages of those binders. I moved to New York City after completing the program to a tiny apartment and didn’t have room for them anymore, so I went through each one and transcribed the most important notes into a digital note taking tool. I took this picture after I stacked them all in the refuse room of my apartment building. Although I had copied the most important notes, I knew that I was losing a tremendous amount of knowledge.

Anyone who has ever thrown out text books or notebooks containing handwritten notes knows the pain of knowing that some of that knowledge is gone forever.

==== Potential Uses ====

* Students each have a personal wiki where they document all their class notes, reading notes, papers, and projects
* Each course has a project wiki owned by the professor and connections with all students. This would allow easy sharing of the syllabus, course notes, assignments, etc.

==== Comparison to an LMS ====

* Most institutions of higher education use a Learning Management System (LMS) for submitting assignments and distributing grades. Many have additional features as well.
* The LMS is not designed to store students' notes or research
* Typically, when the course ends, the student's looses access to everything related to the course

Flutter Dart

2026-07-14T19:42:09Z

Mshell:

Yes—'''Flutter/Dart could be useful later for the iPhone and Android apps''', but I would not use Flutter as the primary technology for customizing the MediaWiki web application as part of the overall [[Production Architecture]].

The strongest architecture is:
<code>MediaWiki remains the core platform and system of record
↓
MediaWiki skin and extensions provide the web experience
↓
MediaWiki APIs expose application functionality
↓
Flutter provides an optional iOS/Android client</code>

== For the web application: stay native to MediaWiki ==
For the web version, align closely with standard MediaWiki development practices:

* '''PHP''' for extensions, business logic, hooks, permissions, special pages, and server-side features
* '''JavaScript''' for interactive browser behavior
* '''CSS/LESS''' and a MediaWiki skin for visual customization
* <code>extension.json</code> and <code>skin.json</code> for standard extension registration

MediaWiki explicitly supports customization through skins and extensions. Its documentation notes that skins control appearance, while extensions customize how MediaWiki works. Basic skin work can be done largely with CSS, JavaScript, and JSON; PHP becomes useful for more advanced behavior. (MediaWiki)

That approach gives GoalStriving several advantages:

* MediaWiki developers can understand and contribute to it.
* Your code can potentially be distributed as conventional MediaWiki extensions or skins.
* You can reuse standard authentication, permissions, page history, templates, categories, notifications, and extension hooks.
* MediaWiki upgrades will be easier than if you replace the normal interface with an unrelated frontend framework.

I would avoid building the web version itself in Flutter Web. Technically Flutter supports web deployment, but it would make GoalStriving feel less like a native MediaWiki project and could complicate accessibility, search indexing, browser behavior, extension compatibility, and community contribution. Flutter’s cross-platform capability is real, but its strongest role here is as a separate mobile client. (Flutter Docs)

== For mobile: Flutter is a reasonable choice ==
Once the MediaWiki web application and its data model are stable, Flutter could provide one shared codebase for:

* iPhone
* Android
* potentially desktop apps later

Flutter officially supports mobile, web, and desktop deployment from a shared Dart codebase. (Flutter Docs)

A GoalStriving mobile app could offer a more focused experience than the full wiki interface:

* View goals and current priorities
* Add progress updates
* Complete daily or weekly check-ins
* Receive reminders
* Record journal entries
* Upload photographs
* Work offline and synchronize later
* Display dashboards and progress charts
* Use mobile notifications and biometric authentication

The app would communicate with MediaWiki rather than replace it.

== MediaWiki should remain the backend ==
MediaWiki provides both an Action API and a REST API. The Action API currently offers broader functionality, while the REST API provides newer, more structured HTTP endpoints. Extensions can also register their own REST endpoints. (MediaWiki)

For GoalStriving, you may eventually create API endpoints such as:
<code>GET /goalstriving/v1/goals
GET /goalstriving/v1/goals/{id}
POST /goalstriving/v1/goals
POST /goalstriving/v1/checkins
GET /goalstriving/v1/dashboard</code>
Those endpoints could be supplied by a normal MediaWiki PHP extension. The Flutter app would consume them using JSON.

This separation is valuable:
<code>MediaWiki extension
- Defines goals
- Enforces permissions
- Stores or retrieves information
- Implements workflow rules
- Exposes REST endpoints

Flutter app
- Presents the mobile interface
- Handles navigation
- Stores temporary offline data
- Calls MediaWiki APIs
- Uses phone-specific features</code>

== Important design decision: pages versus structured records ==
Before building the mobile app, determine how GoalStriving data will be represented.

You might store goals as:

# Ordinary wiki pages with templates
# Semantic MediaWiki properties
# Cargo records
# Custom MediaWiki database tables
# A hybrid of pages and structured records

For community alignment, a hybrid is likely strongest:

* Human-readable wiki pages remain the durable content.
* Templates, Semantic MediaWiki, or Cargo provide structured fields.
* A GoalStriving extension provides workflow and API functionality.
* Flutter consumes the structured representation.

For example:
<code>Goal page
├── Title
├── Description
├── Owner
├── Status
├── Target date
├── Motivational priority
├── Progress entries
└── Related goals</code>
The same information could be edited through:

* standard MediaWiki forms,
* a customized web interface,
* or the Flutter mobile app.

== How to remain aligned with the MediaWiki community ==
I would follow several principles.

=== Build standard extensions rather than modifying MediaWiki core ===
Do not directly edit core MediaWiki PHP files. Put GoalStriving functionality into independently installable extensions and skins. MediaWiki’s supported customization model is explicitly based on extension points, hooks, extensions, skins, gadgets, and APIs. (MediaWiki)

=== Keep the normal wiki usable ===
The project should still work through a browser without the Flutter app. Mobile users who do not install the app should be able to use a responsive MediaWiki interface.

=== Use open standards and documented APIs ===
Prefer:

* MediaWiki REST endpoints
* Action API where necessary
* OAuth or another supported authentication approach
* JSON
* standard MediaWiki page and revision concepts

=== Open-source the MediaWiki components ===
A clearly separated collection could be appealing to the community:
<code>GoalStriving extension
GoalStriving skin or skin customization
GoalStriving templates
GoalStriving Page Forms
GoalStriving mobile app</code>
Someone might adopt only the extension or templates without using the mobile app.

=== Treat Flutter as a client, not the platform ===
This distinction will help community acceptance. GoalStriving would remain a MediaWiki application that happens to offer a Flutter mobile client—not a Flutter product that merely uses MediaWiki as an incidental database.

== Recommended development roadmap ==

=== Phase 1: Define the MediaWiki data model ===
Decide how these concepts are represented:

* goals
* projects
* progress updates
* habits
* motivational priorities
* users and groups
* privacy
* relationships among goals

=== Phase 2: Build the web experience natively ===
Use:
<code>PHP MediaWiki extension
JavaScript
CSS/LESS
MediaWiki skin or skin customization
Page Forms / Semantic MediaWiki / Cargo as appropriate</code>

=== Phase 3: Create an API boundary ===
Do not let the future app depend on scraping HTML pages. Expose stable structured API responses from the GoalStriving extension.

=== Phase 4: Build a small Flutter proof of concept ===
Start with only:

* login
* list goals
* view one goal
* add progress update

This will expose any weaknesses in the API and data model before you build the full app.

=== Phase 5: Add mobile-specific value ===
Add features that justify installing an app:

* notifications
* offline access
* quick check-ins
* camera uploads
* widgets
* biometric login
* calendar integration

== My recommendation ==
Use this technology allocation:
{| class="wikitable"
!Layer
!Recommended technology
|-
|Core platform
|MediaWiki
|-
|Server-side customization
|PHP extension
|-
|Web UI behavior
|JavaScript
|-
|Web appearance
|MediaWiki skin, CSS/LESS
|-
|Structured data
|Semantic MediaWiki, Cargo, custom tables, or hybrid
|-
|API
|MediaWiki REST API plus extension-specific endpoints
|-
|iOS/Android
|Flutter/Dart
|-
|Authentication
|MediaWiki-compatible OAuth/session approach
|}
Flutter is therefore a good potential fit, but '''only after the MediaWiki application, data model, and API are stable'''. Your immediate learning investment should probably remain PHP, MediaWiki extension architecture, JavaScript, and MediaWiki APIs. Dart becomes worthwhile when the mobile client becomes an active development phase.

Flutter Dart

2026-07-14T19:41:33Z

Mshell: Created page with "Yes—'''Flutter/Dart could be useful later for the iPhone and Android apps''', but I would not use Flutter as the primary technology for customizing the MediaWiki web application. The strongest architecture is: <code>MediaWiki remains the core platform and system of record ↓ MediaWiki skin and extensions provide the web experience ↓ MediaWiki APIs expose application functionality ↓ Flutter provides an optional iOS/Android client</co..."

Yes—'''Flutter/Dart could be useful later for the iPhone and Android apps''', but I would not use Flutter as the primary technology for customizing the MediaWiki web application.

The strongest architecture is:
<code>MediaWiki remains the core platform and system of record
↓
MediaWiki skin and extensions provide the web experience
↓
MediaWiki APIs expose application functionality
↓
Flutter provides an optional iOS/Android client</code>

== For the web application: stay native to MediaWiki ==
For the web version, align closely with standard MediaWiki development practices:

* '''PHP''' for extensions, business logic, hooks, permissions, special pages, and server-side features
* '''JavaScript''' for interactive browser behavior
* '''CSS/LESS''' and a MediaWiki skin for visual customization
* <code>extension.json</code> and <code>skin.json</code> for standard extension registration

MediaWiki explicitly supports customization through skins and extensions. Its documentation notes that skins control appearance, while extensions customize how MediaWiki works. Basic skin work can be done largely with CSS, JavaScript, and JSON; PHP becomes useful for more advanced behavior. (MediaWiki)

That approach gives GoalStriving several advantages:

* MediaWiki developers can understand and contribute to it.
* Your code can potentially be distributed as conventional MediaWiki extensions or skins.
* You can reuse standard authentication, permissions, page history, templates, categories, notifications, and extension hooks.
* MediaWiki upgrades will be easier than if you replace the normal interface with an unrelated frontend framework.

I would avoid building the web version itself in Flutter Web. Technically Flutter supports web deployment, but it would make GoalStriving feel less like a native MediaWiki project and could complicate accessibility, search indexing, browser behavior, extension compatibility, and community contribution. Flutter’s cross-platform capability is real, but its strongest role here is as a separate mobile client. (Flutter Docs)

== For mobile: Flutter is a reasonable choice ==
Once the MediaWiki web application and its data model are stable, Flutter could provide one shared codebase for:

* iPhone
* Android
* potentially desktop apps later

Flutter officially supports mobile, web, and desktop deployment from a shared Dart codebase. (Flutter Docs)

A GoalStriving mobile app could offer a more focused experience than the full wiki interface:

* View goals and current priorities
* Add progress updates
* Complete daily or weekly check-ins
* Receive reminders
* Record journal entries
* Upload photographs
* Work offline and synchronize later
* Display dashboards and progress charts
* Use mobile notifications and biometric authentication

The app would communicate with MediaWiki rather than replace it.

== MediaWiki should remain the backend ==
MediaWiki provides both an Action API and a REST API. The Action API currently offers broader functionality, while the REST API provides newer, more structured HTTP endpoints. Extensions can also register their own REST endpoints. (MediaWiki)

For GoalStriving, you may eventually create API endpoints such as:
<code>GET /goalstriving/v1/goals
GET /goalstriving/v1/goals/{id}
POST /goalstriving/v1/goals
POST /goalstriving/v1/checkins
GET /goalstriving/v1/dashboard</code>
Those endpoints could be supplied by a normal MediaWiki PHP extension. The Flutter app would consume them using JSON.

This separation is valuable:
<code>MediaWiki extension
- Defines goals
- Enforces permissions
- Stores or retrieves information
- Implements workflow rules
- Exposes REST endpoints

Flutter app
- Presents the mobile interface
- Handles navigation
- Stores temporary offline data
- Calls MediaWiki APIs
- Uses phone-specific features</code>

== Important design decision: pages versus structured records ==
Before building the mobile app, determine how GoalStriving data will be represented.

You might store goals as:

# Ordinary wiki pages with templates
# Semantic MediaWiki properties
# Cargo records
# Custom MediaWiki database tables
# A hybrid of pages and structured records

For community alignment, a hybrid is likely strongest:

* Human-readable wiki pages remain the durable content.
* Templates, Semantic MediaWiki, or Cargo provide structured fields.
* A GoalStriving extension provides workflow and API functionality.
* Flutter consumes the structured representation.

For example:
<code>Goal page
├── Title
├── Description
├── Owner
├── Status
├── Target date
├── Motivational priority
├── Progress entries
└── Related goals</code>
The same information could be edited through:

* standard MediaWiki forms,
* a customized web interface,
* or the Flutter mobile app.

== How to remain aligned with the MediaWiki community ==
I would follow several principles.

=== Build standard extensions rather than modifying MediaWiki core ===
Do not directly edit core MediaWiki PHP files. Put GoalStriving functionality into independently installable extensions and skins. MediaWiki’s supported customization model is explicitly based on extension points, hooks, extensions, skins, gadgets, and APIs. (MediaWiki)

=== Keep the normal wiki usable ===
The project should still work through a browser without the Flutter app. Mobile users who do not install the app should be able to use a responsive MediaWiki interface.

=== Use open standards and documented APIs ===
Prefer:

* MediaWiki REST endpoints
* Action API where necessary
* OAuth or another supported authentication approach
* JSON
* standard MediaWiki page and revision concepts

=== Open-source the MediaWiki components ===
A clearly separated collection could be appealing to the community:
<code>GoalStriving extension
GoalStriving skin or skin customization
GoalStriving templates
GoalStriving Page Forms
GoalStriving mobile app</code>
Someone might adopt only the extension or templates without using the mobile app.

=== Treat Flutter as a client, not the platform ===
This distinction will help community acceptance. GoalStriving would remain a MediaWiki application that happens to offer a Flutter mobile client—not a Flutter product that merely uses MediaWiki as an incidental database.

== Recommended development roadmap ==

=== Phase 1: Define the MediaWiki data model ===
Decide how these concepts are represented:

* goals
* projects
* progress updates
* habits
* motivational priorities
* users and groups
* privacy
* relationships among goals

=== Phase 2: Build the web experience natively ===
Use:
<code>PHP MediaWiki extension
JavaScript
CSS/LESS
MediaWiki skin or skin customization
Page Forms / Semantic MediaWiki / Cargo as appropriate</code>

=== Phase 3: Create an API boundary ===
Do not let the future app depend on scraping HTML pages. Expose stable structured API responses from the GoalStriving extension.

=== Phase 4: Build a small Flutter proof of concept ===
Start with only:

* login
* list goals
* view one goal
* add progress update

This will expose any weaknesses in the API and data model before you build the full app.

=== Phase 5: Add mobile-specific value ===
Add features that justify installing an app:

* notifications
* offline access
* quick check-ins
* camera uploads
* widgets
* biometric login
* calendar integration

== My recommendation ==
Use this technology allocation:
{| class="wikitable"
!Layer
!Recommended technology
|-
|Core platform
|MediaWiki
|-
|Server-side customization
|PHP extension
|-
|Web UI behavior
|JavaScript
|-
|Web appearance
|MediaWiki skin, CSS/LESS
|-
|Structured data
|Semantic MediaWiki, Cargo, custom tables, or hybrid
|-
|API
|MediaWiki REST API plus extension-specific endpoints
|-
|iOS/Android
|Flutter/Dart
|-
|Authentication
|MediaWiki-compatible OAuth/session approach
|}
Flutter is therefore a good potential fit, but '''only after the MediaWiki application, data model, and API are stable'''. Your immediate learning investment should probably remain PHP, MediaWiki extension architecture, JavaScript, and MediaWiki APIs. Dart becomes worthwhile when the mobile client becomes an active development phase.

Production Architecture

2026-07-14T19:40:30Z

Mshell: /* Environments */

This page contains notes on the architecture that will one day support hundreds of thousands of users in a wiki community.

=== Register Domain ===
Once we decide on a name.

=== DNS Hosting ===
I will host in my personal AWS account and transfer to the nonprofit once it exists.

=== Database ===
* Platform: AWS RDS
* Engine: MariaDB (MySQL)
* Storage: xx GB (storage can be increased without any downtime)

=== Upload Storage ===
* Platform: AWS S3

=== Web and Application ===
* Platform: AWS Fargate / ECS
* Container image: MediaWiki Docker
* Instance class:
* Storage: 50 GB
* Multi-AZ: not at first

=== Load Balancer ===
* AWS

=== Secrets Manager ===

* Whenever possible, passwords and secret keys will be kept in AWS Secrets Manager.

=== Environments ===
The following environments will be built.

* Development
** All new enhancements will be added to the development environment
* Testing
** Completed features will be deployed to the test environment
** A series of test scripts and procedures will be developed to be performed following each new deployment
* Production
** Once a release has passed all tests, it will be deployed to production

=== CI/CD Pipeline ===
This procedure will allow multiple developers to author and commit code. Automated procedures will move releases from Dev to Test, and then to Production.

=== Email and Productivity Suite ===
We will use Google G-Suite. Each account will be about $8 per month until the nonprofit has been formed and we can apply for a grant from Google for free accounts.

=== Smart Phone Apps ===
The GoalStriving project uses MediaWiki as the application platform. I intend to do some customizations to the UI and the application, but previously I was thinking that would be done in PHP, but I had not begun planning. Once the web version is stable, I would like to create an iPhone and Android version. Would Flutter/Dart be useful on this project? I want to remain aligned with the MediaWiki community, because I think that community would all be potential users or supporters of the project. [[Flutter Dart|View Response]]

Page Sets

2026-07-12T15:10:28Z

Mshell:

This page contains information on Page Sets, which are content templates that can be imported to your wiki and optionally shared with others. The goal is to eliminate the blank-page problem. Each Page Set contains a pre-built structure designed to help users capture information consistently. Users can create new Page Sets, customize existing ones, and share them with trusted individuals or groups.

==== Examples ====

* Vacations
** Planning: itineraries, hotels, transportation, budget
** Journal: write a journal while on vacation, upload your favorite photos
** Future: bucket list of vacations you want to take one day
** Packing: if my friend and I both have the Packing page set installed (it probably should be by default) then when I browse anyone else's similar page, there is a plus sign next to each content section where I can add it to mine with a single click! And you can see how many other peopel have added that content. Instead of copy/pasting, we encourage you to Link the content Block and it will display that content block whereever you want in your wiki and by default you can either have it show this snapshot in time, or whatever the current version is based on teh owner's updates. That allows one user to "Subscribe" to a Content block of another user.
** You could have a content block called Status with a value that changes based on your calendar "in a meeting, busy, whatever level you want to show", and make that available to other groups dynamically and you can write rules to change it automatically based on time or events.
* Products
** Purchase information, warranties, maintenance logs, usage notes, links, and support history
* Hobbies
* Education
* Job Search
* Entertainment
** Books: reading list, notes on books you have read
** TV Shows, Movies: lists for things you would like to watch or rewatch; notes after watching
* Home Maintenance
* Family History

Page Sets

2026-07-12T15:06:05Z

Mshell: /* Examples */

Page Sets

2026-07-12T15:05:06Z

Mshell: /* Examples */

Why a wiki

2026-06-24T18:07:35Z

Mshell: /* Knowledge Gardening */

This page describes why a wiki is the ideal platform for personal note-taking and idea cultivation.

=== Common Uses of a Personal Wiki ===

# Learning
## Taking notes while taking a course or seminar
## Taking notes when reading a book, article, etc.
# Projects
## Event planning
## Job search
# Life Notes
## Vacations: bucket list, planning details, journal
## Entertainment: notes on books, movies, shows, concerts you have seen or would like to see
## Hobbies:
## Household: chores, product notes

=== Knowledge Gardening ===
Your wiki is your “digital garden of knowledge.” Instead of thinking about it as a collection of pages and documents, I think of it as a collection of ideas that have been planted like seeds, and you will cultivate over time.

Process:

# Capture a quick note.
# Add related thoughts when they occur.
# Connect notes to other notes.
# Organize into lists and sections.
# Expand into paragraphs.
# Split large topics into sub-pages.
# Continue refining indefinitely.

The wiki isn’t just a tool to organize and archive knowledge; it is a tool to help develop ideas. As you connect notes, create lists, and organize headers, it also organizes the information in your mind and will help to identify content gaps and new connections you didn’t notice before.

=== Second Brain ===
Anyone over 30 years old remembers that we all used to have many phone numbers memorized. We all had an address book (either physical or digital) where we wrote down phone numbers, but we still had to remembered them, because we knew we didn’t always have our address book with us. As soon as we had those numbers saved in a device that we always carried with us, then our brains decided they no longer needed to allocate memory to those numbers so that memory space could be repurposed.

There have been times when I had an idea in my head and I might be thinking about for a few days or weeks and then I write it down. And shortly after I write it down, I will think of a way to expand upon that idea. It is almost like my brain knew not to expand on that idea, because if I did, I wouldn't remember all the details, but as soon as the main idea was saved in a note, then my brain was free to develop it further.

As soon as you have information documented in a well-organized system that is always immediately available to you, something changes in your brain. And so I can actually say my wiki really is like a second brain, because my brain behaves differently with knowledge that is already documented in the wiki.

Main Page

2026-06-23T20:26:03Z

Mshell: /* Project Details */

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Enhancements
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Usage Notes
** [[MediaWiki Extensions]]
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Board of Directors]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Community Restrictions]]
** [[Timeline]]

Main Page

2026-06-23T20:19:08Z

Mshell:

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Enhancements
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Usage Notes
** [[MediaWiki Extensions]]
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Community Restrictions]]
** [[Timeline]]

Governance

2026-06-23T20:16:08Z

Mshell:

The community elects a Board of Directors and the board appoints a manager.

Fundraising

2026-06-23T20:12:07Z

Mshell:

This page contains notes related to fundraising.

* Grant Opportunities
** AWS for Nonprofits
** Google for Nonprofits
** Microsoft for Nonprofits
** Wikimedia Foundation
** Mozilla Foundation

Health & Finance

2026-06-23T19:44:05Z

Mshell:

In my personal wiki, two of the most important sections to me are my notes on Health and Financial.

* Ailments: symptoms, diagnosis, treatment, outcome
* Visits to a healthcare professional
* Prescriptions
* Financial account notes
* Subscription services

However, because of privacy and regulatory laws, I think it is best if we recommend our users not store any health or financial information in their wikis until our systems have been [[Privacy and Security|validated by auditors]].

FreeCodeCamp

2026-06-23T19:39:43Z

Mshell:

This page contains information about a potential partnership with FreeCodeCamp.org - a nonprofit that provides learning resources related to software and application development.

==== Reasons to Form Partnership ====
* Similar nonprofit mission
* Strong focus on learning (which often involves note taking)
* Users frequently work on projects (another need for an organized note taking system)
* Potential pool of volunteer developers
We should wait until we have implemented our new [[Production Architecture|production infrastructure]] prior to contacting them.

FreeCodeCamp

2026-06-23T19:37:50Z

Mshell:

Higher Education

2026-06-23T19:36:12Z

Mshell:

[[File:DukeWEMBAnotes.jpg|alt=A stack of all my notebook binders from my MBA courses at Duke University.|thumb|A stack of all my notebook binders from my MBA courses at Duke University.]]
In 2011, I graduated from the Executive MBA program at Duke University. For each course, students were given a three-ringed binder notebook with the reading and assignments. We were not allowed to have laptops in class, so all my notes were hand written right on the pages of those binders. I moved to New York City after completing the program to a tiny apartment and didn’t have room for them anymore, so I went through each one and transcribed the most important notes into a digital note taking tool. I took this picture after I stacked them all in the refuse room of my apartment building. Although I had copied the most important notes, I knew that I was losing a tremendous amount of knowledge.

Anyone who has ever thrown out text books or notebooks containing handwritten notes knows the pain of knowing that some of that knowledge is gone forever.

==== Potential Uses ====

* Students each have a personal wiki where they document all their class notes, reading notes, papers, and projects
* Each course has a project wiki owned by the professor and connections with all students. This would allow easy sharing of the syllabus, course notes, assignments, etc.

==== Comparison to an LMS ====

* Most institutions of higher education use a Learning Management System (LMS) for submitting assignments and distributing grades. Many have additional features as well.
* The LMS is not designed to store students' notes or research
* Typically, when the course ends, the student's looses access to everything related to the course

Community Restrictions

2026-06-23T19:09:28Z

Mshell:

This page describes any restrictions or limitations we may need to impose for legal or regulatory reasons.

==== Age Restrictions ====

* People under the age of 13 are prohibited from joining
* Community members aged 13 to 17
** Can add info to their personal wiki
** Can view public info throughout the community
** Cannot add connections and cannot be added as a connection by anyone else (therefore, they cannot share or collaborate)
* Community members 18 years of age or older
** No restrictions

Community Restrictions

2026-06-23T19:08:56Z

Mshell: Created page with "This page describes any restrictions or limitations we may need to impose for legal or regulatory reasons. ==== Age Restrictions ==== * Community members aged 13 to 17 ** Can add info to their personal wiki ** Can view public info throughout the community ** Cannot add connections and cannot be added as a connection by anyone else (therefore, they cannot share or collaborate) * Community members 18 years of age or older ** No restrictions"

This page describes any restrictions or limitations we may need to impose for legal or regulatory reasons.

==== Age Restrictions ====

* Community members aged 13 to 17
** Can add info to their personal wiki
** Can view public info throughout the community
** Cannot add connections and cannot be added as a connection by anyone else (therefore, they cannot share or collaborate)
* Community members 18 years of age or older
** No restrictions

Main Page

2026-06-23T19:06:09Z

Mshell: /* Project Details */

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Enhancements
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Usage Notes
** [[MediaWiki Extensions]]
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Governance]]
** [[Community Restrictions]]
** [[Timeline]]

Improvement to Home Page

2026-06-23T19:00:58Z

Mshell: /* Contact Us */

This page contains info about potential enhancements to the home page.

=== Real Time Usage Statistics ===
* Total number of users, wikis
* Logins in the past day, week, month
* Edits in the past hour, day, week
* Estimated current weekly infrastructure costs
* Graph showing total expenses for the past week, month, year
* Graph showing total donations received in the past week, month, year

Projects

2026-06-23T17:59:57Z

Mshell:

Projects are just like [[organizations]], but they have a planned date or milestone when they will end. Any user could create a project in their own wiki and share it, but a separate project wiki could be jointly owned by multiple people.

Existing MediaWiki extensions will be able to provide this functionality. It will probably require custom PHP development.

Organizations

2026-06-23T17:59:41Z

Mshell:

This page contains information about organizations. An organization is a wiki that is not linked to a user account and can have multiple owners.

Existing MediaWiki extensions will be able to provide this functionality. It will probably require custom PHP development.

==== Notes ====

* Personal wikis are directly associated with a user and ownership cannot be transferred.
* Organization wikis can have one or more owners which can be changed at any time.
* Any user can create an organization
* Organization Owners can add contacts and share pages.

==== Example Organization Types ====

* A study group
* A hobby or interest
* A community group

Sharing & Collaborating

2026-06-23T17:59:20Z

Mshell:

This page contains information on making a page or a section of a page on one user's wiki viewable or editable by another community member. Sharing is giving one of your contacts (or a group) read-only access to one or more pages on your wiki. Collaborating is granting edit permission to others, so everyone can add info and view what others added.

Existing MediaWiki extensions will be able to provide this functionality. It will probably require custom PHP development.

=== Potential Uses ===

* Vacation planning with family
* Club activities
* Educational study groups
* Community projects
* Shared hobby collections

=== Sharing Levels ===

* Private: the default for all content
* Select Contacts: you can specify which contacts or groups of contacts
* All Contacts
* All Community Members
* Public

MediaWiki Extensions

2026-06-23T17:58:13Z

Mshell: Created page with "This page contains information about which extensions are used today and which might be used in the future. * OpenID Connect ** Allows integration with Google and other authentication providers; already installed * ConfirmEdit ** Provides CAPTCHA; already installed * DiscussionTools ** Adds the Discuss button to the top of every wiki page; already installed * Cargo ** Allows you to store structured information in database tables while still editing wiki pages. ** I susp..."

This page contains information about which extensions are used today and which might be used in the future.

* OpenID Connect
** Allows integration with Google and other authentication providers; already installed
* ConfirmEdit
** Provides CAPTCHA; already installed
* DiscussionTools
** Adds the Discuss button to the top of every wiki page; already installed
* Cargo
** Allows you to store structured information in database tables while still editing wiki pages.
** I suspect this will be extensively used
* Page Forms
** Will be used extensively in Page Sets
* External Data
** Pulls information from REST APIs, JSON feeds, and XML feeds
* Page Exchange
** Allows import/export of pages and templates.
** Will likely become the foundation of the Page Set marketplace.
* Echo
** Notifications
* Widgets / EmbedVideo
** Allow embedded content
* Maps
** Integrate with Google Maps
* Semantic MediaWiki (SMW)
** Allows you to store structured information in database tables; supports relationships and semantic queries
** More complex and requiring more administration as compared to Cargo
** We will start with Cargo and consider implementing SMW in the future
*

Main Page

2026-06-23T17:35:57Z

Mshell: /* Project Details */

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Enhancements
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Usage Notes
** [[MediaWiki Extensions]]
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Governance]]
** [[Timeline]]

Page Sets

2026-06-23T17:29:41Z

Mshell: /* Examples */

Projects

2026-06-23T17:15:36Z

Mshell:

Projects

2026-06-23T17:15:06Z

Mshell:

Projects are just like [[organizations]], but they have a planned date or milestone when they will end. Any user could create a project in their own wiki and share it, but a separate project wiki could be jointly owned by multiple people.

For any project or organization page, you can click a toggle switch on any wiki page to see a per-user color coding on all of the text, so you can see right away who is writing most of your wiki content.

Organizations

2026-06-23T17:14:16Z

Mshell:

This page contains information about organizations. An organization is a wiki that is not linked to a user account and can have multiple owners.

==== Notes ====

* Personal wikis are directly associated with a user and ownership cannot be transferred.
* Organization wikis can have one or more owners which can be changed at any time.
* Any user can create an organization
* Organization Owners can add contacts and share pages.

==== Example Organization Types ====

* A study group
* A hobby or interest
* A community group

Connections

2026-06-23T17:04:33Z

Mshell:

This page contains information pertaining to Connections and how they are used. Note: initially, I was calling these Contacts, so you may see that name referenced elsewhere. I decided to rename to Connections because I want the site eventually to sync each user's Google Contacts - which could lead to confusion.

==== Add a Connection ====
* One user sends a request
* The other user accepts

==== Questions ====
* Should connections be uni-directional or bi-directional?
* Should it automatically create a page for each of your contacts that you can both edit?
** If connections are bi-directional, in which user's wiki would the shared page exist?
** If connections are uni-directional, then every connection pair would have two of these pages (one in each user's wiki) which may become confusing.

==== Features Related to Connections ====
* You can group your Connections
* You can share pages or sections of pages (as read-only or edit) with one or more of your Connections.
* You can start a project with one of your Connections

Main Page

2026-06-23T17:04:07Z

Mshell:

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Projects
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Connections]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Use Cases
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Governance]]
** [[Timeline]]

Contacts

2026-06-23T17:03:34Z

Mshell: Mshell moved page Contacts to Connections

#REDIRECT [[Connections]]

Connections

2026-06-23T17:03:34Z

Mshell: Mshell moved page Contacts to Connections

This page contains information pertaining to Connections and how they are used. Note: initially, I was calling these Contacts, so you may see that name referenced elsewhere. I decided to rename to Connections because I want the site eventually to sync each user's Google Contacts - which could lead to confusion.

==== Add a Connection ====
* One user sends a request
* The other user accepts

==== Questions ====
* Should connections be uni-directional or bi-directional?
* Should it automatically create a page for each of your contacts that you can both edit?
** If connections are bi-directional, in which user's wiki would the shared page exist?
** If connections are uni-directional, then every connection pair would have two of these pages (one in each user's wiki) which may become confusing.

Features Related to Connections

* You can group your Connections
* You can share pages or sections of pages (as read-only or edit) with one or more of your Connections.
* You can start a project with one of your Connections

Connections

2026-06-23T17:03:15Z

Mshell:

This page contains information pertaining to Connections and how they are used. Note: initially, I was calling these Contacts, so you may see that name referenced elsewhere. I decided to rename to Connections because I want the site eventually to sync each user's Google Contacts - which could lead to confusion.

==== Add a Connection ====
* One user sends a request
* The other user accepts

==== Questions ====
* Should connections be uni-directional or bi-directional?
* Should it automatically create a page for each of your contacts that you can both edit?
** If connections are bi-directional, in which user's wiki would the shared page exist?
** If connections are uni-directional, then every connection pair would have two of these pages (one in each user's wiki) which may become confusing.

Features Related to Connections

* You can group your Connections
* You can share pages or sections of pages (as read-only or edit) with one or more of your Connections.
* You can start a project with one of your Connections

User Profiles

2026-06-23T16:54:08Z

Mshell:

This page contains info related to the user profiles. Some of these features are dependent on [[Sharing & Collaborating|Sharing]] and [[Structured Data]].

* Users must provide: Google email address
* We will probably use the User:<name> page to store user profile info
* We pull from Google profile: name, avatar image, additional info?
* We ask users to enter: LinkedIn profile, zip code

User Profiles

2026-06-23T16:52:04Z

Mshell:

This page contains info related to the user profiles. Some of these features are dependent on [[Sharing & Collaborating|Sharing]] and [[Structured Data]].

* Users must provide: Google email address
* We pull from Google profile: name, avatar image, additional info?
* We ask users to enter: LinkedIn profile, zip code

New Authentication Providers

2026-06-23T16:49:30Z

Mshell: /* Google */

This page contains content related to the external authentication providers which are trusted to authenticate users.

=== Google ===
Offers an API for easy integration with Mail, Calendar, Contacts, and their entire Office suite. Ideally, I would like a wiki page automatically created for each contact with Google contact attributes populating structured data fields of a Page Set in the wiki.

=== Microsoft ===
Not as easy as Google, but at a minimum we can integrate Contacts and Calendar.

=== Local Authentication ===
Enabling this would require we create a procedure to handle user support requests.

=== Others ===
We may consider adding Apple and/or Facebook in the future.

New Authentication Providers

2026-06-23T16:48:18Z

Mshell:

This page contains content related to the external authentication providers which are trusted to authenticate users.

=== Google ===
Offers an API for easy integration with Mail, Calendar, Contacts, and their entire Office suite.

=== Microsoft ===
Not as easy as Google, but at a minimum we can integrate Contacts and Calendar.

=== Local Authentication ===
Enabling this would require we create a procedure to handle user support requests.

=== Others ===
We may consider adding Apple and/or Facebook in the future.

Improve Login Process

2026-06-23T13:57:37Z

Mshell:

This page contains information about how to improve the user login and onboarding experiences.

=== Potential Improvements ===

* The current process with Authentik takes several seconds with multiple page redirects.
* If I login to my personal wiki and then I navigate to the public wiki, it doesn’t automatically log me in - I must click the Log In link and wait several seconds.

Main Page

2026-06-23T13:54:20Z

Mshell:

This page contains info about this shared wiki project, which has attributes of both a wiki family and a wiki farm.

* A '''wiki farm''' is a hosting platform that provides many independent wikis using a shared infrastructure.
* A '''wiki family''' is a group of related wikis that are intentionally connected and usually serve a common purpose or community.
If you would like to contribute ideas to this project (and this wiki), please fill out the Contact Us form at https://goalstriving.org.

==== Project Details ====
* Overview
** [[Why a wiki]]?
** [[Why MediaWiki]]?
** [[Possible Names]]
* Completed
** [[Proof of Concept]]
** [[Privacy and Security]]
* Next Steps
** Identify members of the [[Board of Directors]]
** Decide on a [[Possible Names|name]]
** [[Podcast Request to Create a Wiki|Create a wiki]]
* Future Projects
*# Create a System For Community Members to [[Vote on Future Projects]]
*# [[Production Architecture]]
*# [[Improve Login Process]]
*# [[New Authentication Providers]]
*# [[User Profiles]]
*# [[Contacts]]
*# [[Organizations]]
*# [[Projects]]
*# [[Page Sets]]
*# [[Structured Data]]
*# [[Sharing & Collaborating]]
*# [[Improvement to Home Page]]
*# App for iPhone
*# App for Android
* Use Cases
** [[Higher Education]]
** [[FreeCodeCamp]]
** [[Socializing]]
** [[Health & Finance]]
* Organizational
** [[Formation of NonProfit]]
** [[Financial Transparency]]
** [[Fundraising]]
** [[Volunteer|Staffing]]
** [[Governance]]
** [[Timeline]]

Production Architecture

2026-06-23T13:51:29Z

Mshell: /* Email and Productivity Suite */

Vote on Future Projects

2026-06-23T13:40:20Z

Mshell:

This page contains information on a system that would allow community members to indicate which new features they think are the most important.

Illustrative Example

* If there are 10 projects being voted on, each user get 20 points (projects * 2 = points)
* Users can allocate their points among each project; allocating a max of 5 points to any project
* Votes will be tallied on the first of every month and a dashboard will show graphs of points per project
* Once users allocate their points, they will remain each month and can be changed any time

Podcast Request to Create a Wiki

2026-06-23T13:38:37Z

Mshell:

This page contains information about our planned rollout. At this time, I am encouraging everyone to create a wiki and begin using it. However, this is still a [[Proof of Concept|pilot platform]] that will be migrated to the new [[Production Architecture|production platform]] once it has been built. I suspect the pilot platform will support a few hundred wiki users, and I might limit new signups if performance begins to degrade. Hopefully, by January of 2027, it will be running on the new platform and will be ready for a full rollout.

Board of Directors

2026-06-23T13:28:56Z

Mshell: /* Estimated Annual Commitment: 25–40 hours */

This page contains information about the Board of Directors for the nonprofit organization. Anyone interested in serving should add their name to the [[Board Candidates]] page. Five or seven board members would be ideal; three are needed before the articles of incorporation can be filed.

Board members are responsible for ensuring that to organization:

* Remains mission-focused
* Operates effectively and ethically
* Maintains financial integrity
* Complies with all legal and regulatory obligations
* Implements effective advocacy and public-outreach strategies

==== Key Responsibilities ====

* Attend quarterly board meetings via video conference
* Provide strategic direction and governance
* Serve on one or more committees (Advocacy, Governance, Finance, Technology, Communications, or Fundraising)
* Review and approve major organizational policies
* Approve the annual budget and financial reports
* Participate in strategic planning
* Promote the organization and serve as an ambassador
* Assist with annual fundraising goals as able

==== Estimated Time Commitment: ====

* Quarterly meetings (virtual or in-person)
* Committee participation (monthly or bi-monthly meetings)
* Review of materials, budgets, and policy proposals
* Attendance at major events or briefings (optional but encouraged)

This is designed to be manageable for professionals with full-time careers.

==== Desired Skills & Qualifications ====

* MediaWiki
* Open source projects
* SaaS platforms
* Cloud infrastructure
* Cybersecurity
* Privacy law
* Data governance
* Nonprofit law
* Privacy law
* Education
* Fundraising / Grant writing

==== Financial Contribution ====
There is no financial contribution requirement. Board members are encouraged (but ''not required'') to:

* Make an annual contribution in any amount
* Identify prospective donors
* Support fundraising campaigns as appropriate

Higher Education

2026-06-23T11:47:55Z

Mshell:

[[File:DukeWEMBAnotes.jpg|alt=A stack of all my notebook binders from my MBA courses at Duke University.|thumb|A stack of all my notebook binders from my MBA courses at Duke University.]]
For community members aged 13 to 17, you can add info to your wiki, but you cannot add any contacts or be added to anyone else's contacts, so you can't share anything, but you can view public info throughout the community.

On the wiki page for Education, upload the photo of my notes from Duke. This picture is another reason why having a wiki is so important to me. For listeners, I’m showing a photo of a stack of three-ring binder notebooks - and there are about 20 notebooks and the stack is probably over 3 feet high. I got an MBA from Duke University in 2011 and for every course, we were given a three-ringed binder notebook with the reading and assignments. We were not allowed to have laptops in class, so all my notes were hand written right on the pages of those binders. I moved to New York City after getting the MBA into a tiny apartment and just didn’t have room for them anymore, so I took this picture as I stacked them all in the refuse room of my apartment building. Before I did, I went through many of those binders and transferred the most important of the notes into OneNote (which I was using at the time), but I’m sure there was still a lot that is now gone forever. I can remember some of the notes I took or papers I wrote in college that I really wish I had today.

For higher education, every student and professor has their own wiki. There will also be an project wiki for each class. The professor and each student would join. The syllabus and required reading lists would be available as the course starts. Assignment would be issued, completed, and graded within the wiki. ChatGPT said probably not on that idea, because almost every university already has a learning management system that does assignments and grades, but when the course is over, the student looses access to everything. The wiki would give them a place to take notes that they will have forever. They take their notes, create outlines, and write papers in the wiki and then copy/paste them into the LMS for submission. ChatGPT recommended that instructors create a Page Set (that may be only one page) that includes Course Overview, Assignments , Lecture Notes, Research Journal, Reading Notes, Final Project. Students can download that info and add their own notes, sub-pages, and link to their other wiki pages. Students would be encouraged to write papers in teh wiki starting with some notes, then forming an outline, then add details. There is an auto-save feature every 10 minutes and so your professor can click back through your wiki history to see all your edits since you started the assignment. And someone can make an AI system to analyze to determine how much of the students' work was done by an AI.

Professors get a gold star if they make a tax-deductible donation on behalf of all of their students. Schools can become "supporters" if they make a wiki donation on behalf of each of their students and consider that to be part of the student activity fees. It is cheaper than any other assignment tracking and grading system. Students could be taking notes in their wiki page during the course and the professor is teach from their wiki page and each student has the option of clicking an "I'm lost" button. Also, professors can ask survey or quiz questions during class and the students could answer in real-time, and the professor would have a record of everyone's answers.

Students are encouraged to form a study group and share their work with each other and discuss it.

My nephews... We can make templates for professors to create a course syllabus in Wiki format so that students attending the course can add it directly into their wiki. If universities have their current course list available as a CSV or spreadsheet, I could populate them all into our course list. And I could probably find a list of the one thousand textbooks being used by colleges and universities today and import all of them.