Open fryorcraken opened 2 years ago
I've added the necessary validation TXT records for waku.org
and waku.guide
: https://github.com/status-im/infra-misc/commit/ab8a10a6
This might take an hour or a few though.
And they are verified:
@fryorcraken we wont use Acid Info framework for waku.guide
& *.waku.guide
. As discussed we are going to use a fully specialized framework. We have two solid options
We prefer number 1 because it is an exact match in terms of tech stack (ReactJs + Typescript) with what we use at branding. It also supports MDX which enables you to have way more control over the content and its structure.
@fryorcraken I would suggest moving all tasks related to documentation websites to their own repos, what do you think?
@fryorcraken I would suggest moving all tasks related to documentation websites to their own repos, what do you think?
Yes, happy to clean up once waku.guide is shipped. It's just that part of the task is creating said repo. I am happy to move the tasks to the repos once they are open.
Definition of Done
Tasks
tasks grouped together are sequential
[x] Verify domains on GitHub orga (waku.org, waku.guide)
[x] Ensure publishing works @amirhouieh
[ ] Point from waku.org to waku.guide for docs, remove doc content from waku.org
[ ] Redirect docs.wakuconnect.dev to waku.guide
[ ] Remove doc content from go-waku repo
[ ] Remove doc content from go-waku repo
[ ] Add link to js-waku.guide to js-waku README