I think it comes down pretty much to a personal preference. I tried in the past options like evernote, dokuwiki but what I found works best for me is git. My institute is hosting a gitlab server and it has soon become my number one choice. It forces you to slip projects into repositories which are backup online on the remote server; you can easily share your progress with colleagues in a structured way and work together on the same project. Also, it keeps your code versioned.
When I use gitlab as a lab notebook, I create a new project as well as a README.md file where I explain the structure of the repository, objective and other general info. A doc folder for extra documentation I am collecting during my research (like .pdf files, related papers, etc.. ), a script folder to store all the code. If you are working with R, I strongly recommend implementing your analysis using Rmarkdown. It takes a little bit of extra effort to write your documentation together with your code, but having both of them on the same page pays off on the long run (or one month later when you want to check exactly what you did on that project).