![]() ![]() But the problem was that I forgot to close an tag in the middle of the article. At first, I thought the configurations for Babel or Webpack were wrong. As you see in the below error message, it doesn't say which JSX contents are not closed. Moreover, the error message looks really confusing. Therefore, MDX forces us to close all tags too. But, JSX syntax always forces us to close tags. As you know, in HTML5, you are supposed to write the tag without closing. One of the articles in my old blog was using tags. But supporting JSX might causes some problems. Also, via MDXProvider, you could set the layout components from outside the MDX file. So you can mix markdown and JSX(rendered from React Component) in your markdown articles. MDX introduced itself as a superset of markdown with JSX supporting. In this section, I want to share the cause of my suffering. I'd been undergoing lots of trial and error too. To be honest, the biggest reason for the delay was that I played Apex Legends too much. I thought I could finish it in a week but it took almost a month. I listened to this song while writing this article.īut, although I'm quite motivated, the renewal was not easy. To fix it, I think blogging in English should be one of the best ways. So now, I can speak and write English without hesitation. Although I'm living in Japan and Korea, I'm using English most of the time because my girlfriend is from the US and my coworkers are from the UK and France. For the past year, my English has improved quite a lot. The last reason is that I want to improve my English ability. So I fixed up the stage to start my show again. But, sadly, I realized that I don't have enough channels to share these ideas. My colleagues also like them a lot because they are fixing most problems of the current conventional solutions. So I'm VERY MOTIVATED NOW! And, while working on the Boostnote.next project, I've been inventing lots of interesting tools like prismy. Since the beginning of last August, my company's let me fully focus on the renewal of our Boostnote project, AKA Boostnote.next. But now, I'll definitely recommend it to others.Īnother reason is that I want to share my ideas. I guess the biggest reason was that I don't know Ruby language.(And I don't want to learn it either.Haha) Also, as a member of unifiedjs colletive, I want to try MDX which is based on Remark. It was kind of OK, but I was not happy about it. I want to try fancy new stacks, Next.js and MDX more. So in this article, I want to share how I renewed my blog. Nothing.I've renewed my blog with Typescript, Next.js and MDX to start blogging again. The Chat pane can float too or dock to bottom of app UI.There can be a tab under sidebar pane which shows a Chat among all peers, (similar to Zoom).Optional User Profile picture, User Name, etc independent from Obsidian Account. ![]() The users may choose to set collaboration The collaboration access has to be set per vault.On entering that shared code/URL, The two Obsidian apps will establish a P2P connection.The user needs to share this Collaboration Code to his/her Collaborating partner who inturn will enter it in his/her Open vault > Onboarding Screen> New Collaboration Vault > give local location to save > Enter Code/URL > get started.Where user creates/generates a “Collaboration Code (simple text)”, or “Service URL/QR Code of Service URL(real url or obsidian url, I don’t know)”.There can a “Collaboration” settings tab under Settings > Plugin Options.The connections are formed on ad-hoc basis, and Secure. On server-less model, (server-less implies that no server computer will negotiate when establishing P2P contact, it must all depend on individual peer’s user-agent (user-agent=Obsidian).Īs per my Idea, you don’t need a Obsidian Account to collaborate. I suggest a Peer2Peer solution for collaboration. Assuming that it is going to be on server-less P2P model, This will allow users to skip any third party service, and allow better privacy and control.Across two or more people (good for Teams). ![]()
0 Comments
Leave a Reply. |