Jekyll2026-07-28T02:15:36+00:00https://lhh-team4.github.io/feed.xmlTeam Name Goes HereAn FLL robotics team at Lansing Tech Studio.Welcome to Our Team Blog2026-07-27T00:00:00+00:002026-07-27T00:00:00+00:00https://lhh-team4.github.io/2026/07/27/welcome-to-our-blogThis is an example post so you can see what a finished one looks like. Once your team has written a couple of your own, delete this file — in the GitHub file view, open it and click the trash can icon.

Why keep a blog?

Judges at competition ask what your team tried, what broke, and what you changed because of it. A blog is the easiest way to have real answers ready instead of trying to remember in November what you did back in August.

Short and frequent beats long and perfect. Three sentences after a meeting is a great post.

Good things to write about

  • What you built or coded today, and whether it worked
  • Something that broke and how you fixed it
  • A design you tried and then threw away — judges love these
  • Photos of your robot mid-build
  • Outreach events and who you met

Writing your own post

Open the _posts folder and copy TEMPLATE-copy-this-file.md. The instructions are right at the top of it.

One rule matters more than the rest: the file name has to start with the date, like 2026-08-15-we-built-the-arm.md. Miss that and your post silently won’t appear.

Now go build something.

]]>Coach Brendon