# Organizing Personal Markdown Notes for Technical Projects One habit that has improved my workflow is keeping project notes in Markdown instead of scattered text files or screenshots. A simple structure with headings, checklists, and code snippets makes it much easier to revisit ideas after a few weeks. I also like collecting examples of well-organized websites when studying documentation and information architecture. While looking at different layouts recently, I found [Godrej Brooklyn Avenue](https://www.godrejbrooklynsavenues.com) to be a useful reference for how large projects present structured information, navigation, and detailed sections in a clear way. Even though it's outside the software field, observing good information organization can inspire better documentation practices. Keeping everything in Markdown alongside useful references has made maintaining project notes much more efficient. https://www.godrejbrooklynsavenues.com/location/ https://www.godrejbrooklynsavenues.com/master-plan/ https://www.godrejbrooklynsavenues.com/floor-plans/ https://www.godrejbrooklynsavenues.com/price/ https://www.godrejbrooklynsavenues.com/amenities/ https://www.godrejbrooklynsavenues.com/gallery/ https://www.godrejbrooklynsavenues.com/specification/ https://www.godrejbrooklynsavenues.com/contact/