commit a262d8201a5895c7251c935b937c58e2506228c5
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Tue Aug 9 09:17:35 2022 -0400

    Updates

diff --git a/proposal.md b/proposal.md
index 88170fe..88a17ff 100644
--- a/proposal.md
+++ b/proposal.md
@@ -35,7 +35,7 @@ To paraphrase:
 + Milestones: What are the midterm and final "exams" to check for
   success?
 
-Note, some/most of these will be addressed in the propsal, but will
+Note, some/most of these will be addressed in the proposal, but will
 probably not be in the above exact order.
 
 ## Approach

commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Mon Aug 8 13:58:58 2022 -0400

    Updates

diff --git a/proposal.md b/proposal.md
index 21a24a0..88170fe 100644
--- a/proposal.md
+++ b/proposal.md
@@ -1,6 +1,9 @@
-# Proposal
+---
+pagetitle: Writing a Project Proposal
+version: 0.9
+---
 
-v0.9
+# Writing a Project Proposal
 
 ## Overview
 
@@ -8,13 +11,9 @@ A proposal is often the first 1/3 of a project report, with the main
 sections of:
 
 + Introduction
-
 + Background and Related Work
-
 + Methodology
-
 + Timeline
-
 + References
 
 ## Heilmeier's Catechism 
@@ -32,7 +31,7 @@ To paraphrase:
   think it will be successful?
 + Impact: Who cares? If you're successful, what difference will it make?
 + Cost/Benefit: What are the risks and the payoffs?  How much will it
-cost?  How long will it take?
+  cost?  How long will it take?
 + Milestones: What are the midterm and final "exams" to check for
   success?
 

commit 4279ded4e02728846540357bead8c261fc123c78
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Fri Nov 13 05:52:44 2020 -0500

    Updates

diff --git a/proposal.md b/proposal.md
index 42db84f..21a24a0 100644
--- a/proposal.md
+++ b/proposal.md
@@ -2,6 +2,8 @@
 
 v0.9
 
+## Overview
+
 A proposal is often the first 1/3 of a project report, with the main
 sections of:
 
@@ -15,20 +17,31 @@ sections of:
 
 + References
 
+## Heilmeier's Catechism 
+
 In general, a good proposal should be able to answer Heilmeier's
 Catechism (credit [George
-Heilmeier](https://en.wikipedia.org/wiki/George_H._Heilmeier)):
-
-+ What are you trying to do? Articulate your objectives using
-  absolutely no jargon.
-+ How is it done today, and what are the limits of current practice?
-+ What's new in your approach and why do you think it will be
-  successful?
-+ Who cares? If you're successful, what difference will it make?
-+ What are the risks and the payoffs?
-+ How much will it cost?
-+ How long will it take?
-+ What are the midterm and final "exams" to check for success?
-
-Some/most of these will be answered in a project proposal, 
-but perhaps not in this order.
+Heilmeier](https://en.wikipedia.org/wiki/George_H._Heilmeier)).
+To paraphrase:
+
++ Problem statement: What are you trying to do? Articulate your
+  objectives without jargon.
++ State of the art: How is it done today, and what are the limits of
+  current practice?
++ Novelty in approach: What's new in your approach and why do you
+  think it will be successful?
++ Impact: Who cares? If you're successful, what difference will it make?
++ Cost/Benefit: What are the risks and the payoffs?  How much will it
+cost?  How long will it take?
++ Milestones: What are the midterm and final "exams" to check for
+  success?
+
+Note, some/most of these will be addressed in the propsal, but will
+probably not be in the above exact order.
+
+## Approach
+
+Generally, outline the proposal - basically, provide sections and
+subsections with bullets for content and order for each.  When ready
+to write, see the individual "one-pagers" for each section.
+

commit 385f82b8934327afa719a97fb9e7900893906afc
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Wed Sep 25 14:28:05 2019 -0400

    Updates

diff --git a/proposal.md b/proposal.md
new file mode 100644
index 0000000..42db84f
--- /dev/null
+++ b/proposal.md
@@ -0,0 +1,34 @@
+# Proposal
+
+v0.9
+
+A proposal is often the first 1/3 of a project report, with the main
+sections of:
+
++ Introduction
+
++ Background and Related Work
+
++ Methodology
+
++ Timeline
+
++ References
+
+In general, a good proposal should be able to answer Heilmeier's
+Catechism (credit [George
+Heilmeier](https://en.wikipedia.org/wiki/George_H._Heilmeier)):
+
++ What are you trying to do? Articulate your objectives using
+  absolutely no jargon.
++ How is it done today, and what are the limits of current practice?
++ What's new in your approach and why do you think it will be
+  successful?
++ Who cares? If you're successful, what difference will it make?
++ What are the risks and the payoffs?
++ How much will it cost?
++ How long will it take?
++ What are the midterm and final "exams" to check for success?
+
+Some/most of these will be answered in a project proposal, 
+but perhaps not in this order.