Closed captn3m0 closed 1 month ago
As a summary of the work so far, we've gone from (ignoring any dependencies):
Language | files | blank | comment | code |
---|---|---|---|---|
HTML | 30 | 3372 | 2031 | 14559 |
CSS | 2 | 139 | 22 | 1163 |
SCSS | 1 | 155 | 25 | 623 |
JavaScript | 1 | 9 | 6 | 47 |
-------- | -------- | -------- | -------- | -------- |
SUM: | 34 | 3675 | 2084 | 16392 |
to
Language | files | blank | comment | code |
---|---|---|---|---|
HTML | 45 | 376 | 34 | 2833 |
SCSS | 5 | 3 | 30 | 1435 |
CSS | 3 | 54 | 7 | 331 |
JavaScript | 2 | 40 | 68 | 196 |
Markdown | 12 | 5 | 0 | 118 |
YAML | 1 | 1 | 2 | 29 |
-------- | -------- | -------- | -------- | -------- |
SUM: | 68 | 479 | 141 | 4942 |
Added a tiny easter egg in the footer, see if you can spot it:
Converted half of the events to a new markdown based layout. We no longer need to write HTML to manage events! This is how the upcoming Chess Connect on 28th July looks now:
---
location: the-market-place
title: "Chess Connect Rapid"
image: chessconnect_28072024.jpeg
variations:
- standard-swiss
layout: newevent
payment:
price: 250
razorpay: pl_OT5SsIPvJBThGj
startsAt: 2024-07-28T10:00
endsAt: 2024-07-28T15:30
---
## Event Details
Join us for our next chess meetup for a day filled with chess magic! Whether
you're a seasoned player or just discovering your love for the game, come
embrace the thrill of chess, forge new connections, and make every move
count. Let's bring the chessboard to and continue our journey of checkmates
and camaraderie!
## What's Included
* 5 Hours of **Rapid Chess** (Format 10+5)
* `Special Prizes` for the Top 3 Players
* Chance to Win a `Chess.com Diamond Membership` through Lucky Draw
## Schedule
- Registration and Player Briefing (10:00 AM)
- Round 1 (10:15 AM)
- Round 2 (10:50 AM)
- Round 3 (11:25 AM)
- Round 4 (12:00 PM)
- `Lunch Break (12:35 PM)`
- Round 5 (1:20 PM)
- Round 6 (1:55 PM)
- Round 7 (2:30 PM)
Notably:
_data/variations.yml
for a complete list)Have another 13 chess connect events to convert, will get to them later.
Crossed off a few more items:
layout: event
instead of layout: newevent
)Final Numbers after all events are now in markdown:
Language | files | blank | comment | code |
---|---|---|---|---|
SCSS | 5 | 49 | 28 | 1640 |
HTML | 20 | 70 | 25 | 842 |
Markdown | 39 | 112 | 0 | 736 |
CSS | 2 | 21 | 36 | 224 |
JavaScript | 3 | 39 | 73 | 199 |
YAML | 1 | 1 | 5 | 46 |
JSON | 1 | 1 | 0 | 31 |
-------- | -------- | -------- | -------- | -------- |
SUM: | 71 | 293 | 167 | 3718 |
Most stuff on this TODO list is done, will close this issue and create separate ones.
Laundry list of ideas, suggestions etc. See #99 for context. Keeping this for myself, so I have a list to follow. If you'd like to help, please reach out!
The priority is for maintainability -> usability -> performance, but I can get distracted. Ideal state is to make it easy for maintainers to create new events, and not worry about doing anything once they are done - they should automatically be archived.
Performance
Maintainability
_includes/head*
files togetherYYYYMMDD
for event dates in URLs. Sorting is confusing right now.SEO and Usability