Decide whether to consolidate semiotic and semiotic-docs repo about semiotic HOT 8 CLOSED

@alexeyraspopov & I have been discussing it and we feel like combining the main repo and the docs repo is the way to go. So, unless anyone has a compelling counterargument, that's how we're going to do it.

from semiotic.

There are several benefits from having docs as a part of main repo I see:

1. A single source of truth for both devs and users. This is where can have all Semiotic-related discussions, make atomic updates in both code and docs, align the package and docs release cycle
2. The docs website can start using Semiotic code from main branch so we can find regressions and bugs sooner
3. Single repo means simply fewer things to manage

I was planning to open a PR to pull the docs in this repo, possibly preserving git history.

from semiotic.

@willingc, the branch looks good, I'll use it for migration. Thanks!

from semiotic.

I agree. Let's do it.

from semiotic.

Decision made to create a monorepo. @alexeyraspopov will get us started on combining the repos.

from semiotic.

@emeeks I tried to figure out which branch of semiotic-docs to pull in, and I'm not sure: semiotic-2 has changes that are not in main and possibly does not have some changes from main

Do you remember any specific items from main branch that can possibly be cherry-picked to semiotic-2?

from semiotic.

@alexeyraspopov I did an interactive rebase of the branches in the semiotic-docs repo. This branch (semi-together) should resolve conflicts with main and have the 4 commits ahead from semiotic-2. Building the styleguidist docs works from head of the semi-together branch.

from semiotic.

The PR is ready: #578

from semiotic.