Describe the Pull Request

A clear and concise description of what the pull request does.

Expected Behavior

A clear and concise description of what you expected to happen.

Fixes the Following Issues

A clear and concise description of what you expected to happen.

**Scr...

Describe the Pull Request

Add the latest batch of podcast episodes.

Update files to bump to version 1.7.0

Describe the Pull Request

Add web tests from the other style guide.

Describe the Pull Request

Add web dev tests for Playwright

Describe the Pull Request

Add tests for the main application.

Describe the Pull Request

Add Pytest tests.

Describe the Pull Request

Add tests to playwright

Describe the Pull Request

Add PyTest tests that will break,

Describe the Pull Request

A clear and concise description of what the pull request does.

Expected Behavior

A clear and concise description of what you expected to happen.

Fixes the Following Issues

A clear and concise description of what you expected to happen.

**Scr...

Move from a normal stylesheet to a Bootstrap default.

Add arl and text editor instructions to README.

Instructions on how to get your Deezer arl.

This should be the last time I have to change this link - hopefully.

Created an open source template for a timeline of important science figures that people studying science at my school can use.

Here is the first edition of the readme. Should be merged without a hitch.

I made another spelling error... This time I wrote "we are hopping to be up and running"..., when it should have been ''hoping".

I made another spelling error... This time I wrote "we are hopping to be up and running"... when it should have been ''hoping".

There is no need for this file anymore because all there is is HTML code.

Update the README with new instructions - but then I realized that there was a typo in the actual code, so I will fix that first.

Finish the README code and finish the README itself.

Reverse the changes by the previous commit where I copied the code from the template and forgot to change the %_% blanks. Also, add the Google Analytics tag.

Add links to some popular style guides from the internet to the README for future use and ideas.

Delete the unused Privacy Policy and EULA text files as we are changing over to HTML format.

Delete the unused EULA text file as we are changing over to HTML format.

Add a link to the Issues page as well as a link to the Pull Request page.

Add some install instructions as well as a link to the maintainers.

Update the old Privacy Policy, EULA and Environmental Policy to HTML.

Add the new version of the README that conforms to Markdown standards.

Upload the Snoopy image so we can link it to the HTML code so you only have to copy a small HTML file.

Update and add the landing page HTML file which includes blanks for where you can insert your timeline, GitHub profile, and email address.

Fixes issue # 0.

Changes proposed in this PR:

• Update the community docs.

Reason for PR: To update the community docs.

@willtheorangeguy

Change the LICENSE file format from Markdown to no-name brand because otherwise, it won't show up in the GitHub info bar.

Remove the cringey CI notice that shouldn't be here anymore.

Update the document so it actually reflects changes made in this repo and the name of this repo.

Fixes issue #0 .

Changes proposed in this PR:

• Fix CONTRIBUTING.md

Reason for PR: fix typos and spelling errors

@willtheorangeguy

Fix some formatting errors.

Fixes issue # .

Changes proposed in this PR:

Reason for PR. (replace this text)

@willtheorangeguy

Fixes issue #0 .

Changes proposed in this PR:

• Update the CONTRIBUTING file with the proper info for this repo.

Reason for PR: the same as the above

@willtheorangeguy

Add community documents like the issue template and code of conduct.

Update the formatting of the links in the readme and the spelling of the word 'Black'.

Files changed:

• readme.md

I have updated the formatting of the titles in the README.md by adding spaces between the # and the title text. I have also streamlined the code syntax for the titles/headings so that they all use the # method.

Files changed:

• README.md

Final initial commit before real Pr is opened.

I have edited all of the code to work with Python 3.

Some of the code still does not work, but that is because of code base issues. If you would like it, I can try to solve some of those problems too.

Delete HTMLMessage.py and TextMessage.py.

I have realized that in many places LEGO has been spelled lowercase as in lego. This is against the LEGO brand guidelines which can be found here: https://bricks.stackexchange.com/a/8659

I have tried to update all the files, but if there are some ...

Update docs based on common and best Markdown practices.

Changes proposed in this PR:

• Update all docs in conformation with Markdown Lint.

@willtheorangeguy

I have updated the README.md with some formatting and grammar changes.

I have changed AUTHORS to AUTHORS.md. I formatted the text in the AUTHORS.md file to conform with Markdown standards.

I have clarified the requirements list in the README.md file by sorting all the optional and must-have items together. I have also added capitals to the beginning of the items in the features list so everything is grammatically correct.

I have also added issue numbers (that link to their res...

Clarify README lists, and add bug numbers.

This is a PR for the initial code commit.

(Main reason: so I can get more PRs for 24 Pull Requests!)