Replies: 2 comments 6 replies
-
Possible suggestion : link the materializecss.com domain to the org's gh pages, and ensuring the old docs version will be archived without bugs Being able to close tickets (esp. spams) from the original repo. Or just provide a safe way to get access in the original repo + SN |
Beta Was this translation helpful? Give feedback.
6 replies
-
nope, I gave up hope on that
…________________________________
De : roiLeo ***@***.***>
Envoyé : lundi 22 août 2022 16:06
À : materializecss/materialize ***@***.***>
Cc : ShinProg (Logan Tann) ***@***.***>; Author ***@***.***>
Objet : Re: [materializecss/materialize] We might get in contact with one of the original contributors (Discussion #263)
Still no answer? I see some activity on his profile
—
Reply to this email directly, view it on GitHub<#263 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AG2U34OH242NTXBGSHXJJSLV2OCOPANCNFSM5UJIOR3Q>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello @materializecss/members @materializecss/maintainers
I contacted Spiral Burst's twitter (the company that have born as the next personal project of one of materializecss' original member) about how we could get in contact with them.
Here's the answer :

I suggest we talk here about the content of the letter before sending it 👇
Beta Was this translation helpful? Give feedback.
All reactions