Event report of “Vivliostyle User/Dev Meetup Autumn 2021”
(The original article is 「Vivliostyle ユーザーと開発者の集い 2021秋」開催報告 in Japanese)
The semi-annual “Vivliostyle User/Dev Meetup Autumn 2021” was held online on November 14. The slides and a summary of comments from the day (by yamasy1549) are available at the following page.
- [Japanese] List of event materials
- [Japanese] Board writing of “Vivliostyle User / Dev Meetup 2021 Autumn”
In addition, videos of each presentation are available on our YouTube channel as follows.
- Part 1: Vivliostyle from the User’s Perspective
- Part 2: Vivliostyle as a Library
- Part 3: Vivliostyle as an Application
- Vivliostyle CLI update - 2021 Autumn (spring_raining) (17:14)
- Release of Vivliostyle Theme Development Guidelines (yamasy1549) (16:17)
- Development of Theme Acquisition Library (AyumuTakai) (17:31)
- Vivliostyle Pub Current Status and Future Development Schedule (takanakahiko) (21:42)
- Q&A session (14:27)
- Part 4: Vivliostyle Dev Meeting (46:48)
This time, the start time was delayed by about 30 minutes due to my poor setup. Also, due to this, I was not able to get the questionnaire that I had planned for Ayumu Takai’s presentation, which left me with many things to regret. We deeply apologize for the inconvenience caused to everyone who applied for participation and the speakers.
I was impressed by Zaslon’s point that “the information on the official website of Vivliostyle is only describing the application, not the CSS typesetting itself”. Certainly, from the user’s point of view, the information on the official website seems to be biased. Just a few days ago, I had a conversation with Founder Murakami saying, “We are achieving the initial development goals for Vivliostyle.js, so let’s work on the spread of CSS typesetting as the next step”. It’s a good opportunity, so let’s think about what we can do.
I also felt that the code reading that our old friend Kojima-san talked about was very important. One of the issues we’ve been facing in Vivliostyle lately is that the only committer for Vivliostyle.js is Founder Murakami. If we don’t solve this problem, sustainability will be a concern. The only way to do this is to start by getting as many people as possible to read the source code, even if it seems like a detour. I realized that what we need now are measures to support that.
The next meetup is scheduled for next year, Spring 2022. By this time, the beta release of Vivliostyle Pub should have started. Stay tuned to see what announcements we can make!