summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorArghKevin <50538286+ArghKevin@users.noreply.github.com>2024-04-16 09:58:00 -0700
committerGitHub <noreply@github.com>2024-04-16 09:58:00 -0700
commit4527e38738af610071c1f83790cab552b18378b6 (patch)
tree59fd5a023aa02ed671e832e0ea4a301bff5087ae /README.md
parent34144cc9ccc9437b4045b321975d8d82eeed3e8a (diff)
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md30
1 files changed, 14 insertions, 16 deletions
diff --git a/README.md b/README.md
index ab75f0a..cddd18b 100644
--- a/README.md
+++ b/README.md
@@ -1,16 +1,16 @@
-# GoogleFontStyleVSPopularity
+# Week One
## The Pitch
Google Fonts provides a public-access CDN for typefaces released for use without restriction on commercial use. Setting aside professional opinions on which of the typefaces are worth using, some of the typefaces are downloaded for use on web pages several million times per month. Others are hardly used. Good design isn't an exact science, however there may be tangible, technical qualities which correlate with typeface popularity.
-Google Fonts provides two databases publicly. https://raw.githubusercontent.com/google/fonts/main/tags/all/families.csv provides a listing of each typeface's name; style; and weight. https://fonts.google.com/metadata/statsLinks to an external site. provides popularity statistics of each typeface, over different metrics of time. Together, these may be used to generate a graphical interface demonstrating what correlation, if any, lies between a typeface's technical qualities and actual popularity. The typefaces are downloadable from a central repository, https://github.com/google/fonts. Using the files included, lower-level properties, such as glyph count and file size, may be analyzed.
+Google Fonts provides two databases publicly. https://raw.githubusercontent.com/google/fonts/main/tags/all/families.csv provides a listing of each typeface's name; style; and weight. https://fonts.google.com/metadata/stats provides popularity statistics of each typeface, over different metrics of time. Together, these may be used to generate a graphical interface demonstrating what correlation, if any, lies between a typeface's technical qualities and actual popularity. The typefaces are downloadable from a central repository, https://github.com/google/fonts. Using the files included, lower-level properties, such as glyph count and file size, may be analyzed.
## The Plan
I've started the project two weeks late. The original criteria
-specifies 24 hours of work. Over 6 weeks, that's 4 hours
-per week. Below are 4-hour time allocations per week.
+specifies 24 hours of work. Over the coming 6 weeks, Diego
+and I will be catching up.
### Week 1
@@ -19,39 +19,37 @@ per week. Below are 4-hour time allocations per week.
* UML
* Video explanation
* This timeline
-* Start method stubs
### Week 2
+* Start method stubs
+* Start GUI
+
+### Week 3
-* Beginning of GUI
* Start parsing CSV
* Javadoc in advance as much as is pragmatic,
-### Week 3
+### Week 4
* Start parsing JSON
* Write objects which represent each font
* Figure out API calls for file size and glyph count
-### Week 4
+### Week 5
* Start writing methods to calculate trends over time
* Line graph of top styles?
* Check documentation as it exists
-### Week 5
+### Week 6
* Update databases
* Finalize trend calculation methods
+
+### Week 7
* re-structure as needed
-### Week 6
+### Week 8
* Whatever isn't done, finish it
* Demonstration video
-
-## CRC Cards
-
-## UML
-
-## First video