Not too complicated actually.

I work in sales, I set up a few pages, namely:

• Clients (a base for clients)
• Projects (a base for current projects)
• Tasks (query all the TODO, WAITING, etc)
• Suppliers (general supplier info)

And then set up a few templates that i use whenever i get a new client and new project so its a simple /template and bam they’re automatically linked to the project pages.

here’s an example of a new client template:

- # #Client details
  template:: New Client
	- contact::
	- email::
	- telephone::
	- address::
	- tags::
	

It links back to the client page and the new project template links back to that specific client so everything is always within the proper linked reference.

here’s an example of a new project:

- # #Projects Details  
  template:: New Project
	-client::
		-status:: TODO
		-creation::
		-deadline::
		-tags::
		
		- ## Project Summary
			-

I log everything in the journal (which is why i prefer logseq).

I had a more complicated set up when if first started but ended up simplifying it and honestly the simpler the better since as long as you make sure to use the project tag all of your notes will show up as linked references.

I like the concept of tab groups but i don’t think that they’re for me. If i could pin certain sites into the groups however, that would be a game changer.

just copy your ‘.mozilla’ folder over and you’re good to go.

As for copying to forks, idk, i generally try to keep those seperate but mozilla sync should do the trick if you wanted to do it that way.

I tried everything under the sun and then just decided to build my own CRM system with logseq and I’ve never looked back.

“The deal we struck with Google for all that nice free stuff, the affordable mobile phone ecosystem, the entertaining videos etc. has proved a deal with the devil” (View Highlight)

Author: Rupert Goodwins