<commit_before>- using a config.json file to store settings
	- this file is located in the root directory (where manage.py is)
- uses a postgresql database
	- set up database connection information in the config.json file
- template structure is from django tutorial
    - uses a directory in root for global includes and a folder in each app (there's only one right now, blog) for specific templates
- trying to use virtualenv and virtualenvwrapper to help with maintaining requirements
    - using a virtualenv named "blog_django"
    - wasn't super intuitive to install psycopg2 (ended up having to run "easy_install" on the link to the windows executable)

- initial models for the blog
    - post: standard stuff here. Title, slug (for link generation), body, publish date, category (foreign key and will be restricted to one), and excerpt (for the front page).
    - category: basic tree organization for categories. Title for category, slug (similar to post), and foreign key to category (this will hold the parent for the tree structure)

- creating an index page
    - basic view for now that just lists every post with the most recent one first

- importing stylesheets and templates from a different blog project
    - now things look more polished with a bootstrap theme (hopefully)
    - storing bootstrap css and sidebar icons in a "static" folder in the root directory (theoretically all other apps would use this theme)
    - added a separate "static" folder to the app to store media files used by posts. This will likely change to use cloud storage.

- added some pagination

- added a category index to show posts in a category
    - even though categories can have parents, I only look one level down for displaying the tree structure
    - however, the site will look all the way down the category tree to find out which categories a post belongs in
    
- added tags, using django-taggit package
    - tags are just added to the Post model with the manager
    - created a tag index in urls and views that is basically a copy of the category index without the child searching
    
- created flatpages for about and contact pages. These pages are just stubs for now. I'll add functionality later.
    - these pages exist on the database, so I dumped their data and stored it in the fixtures folder. They can be brought back with 'manage.py loaddata fixtures/flatpages.json'
    
- added support for storing static files in amazon s3 as well as media files. I'm starting to wonder if I really need to store the static css/js files in S3. Would it be more efficient to store it locally? If so, I left the original static url setting as a comment in the settings file. I created a basic Media model for testing. It seems to upload S3 fine, but I need to add more metadata to the model, such as folder organization, upload date, (last update date?), some sort of title. 

- added versatile image field to handle thumbnailing images. Find a solution to the error with name length.

- removed flatpages and switched to using static template pages for about and contact

- switched versatile image field to regular image field. better to just do the thumbnailing myself.

- added support for displaying all posts for a given year, month, or day.<commit_msg>added some random stuff to the notes file<commit_after>- using a config.json file to store settings
	- this file is located in the root directory (where manage.py is)
- uses a postgresql database
	- set up database connection information in the config.json file
- template structure is from django tutorial
    - uses a directory in root for global includes and a folder in each app (there's only one right now, blog) for specific templates
- trying to use virtualenv and virtualenvwrapper to help with maintaining requirements
    - using a virtualenv named "blog_django"
    - wasn't super intuitive to install psycopg2 (ended up having to run "easy_install" on the link to the windows executable)

- initial models for the blog
    - post: standard stuff here. Title, slug (for link generation), body, publish date, category (foreign key and will be restricted to one), and excerpt (for the front page).
    - category: basic tree organization for categories. Title for category, slug (similar to post), and foreign key to category (this will hold the parent for the tree structure)

- creating an index page
    - basic view for now that just lists every post with the most recent one first

- importing stylesheets and templates from a different blog project
    - now things look more polished with a bootstrap theme (hopefully)
    - storing bootstrap css and sidebar icons in a "static" folder in the root directory (theoretically all other apps would use this theme)
    - added a separate "static" folder to the app to store media files used by posts. This will likely change to use cloud storage.

- added some pagination

- added a category index to show posts in a category
    - even though categories can have parents, I only look one level down for displaying the tree structure
    - however, the site will look all the way down the category tree to find out which categories a post belongs in
    
- added tags, using django-taggit package
    - tags are just added to the Post model with the manager
    - created a tag index in urls and views that is basically a copy of the category index without the child searching
    
- created flatpages for about and contact pages. These pages are just stubs for now. I'll add functionality later.
    - these pages exist on the database, so I dumped their data and stored it in the fixtures folder. They can be brought back with 'manage.py loaddata fixtures/flatpages.json'
    
- added support for storing static files in amazon s3 as well as media files. I'm starting to wonder if I really need to store the static css/js files in S3. Would it be more efficient to store it locally? If so, I left the original static url setting as a comment in the settings file. I created a basic Media model for testing. It seems to upload S3 fine, but I need to add more metadata to the model, such as folder organization, upload date, (last update date?), some sort of title. 

- added versatile image field to handle thumbnailing images. Find a solution to the error with name length.

- removed flatpages and switched to using static template pages for about and contact

- switched versatile image field to regular image field. better to just do the thumbnailing myself.

- added support for displaying all posts for a given year, month, or day.

- added the ability to use {{REPLACE}} in my post body instead of hardcoding the image links.

stuff to do:
- remove the body_html field from the post admin (probably not necessary because it lets me check that things are working)
- maybe make it so the replace thing only triggers when the body_html is empty?
- find a better way to pick images for the post
{'fraction_non_alphanumeric': 0.03708513708513708, 'fraction_numerical': 0.0011544011544011544, 'mean_word_length': 3.7213896457765667, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1611747', 'n_tokens_mistral': 1655, 'n_tokens_neox': 1582, 'n_words': 1111}