Skip to content

Commit ef6e868

Browse files
Removed folders:
- 2018 - DOCS - old_files - pull_request_intro - temp - site_icons Updated paths to icons in head.html and browserconfig.xml. Moved icons / config files for them to static/icons.
1 parent 9b4ceb4 commit ef6e868

File tree

2 files changed

+52
-0
lines changed

2 files changed

+52
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Improvements
2+
3+
- automatic srcset generation for responsive images (portrait, landscape and sizes) - #88
4+
- responsive background image for events chapters (portrait) and globally - #90
5+
- convert main navigation to (ul li) keeping the styling (it is display: block) - #84
6+
- move map related javascript code to site.js and confirm all works - #91
7+
- add event location map to event details with exact event's address - #92
8+
- add calendar icon in events list on the home page where date / time is shown - #85
9+
- find a way to detect users location before generating chapters map and center it on users location - #86
10+
- change button in events list from "Learn More" to (i) - info icon - #89
11+
- introduce events calendar (got a web link to a project which did that for jekyll) - #93
12+
- additional layout for events card for special events (like global pandas was), something to make a particular event stand out - bigger card, with an image and a short description etc. - #94
13+
- style google map markers to match site's color theme / fonts etc. - #95
14+
- add Selenium tests to make sure all links and stuff works across all browsers - #96
15+
16+
17+
# Issues
18+
- create chapter detailed view - #97
19+
- create event detailed view - #98
20+
- forced site regeneration (to keep events up to date) (empty commit on a cron job at night?) - #99
21+
- create Thursday's event (@ QuantumBlack) (should we display all future events?, display only 1 closest to today's date per chapter or display within time limit (like all in next week/fortnight/month))
22+
- decide on chapters card layout (what link should there be, any additional info) - #100
23+
- automate chapters cards generation - #87
24+
- check what happens if too many events are concurrent - how far do we want that section to stretch (the background image goes out of sharpness) - #101
25+
- create include to generate chapters variable used for google map - #102
26+
- create resources section with guides (pull request, pandas docs etc., this is least priority) - #103
27+
28+
# Documentation
29+
30+
- document image sizes required for all sections including responsive, set standard image naming policy - #104
31+
currently it is name_SizeXxSizeYpx.ext, we may need to agree on adding orientation to the name as well (_op, _ol or similar).
32+
- document collections (sponsors, chapters) (what items are in, what data they hold, where are they displayed, examples of usage) - #105
33+
- document _includes (layout snippets and function like code, examples of usage, parameters, returns etc.) - #106
34+
- document _layouts (which one is for what page etc., variables used, variables required) - #107
35+
- document _pages (what sections are contained within, dependecies) - #108
36+
- document _sass (set some standards what css goes where etc.) - #109
37+
- documents events (how to create an event, what variables are required, what can be blank etc.) - #110
38+
- documents chapters(how to create a chapter, what variables are required, what can be blank etc.) - #111
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# How does jekyll work
2+
3+
#### Create layouts (templates for django people) to generate your views
4+
#### Create content files with yml variables(date) and html / plain text to feed into the layouts
5+
#### Use scss (sass) or less to style (automatically preprocessed into css during build) - see _sass (partials)
6+
#### Main content goes into _pages
7+
#### Use Liquid templating language (similar to jinja2 / django templating languages) to create logic
8+
#### includes are your friends - use them as modules, functions , snippets of html or whatever
9+
#### time related files - _posts (see chapters_events), categories are automatically generated by jekyll using the parent folder name as the category name
10+
#### subject related files - collections, have to add them in _config.yml for jekyll to see them properly (see _sponsors, _chapters)
11+
#### Config in _config.yml
12+
#### Static content - images, javascript, css in static folder.
13+
14+
#### When change pushed to master / origin - github pages rebuilds the site.

0 commit comments

Comments
 (0)