+
+ + {{ article.title }} +
++ {{ article.summary }} +
+
+ {{ dayjs(article.date).format("MMMM D, YYYY") }}
+
+ + {{ article.summary }} +
+When you sign up for our - - Creator Monetization Program + Creator Monetization Program (the "CMP"), we collect:
diff --git a/apps/frontend/src/pages/news/article/[slug].vue b/apps/frontend/src/pages/news/article/[slug].vue new file mode 100644 index 000000000..10e380538 --- /dev/null +++ b/apps/frontend/src/pages/news/article/[slug].vue @@ -0,0 +1,263 @@ + + + +{{ article.summary }}
+Featured article
+{{ featuredArticle?.summary }}
+Over the few months, Modrinth has seen incredible interest towards our Servers product, and with significant growth, our vision for what Modrinth Servers can be has evolved alongside it. To continue striving towards our goal of providing the best place to get your own Minecraft multiplayer server, we’ve made the decision to bring our server hosting fully in-house.
Modrinth has some ambitious goals for the next year. We want to create the best possible way for all Java players play Minecraft, and to host and play their favorite modpacks and custom servers. To achieve this, it’s clear that Modrinth Servers needs to be built and scaled on our own infrastructure.
By running every aspect of our hosting platform, we gain the flexibility to tailor the experience to our community’s needs—whether that means deeper integrations with Modrinth’s ecosystem, better performance, or more innovative features. This also allows us to invest in the long-term sustainability of Modrinth Servers, ensuring that we can scale seamlessly and avoid running out of available servers stock.
This change is purely a logistical step forward and does not reflect negatively on our partnership with Pyro. In fact, Pyro has been an incredible partner in getting Modrinth Servers off the ground and we are very grateful for their collaboration. We completely support Pyro and their future, and we know they’re working on some exciting new products of their own, which we can’t wait to check out!
We know you may have questions, and we want to make this transition as smooth as possible.
What part of my server was being run by Pyro?
Until this point, Pyro has been responsible for the physical server machines that run your Modrinth servers. This means that they have been responsible for the hardware that powers your server, as well as the files and data for them. Moving forward, all of this will exist under Modrinth.
What happens to my running servers?
Your current servers will continue running, and we’ll provide a clear migration path if any action is needed on your part. You can expect a follow up soon, however our goal is to do this with 0 downtime or impact to you if possible.
Will anything else change that impacts me?
Modrinth Servers will remain the same great experience its has been, you likely won’t notice any changes right away. Long term, this means we’ll be able to improve both the stability of servers as well as the features that make managing your server a breeze.
This is an exciting step toward a future where Modrinth is the go-to destination for Java Minecraft players—not just for mods and mod-packs, but for hosting and playing too. We appreciate your support and can’t wait to share more soon!
' diff --git a/packages/blog/compiled/a_new_chapter_for_modrinth_servers.ts b/packages/blog/compiled/a_new_chapter_for_modrinth_servers.ts new file mode 100644 index 000000000..ec586cd06 --- /dev/null +++ b/packages/blog/compiled/a_new_chapter_for_modrinth_servers.ts @@ -0,0 +1,9 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./a_new_chapter_for_modrinth_servers.content').then((m) => m.html), + title: 'A New Chapter for Modrinth Servers', + summary: 'Modrinth Servers is now fully operated in-house by the Modrinth Team.', + date: '2025-03-13T00:00:00.000Z', + slug: 'a-new-chapter-for-modrinth-servers', + thumbnail: true, +} diff --git a/packages/blog/compiled/accelerating_development.content.ts b/packages/blog/compiled/accelerating_development.content.ts new file mode 100644 index 000000000..b483c4b9f --- /dev/null +++ b/packages/blog/compiled/accelerating_development.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Update: On April 4, 2024 we announced that we had returned the remaining $800k in investor capital back to our investors to take a different path. Read that announcement here. This article remains here for archival purposes.
There are over 3 billion gamers worldwide, but only a small fraction ever go further and mod the games they play. Modrinth is here to bring modding to every player on the planet—all the while allowing mod creators to make a living off of it.
Since our founding in 2020 and up until a few months ago, Modrinth has been a purely volunteer project. In the past couple months, the Modrinth team has been more productive than ever. We\'ve released the Anniversary Update, we\'re actively working on the launcher once more, and we\'re laying out plans for how to multiply Modrinth creator payouts.
The vision we have for the future of Modrinth is great, and right alongside that is the need for an amazing team to build out this vision. That\'s why we recently announced that we\'re hiring—we\'ve already come so far on just volunteer work, but for Modrinth to be sustainable and for its growth to be sustainable, we need to pick up the pace.
That\'s why we\'re excited to announce that we\'ve raised a pre-seed round of funding led by Makers Fund, with investors including Ryan Johnson, Stephen Cole, Pim de Witte, Chris Lee, and Andreas Thorstensson to accelerate development and expand to new horizons for Modrinth.
We\'re thrilled to keep on building and iterating on Modrinth over the next few years. Here\'s a look into what we have in store over the next few months for Modrinth:
Support for new games!
We are excited that we are able to build a product that will manage to grow us to sustainability and create the best modding experience for creators and users. Being able to pay ourselves and bring on new people is a big step in making that happen. There is still a lot to do, so let\'s get to it!
We know there might be some concerns so we included a short Q&A section below for some common ones. Feel free to ask in our Discord if you have any more questions!
Our main expense is and will continue to be salaries. The labor cost has always been the main bottleneck for Modrinth. Having paid employees will allow us to develop Modrinth faster, bringing Modrinth to a point of sustainability and growing the platform. For example, we\'re planning to release our launcher this year, and eventually we\'re hoping to expand into more games. Those won\'t be possible without having paid employees.
We started and always will have the goal of creating a community-oriented, open-source modding platform. Simply put, there isn\'t any reason for us not to be. It\'s clear that the previous impersonal, corporate approaches to video game modding have not worked, and Modrinth is excited to change that.
Yes! We are committed to having all (when possible) our current code and future code we write to be open-source. Copyright is held by the contributors as we have no CLA, so we cannot make it closed-source (even if we wanted to) without, well, violating the law.
The Modrinth team (currently consisting of Prospector, Emma, and Geometrically) is behind Modrinth. We\'ve been modding Minecraft for years, with connections extending back to grade school. Investors have a minority stake in the company, and have no control or say in our decisions.
No. We have no plans to adopt or explore web3 for Modrinth.
Not directly. Hiring more people will allow us to build up the infrastructure that can increase payouts, but the money we pay out to creators will always come from sustainable sources such as advertising and never from investment funds.
' diff --git a/packages/blog/compiled/accelerating_development.ts b/packages/blog/compiled/accelerating_development.ts new file mode 100644 index 000000000..4c6019dbe --- /dev/null +++ b/packages/blog/compiled/accelerating_development.ts @@ -0,0 +1,9 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./accelerating_development.content').then((m) => m.html), + title: "Accelerating Modrinth's Development", + summary: 'Our fundraiser and the future of Modrinth!', + date: '2023-02-01T20:00:00.000Z', + slug: 'accelerating-development', + thumbnail: false, +} diff --git a/packages/blog/compiled/becoming_sustainable.content.ts b/packages/blog/compiled/becoming_sustainable.content.ts new file mode 100644 index 000000000..3b7b6ccde --- /dev/null +++ b/packages/blog/compiled/becoming_sustainable.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Just over 3 weeks ago, we launched our new ads powered by Aditude. These ads have allowed us to improve creator revenue drastically and become sustainable. Read on for more info!
We’re excited to share we have been able to increase creator revenue by 5-8x what it was before!
There’s a couple changes to how revenue is distributed out to creators coming with this increase.
First, revenue is no longer entirely paid out the day they are earned. Previously, we used our own in-house advertisement deal which paid us in advance for the entire month, and we divided that among each day in the month, as the month progressed. With the switch to a more traditional ad network, we are paid on a NET 60 basis, which is fairly standard with ad networks. What this means is that some of your revenue may be pending until the ad network pays us out. Exactly how this works is explained further here.
Second, the revenue split between Modrinth and Creators has changed. See the next section on sustainability for more on this.
We have updated the Modrinth creator revenue split from 90/10 to 75/25. However, all of the increases listed above are with the new rate included, so while the percentage is lower, the overall revenue is much, much higher.
While 90% is a more remarkable figure, we changed it in order to ensure we can keep running Modrinth and continue to grow creator revenue without having to worry about losing money on operational costs.
Through these changes, we are proud to announce Modrinth is now fully sustainable with the new income, with all hosting and operational costs accounted for (including paying our developers, moderators, and support staff!) With the new revenue, users will see reduced support times and we will be able to ship bigger and better updates quicker to you all!
In an effort to be more transparent with our community than ever before, we are opening up as many of our finances as possible so you all can know how we’re doing and where all the money is going. We’re working to develop a transparency page on our website for you to view all the graphs and numbers, but it wasn’t ready in time for this blog post (for now, you can view our site-wide ad revenue in the API here. We also plan to publish monthly transparency reports with more details about our revenue and expenses, the first of which should be available in early October, so keep an eye out for that.
For now, we can tell you that creators on Modrinth have earned a total of $160,868 on Modrinth to date (as of September 13, 2024), and here’s a graph of our revenue from the past 30 days:
We have a lot of exciting things coming up still, and of course, we greatly appreciate all of your support!
' diff --git a/packages/blog/compiled/becoming_sustainable.ts b/packages/blog/compiled/becoming_sustainable.ts new file mode 100644 index 000000000..fffe8666c --- /dev/null +++ b/packages/blog/compiled/becoming_sustainable.ts @@ -0,0 +1,11 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./becoming_sustainable.content').then((m) => m.html), + title: 'Quintupling Creator Revenue and Becoming Sustainable', + summary: 'Announcing an update to our monetization program, creator split, and more!', + date: '2024-09-13T20:00:00.000Z', + slug: 'becoming-sustainable', + thumbnail: true, + short_title: 'Becoming Sustainable', + short_summary: 'Announcing 5x creator revenue and updates to the monetization program.', +} diff --git a/packages/blog/compiled/capital_return.content.ts b/packages/blog/compiled/capital_return.content.ts new file mode 100644 index 000000000..3102f30fa --- /dev/null +++ b/packages/blog/compiled/capital_return.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Over three years ago, I started Modrinth: a new Minecraft modding platform built on community principles, a fully open-source codebase, and a focus on creators.
What started as a hobby project quickly grew into something much bigger, with over twelve thousand creators and millions of players modding their game with Modrinth! Running Modrinth quickly evolved into a full-time job as we worked to scale the platform, develop new features, and fix bugs.
As our small project that originated in the Fabric Discord server started to get more and more serious, we decided to seek funding to accelerate growth and keep up with the competition. A year and a half ago, we raised a $1.2 million pre-seed round of investor capital. With the money, we hired full-time developers and part-time community members, some of whom have supported Modrinth since the very beginning. With all this support, we launched creator monetization, authentication, analytics, organizations, collections, the Modrinth App, and support for more project types, growing Modrinth’s user base fifteen-fold!
But, this rapid growth came at some costs. We let sustainable infrastructure for moderation slip to the back-burner since we could just hire extra moderators to compensate, and more and more of my time as the founder was taken up by things that didn’t make Modrinth better. Bugs and technical debt also gradually infected our codebase as we focused on hyper-growth over maintenance.
Alongside this, as we looked more into the future, we saw that the venture-backed cycle wouldn’t be the right path for Modrinth. Every investor invests in a company with the expectation of a return on their investment, and while all of our backers have been incredibly supportive, we wanted to be able to work on Modrinth at our own pace and terms. We’ve seen other companies in this space prioritize profits and growth at the expense of the community and creators, and we didn’t want this to happen to Modrinth.
In short, forgoing the venture route would allow us to build Modrinth independently at a sustainable pace and put our creators, community, open-source nature, and values first, without having to worry about expectations of profit or growth.
In the end, as of February 1st, 2024, I decided to return $800k in remaining investor capital back to our investors.
This decision was not an easy one, as without this funding, we would be unable to support the Modrinth team as it previously existed. With this reality, I made the difficult decision to significantly reduce the size of our team to match our goals of sustainable growth.
I also owe a huge debt of gratitude to everyone on the team affected by all of this–Emma, Wyatt, Maya, Coolbot, Jade, Carter, and Prospector–for everything they have done to help make Modrinth what it is today.
I want to take a moment to highlight each of their contributions:
This transition was challenging, causing significant delays in project reviews and support ticket resolution, not to mention the stress for the former team. While project review and support times have returned to normal, this was not the experience we wanted for our creators or users to have. I sincerely apologize that you all had to experience this transition, and I wish that it had been executed more smoothly.
I would also like to apologize for how long this post has taken to come out. It took longer than I expected to do all the legal work and coordination necessary to return the remaining money to the investors, but it has finally been finished.
Going forward, we will be continuing to build a platform that is sustainable for both the creators and all the people who work on making the platform what it is. Hosting Modrinth is already sustainable, and we are working to make developing Modrinth sustainable as well.
We’ve made great strides in this already with new moderation infrastructure including AutoMod and a built-in moderator checklist, greatly reducing moderator time per project. We’re also focused on increased transparency, through providing consistent updates on Modrinth’s development and making it easier to contribute to Modrinth with better documentation and contribution cycle.
We started Modrinth to serve the community, and are taking this path so we can continue to. We hope you all will continue to support us as the newly independent Modrinth.
—
Jai (aka Geometrically)
Founder of Modrinth
Update 10/24: A month and a half ago we began testing Carbon Ads on Modrinth, and in the end, using Carbon did not work out. After disabling ads with tracking in them, the revenue was about equal to or worse than what we were generating previously with EthicalAds. Effective today, we are switching our ads provider back to EthicalAds for the time being.
As a step towards implementing author payouts, we\'re experimenting with a couple different ad providers to see which one works the best for us. We\'ve been using EthicalAds for a long time now, but we\'d like to now try out CarbonAds.
In most respects, this is a temporary experiment, but we\'re hoping that Carbon will become our primary ad provider in the near future.
Over the past week and a half, we\'ve garnered a lot of useful feedback in the #devlog channel of our Discord. Over those 1,300 or so messages of open discussion and debate, there were also a lot of questions, concerns, and misconceptions. This blog post aims to address the most frequent of those.
Yes. This was confirmed to us via email by a Carbon representative.
No. They fall under the Acceptable Ads Standard; that is, there is only ever one per page, they are less than 120 pixels tall, and they are separate and distinguishable from actual site content.
Alongside the introduction of Carbon, we have removed the privacy settings that we previously had. These privacy settings controlled whether PII would be sent in our internal analytics and whether you wanted personalized ads to show up. Our analytics do not contain PII and Modrinth does not show personalized ads. Both of those would be intense breaches of your privacy, opt-in or not, and Modrinth intends to respect your privacy.
We have been using ariadne to take note of page views and ad revenue since August 1st, 2022. While creator payouts cannot yet be claimed, all ad revenue from this date forward will be claimable once payouts are released!
Payouts are not yet done, but this switch is one of the largest things that needs to be done prior to its release.
There are quite a number of reasons why it\'s not feasible for us to continue using Ethical. In order to be fully transparent, let\'s go into detail about each of them.
Over half of the ads shown by Ethical are their so-called "in-house ads". That is, Ethical does not have enough inventory to always be showing an ad, so instead it shows an advertisement for itself. These self-advertisements make a whopping $0 for Modrinth.
Ethical does provide an option to replace these self-advertisements with our own fallback ads, which we\'ve done for the past month or so. However, negotiating those sorts of deals takes an excruciating amount of time, time that we would rather be spending on developing Modrinth to make it better.
Carbon allows us to have a more hands-off approach with advertising, which is most ideal for us right now.
Ethical gives us an average of $0.24 for every thousand page views (also known as CPM) after taking into account the aforementioned in-house ads. Anyone who knows anything about the advertising business knows that this figure is abysmally low. With Modrinth getting over four million page views in a month\'s timespan, we make an average of less than $1000 per month with Ethical. This simply isn\'t sustainable for the thousands of creators on Modrinth.
While we can\'t quite be sure what our CPM with Carbon will be -- again, this is only a temporary experiment for now -- we have reason to believe that it will be considerably greater than what Ethical can provide.
Over the time that Modrinth has used Ethical, we have found that the diversity of the advertisers shown has declined at a rate greater than is sustainable. The vast majority of the ads shown by Ethical, excluding its in-house ads, are for DigitalOcean. If DigitalOcean decided to withdraw from Ethical, that would end up toppling our entire system. Modrinth\'s payouts simply cannot rest on this house of cards if we wish to grow in any capacity.
You are still able to access Modrinth using an adblocker, and Modrinth will not force you to disable it to access the site. However, Modrinth\'s ads are unintrusive and take up no more space than it would otherwise.
When you turn off your adblocker for Modrinth, you are supporting both Modrinth and its creators in the process. 100% of the ad revenue from creator pages, including projects, versions, and users, go directly to creators. The ad revenue from other pages, including search, pay for Modrinth\'s upkeep costs and allow us to continue to exist.
For the benefit of everyone involved, we humbly request that you turn off your adblocker for Modrinth. We have a full guide for how to turn off your adblocker located on our docs site.
In conclusion, we hope you\'re as excited about our upcoming release of payouts as we are. Exploring our options for ad providers is quintessential if we wish to be sustainable for payouts, and the best time to do this is now. As always, though, no release ETAs!
Please note that this blog post was not editorialized or reviewed by Carbon prior to publishing. These are the findings and words of Modrinth and Modrinth alone. What\'s said here about CPMs and other statistics will not be true of other sites, but they are true for Modrinth.
' diff --git a/packages/blog/compiled/carbon_ads.ts b/packages/blog/compiled/carbon_ads.ts new file mode 100644 index 000000000..54c1a2db0 --- /dev/null +++ b/packages/blog/compiled/carbon_ads.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./carbon_ads.content').then((m) => m.html), + title: "Modrinth's Carbon Ads experiment", + summary: + "As a step towards implementing author payouts, we're experimenting with a couple different ad providers to see which one works the best for us.", + date: '2022-09-08T00:00:00.000Z', + slug: 'carbon-ads', + thumbnail: true, +} diff --git a/packages/blog/compiled/creator_monetization.content.ts b/packages/blog/compiled/creator_monetization.content.ts new file mode 100644 index 000000000..a4be62aca --- /dev/null +++ b/packages/blog/compiled/creator_monetization.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Yes, you read the title correctly: Modrinth\'s Creator Monetization Program, also known as payouts, is now in an open beta phase. All of the money that project owners have earned since August 1st is available to claim right now!
This includes even projects other than mods! Modpacks, plugins, and resource packs also generate payouts for creators to claim.
Alongside this, the frontend also got a facelift across the entire site, most notably on the settings, notifications, and user profile pages.
Since the start, Modrinth has been a platform created by Minecraft content creators for Minecraft content creators. Allowing creators to earn a bit of money for their hard work and dedication to their content has been a goal since we started, and we are so incredibly ecstatic to finally be able to release this for everyone.
Whether it\'s used for buying coffee, paying for server costs, or to get that luxury pair of socks, we hope that creators will be able to use their payouts on whatever keeps them running. We want to encourage creators to keep making content for everyone to enjoy, with the hope that everyone will eventually be able to call Modrinth their go-to destination for Minecraft modded content.
For every project uploaded to Modrinth, we keep track of its page views and downloads through an internal system we call ariadne. Through our payouts algorithm (source code), we distribute 100% of ad revenue earned from creator pages to the creators behind these projects. Project owners can decide how to split it (or how not to split it) between their team members.
Modpacks are a bit different, with revenue split 80% to the Modrinth dependencies on the pack and 20% to the modpack author. This split is subject to change and will be evaluated periodically to ensure the split is reasonably fair.
After taking the search pages into account, around 10% of the site\'s ad revenue ends up going to us, mainly to cover hosting and personnel expenses, and 90% to creators.
While payouts will be small at first, we\'re working on improving our ads system to better fund the program. We\'ve also got big projects coming soon to continue our trajectory of making the monetization program and the site better!
When a project of yours on Modrinth gets approved, you are automatically enrolled into the program. You will start to incur a balance, which you can view from the Monetization dashboard. You can claim your first payout via PayPal or Venmo as soon as you enter your credentials and have the minimum balance of 0.26 USD.
Even though the minimum is low, you will want to wait some time to allow your balance to build up before claiming. Each payment processor has its own fees which depend upon whether you\'re within the United States, which are detailed on the dashboard\'s revenue tab.
Once you request a transfer, you may have to confirm the transfer via email if you don\'t already have a PayPal account. If you do not confirm using the link in the email within 30 days, or the transfer fails for whatever reason, the amount requested will be returned to your Modrinth balance, though the processor\'s fees may already have been deducted by that point.
Since Modrinth is a US-based company, all amounts are stored, displayed, and paid out in US dollars. PayPal will convert the amount to your local currency once you begin the process of transferring from your Modrinth balance to your PayPal account.
We\'re aware of some extenuating circumstances for creators living in areas affected by geopolitical conflict. As such, we are looking into alternative ways to allow payouts to continue in these regions.
At the moment, there are no mechanisms in place to make your Modrinth balance expire after some time, though this is likely to be added in the future for creators who do not claim their balance after several years. Rest assured, we will have processes in place to make sure that your money doesn\'t go poof just because you weren\'t able to claim it in time.
The website frontend has had some "small" changes of around 12,322 lines of code to accommodate payouts and many other changes. Many of these changes were inspired by the experiments done on the SvelteKit Rewrite, progress on which is paused for the time being. Navigate around the main site for a bit to discover some of these changes! Highlights include:
This is a jam-packed update, and it would be impossible to list all the changes in this post. Feel free to explore the site, claim your funds, and give us feedback on Discord. If you suspect you\'ve found any critical bugs or exploits, please email us immediately at support@modrinth.com - otherwise, for non-critical bugs, report them on GitHub.
👑
' diff --git a/packages/blog/compiled/creator_monetization.ts b/packages/blog/compiled/creator_monetization.ts new file mode 100644 index 000000000..72ba5a6c1 --- /dev/null +++ b/packages/blog/compiled/creator_monetization.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./creator_monetization.content').then((m) => m.html), + title: 'Creators can now make money on Modrinth!', + summary: + "Yes, you read the title correctly: Modrinth's creator monetization program, also known as payouts, is now in an open beta phase. Read on for more information!", + date: '2022-11-12T00:00:00.000Z', + slug: 'creator-monetization', + thumbnail: true, +} diff --git a/packages/blog/compiled/creator_update.content.ts b/packages/blog/compiled/creator_update.content.ts new file mode 100644 index 000000000..c423cc612 --- /dev/null +++ b/packages/blog/compiled/creator_update.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'December may be over, but that doesn’t mean we’re done giving gifts here at Modrinth. Over the past few months, we’ve been cooking up a whole bunch of new features for everyone to enjoy. Now seems like as good of a time as ever to bring you our Creator Update! Buckle up, because this is a big one.
The headlining features include:
The long-awaited addition of analytics is here for creators! You can view analytics over time for your projects, including downloads, page views, and revenue, all in an effortlessly easy-to-use dashboard.
The data for analytics have been collected over the course of many months. In fact, the data for revenue goes all the way back to August 2022, and the data for downloads and views back to February 2023.
You can view the analytics for an individual project by going to the settings and clicking “Analytics”. You can view analytics for all of your projects in the analytics dashboard.
Isn’t managing permissions across a bunch of different projects pretty tedious? We sure thought so. Just like on GitHub, you can now create organizations on Modrinth to manage permissions across multiple projects.
You can create organizations from the organizations dashboard. Each organization has a name, a brief summary, and an icon. Just like project members, organization members have a role, a monetization weight, and project permissions, plus permissions for the organization as a whole. Roles, monetization weights, and project permissions can be overridden on a per-project basis.
Unlike GitHub, usernames and organization names on Modrinth do not conflict with one another. If you want to have an organization named after yourself, feel free to do so!
Just like how Spotify has playlists or how Goodreads has shelves, Modrinth now has collections! Collections are lists of Modrinth projects put together for a common purpose. You can then share these collections with others to view.
Your followed projects now make up an automatically generated private collection, which you can access from the “Your collections” section of the dashboard.
Not quite! Modpacks are much more complex than collections. Collections are simply lists of projects. Here’s a quick comparison:
| Modpacks | Collections |
|---|---|
| Created through a launcher, such as the Modrinth App. | Created on the Modrinth website. |
Contains options files, configuration files, and optionally files from outside of Modrinth, wrapped together in a .mrpack file. | Contains a list of Modrinth projects (mods, plugins, data packs, resource packs, shaders, and modpacks). |
| Has individual releases with version history. | Instantly updates whenever a project is added or removed. |
| Must be reviewed by Modrinth’s staff and approved per Modrinth’s rules before it can be published. | Does not need to be reviewed by Modrinth’s staff. Can go public at any time. |
| After approval, can be listed in search, archived, unlisted, or private. | Can be public (shows up on your Modrinth profile), unlisted (only accessible by direct URL), or private (only you can access it). |
All in all, collections are handy for easily grouping together and sharing Modrinth projects. If you’re bored on the subway heading home, you can look for new mods on your phone and quickly add them to a Modrinth collection. However, for many use cases, spending the time to create a modpack might make more sense. Collections and modpacks are both here to stay—one is not going to replace the other.
PayPal and Venmo are so 2023. To enter 2024, we are adding support for a bunch of different new payout methods, including ACH (available for direct transfer to a United States bank account) and a couple thousand gift cards. You know, just “a few”.
Whether you want Applebee’s in America, Boek & Bladkado in Belgium, or Cineplex in Canada, we’ve got them all and plenty more. Prepaid Visa cards, Amazon gift cards, and Steam gift cards are among the available options. Does anyone want a Home Depot gift card? We’ve got those, too.
For the longest time, Modrinth’s text editor for descriptions, changelogs, reports, and more has just been a box to enter Markdown syntax. What about people who don’t know Markdown, though? Even for those who do, writing it out by hand gets tedious after a while. That’s why we rebuilt it from the ground up to make it far easier to use.
Among its features are standard shortcuts (like Ctrl+B for bold), a monospace font in the editor itself, and buttons for inserting headers, basic formatting, lists, spoilers, block quotes, links, images, and YouTube videos.
Using the image button, you can also now upload images directly, instead of having to use an external host or the Gallery tab of a project. You can still insert images from outside sources, though certain sources (such as the Discord CDN) are blocked. We will notify authors using these blocked sources to replace the images.
Wouldn’t it be nice if other websites or apps could add a “Sign in with Modrinth” feature? We asked ourselves this and thought, yes, it would be nice to add. So we added it.
The OAuth2 protocol allows other services to gain a limited amount of access to your Modrinth account without compromising your login information. Maybe you want to create your own analytics dashboard? Or maybe you want to make your own way to add content to collections? How about connecting organization permissions to roles in a Discord server? The possibilities are endless.
You can create a new OAuth application in the Applications section of your settings. You can see which applications you’ve granted access to in the Authorizations section.
Want to hear more from us on a regular basis? Check us out on our social media pages; we post often on both Mastodon and X/Twitter. You can also chat with us on Discord if you like that.
Thanks to intergrav for making the banner image.
' diff --git a/packages/blog/compiled/creator_update.ts b/packages/blog/compiled/creator_update.ts new file mode 100644 index 000000000..ae7b2b64e --- /dev/null +++ b/packages/blog/compiled/creator_update.ts @@ -0,0 +1,11 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./creator_update.content').then((m) => m.html), + title: 'Creator Update: Analytics, Organizations, Collections, and more', + summary: 'December may be over, but we’re not done giving gifts.', + date: '2024-01-06T20:00:00.000Z', + slug: 'creator-update', + thumbnail: true, + short_title: 'The Creator Update', + short_summary: 'Adding analytics, orgs, collections, and more!', +} diff --git a/packages/blog/compiled/design_refresh.content.ts b/packages/blog/compiled/design_refresh.content.ts new file mode 100644 index 000000000..f30625578 --- /dev/null +++ b/packages/blog/compiled/design_refresh.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'We’ve got a big launch with tons of new stuff today and some important updates about Modrinth. Read on, because we have a lot to cover!
First off, we’re launching Modrinth+, a monthly subscription to help support Modrinth and all of the creators on it directly!
As a Modrinth+ subscriber, you will get:
Pricing starts at $5/month, with discounts depending on what region you live in and if you opt for an annual plan.
We created Modrinth+ so people could help support Modrinth and creators on the site. We have no plans to paywall any content on Modrinth, and creator features will never cost money. We started Modrinth as a free and open-source platform, and we intend to keep it that way.
If you do have a few extra dollars a month and want to help support Modrinth, this is a great way to do it!
We’re launching Stage One of Modrinth’s refreshed look to Modrinth.com today as well. I want to stress that it’s not fully complete and we’re going to be continuing to refine and finish updating the rest of the pages over the coming weeks. However, it has enough significant usability improvements and new features that we’re launching it broadly now. Please bear with us while we work to complete it promptly!
Key new features include:
We know there will be some minor hiccups and disruptions of workflows, but we’d really appreciate it if you could gently let us know how a particular change has affected you on GitHub here (or upvote/comment on an existing issue) rather than declaring it’s the end of the world.
In the last few months, Modrinth has grown an incredible amount. We are now serving over a petabyte of data per month (that is, 1,000 terabytes!) to over 20 million unique IP addresses. It’s almost unfathomable how large we have become since we started from nothing just four years ago.
However, with growth like this, our costs have also grown drastically—primarily in bandwidth. This, unfortunately, means that we’ve grown well beyond what a single advertiser could support.
Our original plan was to build out our own ad network (Adrinth) where we could cut out the middleman and provide highly targeted ads without the need for tracking to our gaming-specific audience. Unfortunately, we’ve grown too quickly (a very good problem to have!) and don’t have the immediate resources to do this at this time.
This leaves us with no choice but to switch to a more traditional programmatic ads setup powered by Aditude for the time being. We\'re not making this decision lightly, and we understand that some folks will not be happy about this change. Rest assured, we\'ve made sure that our new ad network partner meets our requirements, such as compliance with all local regulations such as GDPR and CCPA, and that the new ads remain as unobstructive as possible with this format.
These changes bring Modrinth back to sustainability as well as conservatively increasing creator revenue by three-fold! Along with paying hosting bills, the new income will also be used for more support staff and paid team members, decreasing ticket time and speeding up our development.
We also want to thank our friends over at BisectHosting for supporting us with our ad deal for the past year.
Over the last few months, we’ve been overhauling the internals of the Modrinth App to drastically improve performance and stability. Over one hundred issues have been closed with this update alone! Here’s a short list of the major changes:
Don’t have the Modrinth App? Check it out here!
Want to hear more from us on a regular basis? Check us out on our social media pages; we post often on both Mastodon and X/Twitter. You can also chat with us on Discord if you like that.
Thanks to intergrav for making the banner image.
' diff --git a/packages/blog/compiled/design_refresh.ts b/packages/blog/compiled/design_refresh.ts new file mode 100644 index 000000000..48c52b230 --- /dev/null +++ b/packages/blog/compiled/design_refresh.ts @@ -0,0 +1,12 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./design_refresh.content').then((m) => m.html), + title: 'Introducing Modrinth+, a refreshed site look, and a new advertising system!', + summary: 'Learn about this major update to Modrinth.', + date: '2024-08-21T20:00:00.000Z', + slug: 'design-refresh', + thumbnail: true, + short_title: 'Modrinth+ and New Ads', + short_summary: + 'Introducing a new ad system, a subscription to remove ads, and a redesign of the website!', +} diff --git a/packages/blog/compiled/download_adjustment.content.ts b/packages/blog/compiled/download_adjustment.content.ts new file mode 100644 index 000000000..bcb93282a --- /dev/null +++ b/packages/blog/compiled/download_adjustment.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'While working on the upcoming analytics update for Modrinth, our team found an issue leading to higher download counts from specific countries. This was caused by an oversight with regards to rate limiting, or in other words, certain files being downloaded over and over again. Importantly, this did not affect creator payouts; only our analytics. Approximately 15.4% of Modrinth downloads were found to be over-counted. These duplicates have been identified and are being removed from project download counts and analytics. Read on to learn about the cause of this error and how we fixed it.
A graph of many Modrinth projects and their download counts, showing a disproportionate amount of downloads from China.
More specifically, the issue we encountered is that the download counts from China were through the roof compared to the page view statistics.
Upon further investigation, there was one specific launcher that was repeatedly downloading the same files from Modrinth over and over again within a very short time span.
Notice how the downloads in each section (delineated by the bold line) have the same path and were created within the same second.
This, to say the least, baffled us. We already had code called Sisyphus in place to limit the number of downloads that a single source can make over a given span of time. So what gives?
As it turns out, the issue lay in the underlying technology used by Sisyphus. It uses Cloudflare Workers in order to intercept the request each time that a file is requested to be downloaded. Essentially, it acted like so:
For the most part, this system works fairly well. The main issue comes in step 2: it takes a little while for different Sisyphus instances to sync up with each other. One of the benefits of Cloudflare Workers is that the code is deployed to hundreds of different servers around the world. When multiple requests come in at the same time, they can get routed to different servers in order to allow each request to be handled faster. Cloudflare Workers, however, takes up to 60 seconds for each server’s information to sync up with each other. A server in Australia might know that a given source has already downloaded something, but a server in Turkey might not. As a result, multiple downloads from the same source might all get counted if they are handled by different servers.
In order to fix this, we entirely rewrote Sisyphus. It still uses Cloudflare Workers, but all of the processing of step 2 has been offloaded to the main Modrinth backend. This not only speeds up downloads (even if only briefly), but also makes download counts more reliable. Over the past few days, we\'ve already implemented the necessary adjustments. Our observations have shown that the results are significantly more consistent in their accuracy. Instead of having strange spikes in activity, the graph of new downloads now follows the expected pattern.
Notice the spikes on the left? Compare that to the silky-smooth sinusoidal satisfaction on the right!
To reiterate, the issue is now resolved and payouts were not affected. Payouts do not take into account downloads from launchers other than the Modrinth App; therefore, this adjustment has no bearing on payouts.
P.S. Are you curious about why our download counter is called Sisyphus? In Greek mythology, Sisyphus rolls a boulder up a hill for the rest of eternity. Like Sisyphus, our download counter has no point other than to keep increasing for as long as Modrinth exists.
' diff --git a/packages/blog/compiled/download_adjustment.ts b/packages/blog/compiled/download_adjustment.ts new file mode 100644 index 000000000..126e90003 --- /dev/null +++ b/packages/blog/compiled/download_adjustment.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./download_adjustment.content').then((m) => m.html), + title: 'Correcting Inflated Download Counts due to Rate Limiting Issue', + summary: 'A rate limiting issue caused inflated download counts in certain countries.', + date: '2023-11-10T20:00:00.000Z', + slug: 'download-adjustment', + thumbnail: false, + short_title: 'Correcting Inflated Download Counts', +} diff --git a/packages/blog/compiled/index.ts b/packages/blog/compiled/index.ts new file mode 100644 index 000000000..1389e6b1d --- /dev/null +++ b/packages/blog/compiled/index.ts @@ -0,0 +1,50 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +import { article as a_new_chapter_for_modrinth_servers } from './a_new_chapter_for_modrinth_servers' +import { article as accelerating_development } from './accelerating_development' +import { article as becoming_sustainable } from './becoming_sustainable' +import { article as capital_return } from './capital_return' +import { article as carbon_ads } from './carbon_ads' +import { article as creator_monetization } from './creator_monetization' +import { article as creator_update } from './creator_update' +import { article as design_refresh } from './design_refresh' +import { article as download_adjustment } from './download_adjustment' +import { article as knossos_v2_1_0 } from './knossos_v2_1_0' +import { article as licensing_guide } from './licensing_guide' +import { article as modpack_changes } from './modpack_changes' +import { article as modpacks_alpha } from './modpacks_alpha' +import { article as modrinth_app_beta } from './modrinth_app_beta' +import { article as modrinth_beta } from './modrinth_beta' +import { article as modrinth_servers_beta } from './modrinth_servers_beta' +import { article as new_site_beta } from './new_site_beta' +import { article as plugins_resource_packs } from './plugins_resource_packs' +import { article as redesign } from './redesign' +import { article as two_years_of_modrinth_history } from './two_years_of_modrinth_history' +import { article as two_years_of_modrinth } from './two_years_of_modrinth' +import { article as whats_modrinth } from './whats_modrinth' +import { article as windows_borderless_malware_disclosure } from './windows_borderless_malware_disclosure' + +export const articles = [ + a_new_chapter_for_modrinth_servers, + accelerating_development, + becoming_sustainable, + capital_return, + carbon_ads, + creator_monetization, + creator_update, + design_refresh, + download_adjustment, + knossos_v2_1_0, + licensing_guide, + modpack_changes, + modpacks_alpha, + modrinth_app_beta, + modrinth_beta, + modrinth_servers_beta, + new_site_beta, + plugins_resource_packs, + redesign, + two_years_of_modrinth_history, + two_years_of_modrinth, + whats_modrinth, + windows_borderless_malware_disclosure, +] diff --git a/packages/blog/compiled/knossos_v2_1_0.content.ts b/packages/blog/compiled/knossos_v2_1_0.content.ts new file mode 100644 index 000000000..2562b113f --- /dev/null +++ b/packages/blog/compiled/knossos_v2_1_0.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'It\'s officially been a bit over a week since Modrinth launched out of beta. We have continued to make improvements to the user experience on the website.
We\'ve added a number of new features to improve your experience.
In the gallery page of a project, you can now click on the images to expand the image and view it more closely. You can also use the left arrow, right arrow, and Escape keyboard keys to aid navigation.
Versions on the Changelog and Versions page can now be filtered by mod loader and Minecraft version.
The link to the list of your followed projects is now listed in your profile dropdown.
While new features are great, we\'ve also been working on a bunch of bugfixes. Below is a list of some of the notable fixes, but it is not a comprehensive list.
Minotaur, our Gradle plugin, has also received a few fixes. This isn\'t going to be relevant to most people, but is relevant to some developers using this tool to deploy their mods.
debugMode = true) allows previewing the data to be uploaded before uploadingdoLast and related methods not being usable because the task was registered in afterEvaluateThese fixes should have been automatically pulled in, assuming you\'re using Minotaur 2.+. If not, you should be upgrading to 2.0.2.
Need a guide to migrate from Minotaur v1 to v2? Check the migration guide on the redesign post.
' diff --git a/packages/blog/compiled/knossos_v2_1_0.ts b/packages/blog/compiled/knossos_v2_1_0.ts new file mode 100644 index 000000000..168e60b8e --- /dev/null +++ b/packages/blog/compiled/knossos_v2_1_0.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./knossos_v2_1_0.content').then((m) => m.html), + title: 'This week in Modrinth development: Filters and Fixes', + summary: + 'After a great first week since Modrinth launched out of beta, we have continued to improve the user interface based on feedback.', + date: '2022-03-09T00:00:00.000Z', + slug: 'knossos-v2.1.0', + thumbnail: true, +} diff --git a/packages/blog/compiled/licensing_guide.content.ts b/packages/blog/compiled/licensing_guide.content.ts new file mode 100644 index 000000000..8ccc80df7 --- /dev/null +++ b/packages/blog/compiled/licensing_guide.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Why do you need to license your software? What are those licenses for anyway? These questions are more important than you think
To summarise the Wikipedia article on the matter, it\'s essentially a legal contract between you (the mod developer) and anyone who uses, copies, modifies, etc the mod or any code having to do with it. License has the power to allow people to do whatever they want, or only permit the usage of the mod in-game. However, the majority of cases lie in-between these opposites.
First and foremost, the choice of the software license is not entirely up to you, because you have to have the legal ability to do so. For instance, not all licenses are compatible with Minecraft\'s EULA (End-User License Agreement). Besides, if you are not the only one working on the project, you must get permission from all other contributors to your code before changing or adding a license. Please, ensure you have done so before implementing a license.
Before we can decide which one to use, however, we must establish some additional definitions. Open software licenses can be split into three main categories: public domain, permissive, and copyleft.
A permissive license is a type of license that usually gives the abilities to use, copy, modify, distribute, sell, and relicense a piece of software.
The most popular license on Modrinth, the MIT License, is a permissive license. It is an easy-to-read license designed to be used for developers, which is why it is used extensively in the Minecraft open source community.
The Apache License 2.0 is also a very good permissive license to use. The main difference between it and the MIT License is that the Apache License gives an explicit patent grant, whereas patents must be registered manually with the MIT. There is also an additional clause with the Apache License, stating that any modified files must "carry prominent notices" of it being modified.
A copyleft license gives to the other party specific rights usually only given to the copyright owner, under the condition that those same rights are applied to all variations of that software. These are also sometimes called "viral" or "infectious" licenses, because of the requirement to pass those rights on to derivatives.
The second most common license on Modrinth is a copyleft license: the GNU Lesser General Public License Version 3 (usually shortened to LGPL-3.0).
Typically, when a copyleft license is wanted, the GPL-3.0 or AGPL-3.0 would be used. However, these licenses are incompatible if linking into Minecraft, due to an issue with the difference between proprietary and free software outlined by these licenses (more information here). An exception can be added to allow linking, such as that found here, but it is recommended to just use the LGPL-3.0 instead if possible.
A public domain dedication gives all rights to everyone who gets a copy of the software. This includes but is not limited to the ability to use, copy, modify, distribute, sell, or relicense that software. Software with a public domain dedication has no copyright holder.
The third most common license used on Modrinth is the Creative Commons Zero 1.0 Universal, which is a public domain dedication with a strong international legal basis, while still retaining trademark and patent rights.
Creative Commons licenses as a whole are not recommended for software, but rather for other creative works: use this license with caution. If you wish to have the simplest public domain dedication possible, the Unlicense is also an option.
Without a license software is considered proprietary and all rights reserved. This means that people may only use it in the ways the copyright owner specifies, which, in the Minecraft world (no pun intended), typically just means downloading and using it; no modifications, unauthorized distributions: basically nothing.
This is why picking a proper software license is so important. It tells everyone what they can and cannot do with your software, making the difference between software anyone can contribute to and change however they want, and software that only you have the code behind.
That being said, All Rights Reserved and not using a license are options, if you don\'t want to choose a public domain, permissive, or copyleft license. This can be useful in some cases, but as with any license, be aware of the effects: contributions will be difficult or impossible, and users may be inclined not to use your software. Also, in case of Minecraft, all mods, including the All Rights Reserved mods, are affected by Minecraft\'s EULA, which states:
Any Mods you create for the Game from scratch belong to you (including pre-run Mods and in-memory Mods) and you can do whatever you want with them, as long as you don\'t sell them for money / try to make money from them and so long as you don\'t distribute Modded Versions of the Game.
What this means is you are not allowed to sell your mods even if you reserve all rights to them. There are plenty more examples of such details in licenses and other legal agreements in the modding world. All in all, be aware that you cannot decide all of your and other\'s rights with your license.
To conclude, the importance of a software license cannot be overstated. You can choose whatever license you want (assuming you have the legal ability, of course), but be aware of the differences and consequences of choosing one over another. The licenses we\'ve specified are what we recommend, as they are common and easy to understand. Hopefully, you will make your decision based on what you want to use and what your goals and purposes are.
A massive thank you goes to Alexander Ryckeboer (Progryck) for the cover image!
We are not lawyers, and thus, this is not legal advice. No warranty is given regarding this information, and we (Modrinth) disclaim liability for damages resulting in using this information given on an "as-is" basis. For more information on the legal aspect to software licensing, please refer to "The Legal Side of Open Source".
No matter your choice of license, by uploading any Content (including but not limited to text, software, and graphics) to Modrinth, you give us certain rights to your Content, including but not limited to the ability to use, reproduce, or distribute. For more information, please see the Modrinth Terms of Use.
Measurements for "most popular license", "second most common license", and "third most common license", were taken 2021-04-30. Custom licenses were not taken into account.
' diff --git a/packages/blog/compiled/licensing_guide.ts b/packages/blog/compiled/licensing_guide.ts new file mode 100644 index 000000000..c3bbd1fbd --- /dev/null +++ b/packages/blog/compiled/licensing_guide.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./licensing_guide.content').then((m) => m.html), + title: "Beginner's Guide to Licensing your Mods", + summary: + "Software licenses; the nitty-gritty legal aspect of software development. They're more important than you think.", + date: '2021-05-16T00:00:00.000Z', + slug: 'licensing-guide', + thumbnail: true, +} diff --git a/packages/blog/compiled/modpack_changes.content.ts b/packages/blog/compiled/modpack_changes.content.ts new file mode 100644 index 000000000..588841a2c --- /dev/null +++ b/packages/blog/compiled/modpack_changes.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + "CurseForge CDN links requested to be removed by the end of the month
Modrinth's alpha launch of modpacks has been highly successful in the nearly two weeks it has been live, with over forty packs launched to the platform. However, a number of these packs include links to download mods from CurseForge's CDN, which has caught the attention of CurseForge. On May 24th, 2022, a representative from Overwolf sent email correspondence to us demanding us to remove all modpacks and documentation that contain references to CurseForge CDN links by the end of the month. The message was vague, and didn't specify whether or not they were making a legal threat against us or not, so we responded in attempt to clarify what would happen if we chose not to comply. In response, they told us that they would "consider next steps."
Modrinth has every intention of complying with their demands, despite our belief that this is a huge loss for the community. However, CurseForge's immediate "next steps" were to message launcher developers, requesting that they break support for Modrinth packs that contain CurseForge CDN links, and claiming to them that we outright refused to remove the packs containing the links from our platform ourselves when we did not refuse.
To be clear, Modrinth condemns the anti-competitive behaviors that CurseForge are engaging in, however, we do not wish for CurseForge or authors who have elected to opt-out of third party downloads from their platform to be our enemies. Modrinth is and will always remain a project in support of open source software, with open and free APIs for all to use, and encouraging of much needed competition and diversity in the mod hosting space.
Unfortunately, in order to comply with their request, all Modrinth modpacks must now use override JARs in place of any links to CurseForge's CDN. Specifically, CDN links to edge.forgecdn.net and media.forgecdn.net will no longer be part of the .mrpack specification, effective today. Of course, modpack authors must ensure that they are properly licensed to redistribute any mods that are not hosted on the Modrinth platform. While this is a huge blow to modpack creators and users of our platform for now, relying on CurseForge CDN links has always been unreliable as a long-term solution, because they could choose to change the links at any time, and it leaves variables outside of our control. In the long run, packs containing mostly mods hosted on Modrinth will be better for the growth of our platform and for the stability of modpacks.
In order to use mods exclusively hosted on CurseForge as override JARs, pack creators must ensure that either of the following conditions must be met:
In order to aid in this process, Modrinth will be building a third party mod license database and automated tools that will help pack creators with the hassle that will be ensuring all of the mods in their packs are properly licensed. In addition, packs will continue to be hand-reviewed by Modrinth moderation staff and verified. Do note that in this transition time, the review process for modpack projects may experience significant delays. Authors of existing modpacks on the platform will be reached out to in order to help them convert their existing packs to compliant packs.
For those wondering, our next steps as a company are:
After over a year of development, Modrinth is happy to announce that modpack support is now in alpha testing!
What does alpha mean, exactly? Principally, it means that modpack support is still unstable and that not everything is perfect yet. However, we believe it to be complete enough that it can be released for general use and testing.
From this point forward, Modrinth has shifted development effort from modpacks to creator payouts. This long-anticipated feature means that mod developers, modpack creators, and anyone else who uploads content to Modrinth will be eligible to get the ad revenue generated from their project pages.
Right next to mods on the site! URLs to modpacks are the same as mods, just with mod replaced with modpacks, so you can find the search at https://modrinth.com/modpacks.
Over a dozen modpacks have already been created by our early pack adopters, and those are available for download right now!
At this point in time, the only stable way to download modpacks and use them is through ATLauncher. You can also install Modrinth packs if you switch to the development branch of MultiMC. We\'re hoping to be supported by more launchers in the future, including our own launcher, which is still in development. Our documentation for playing modpacks will always have an up-to-date listing of the most popular ways to play packs.
You can either use ATLauncher or packwiz to create modpacks. The Modrinth format is unique for our purposes, which is specifically in order to allow mods from multiple platforms to be in a pack. Our documentation for creating modpacks will always have an up-to-date listing of the most popular ways to create packs.
Yes! The Modrinth format uses a link-based approach, meaning that theoretically, mods from any platform are usable. In practice, we are only allowing links from Modrinth, CurseForge, and GitHub. In the future, we may allow other sites.
For a while, we\'ve been teasing Theseus, our own launcher. While lots of progress has been made on it, we haven\'t yet gotten it to a usable state even for alpha testing. Once we think it\'s usable, we will provide alpha builds -- however, for now, our main focus will be shifting to payouts, with Theseus development ramping up once that is out.
Remember: Modrinth only has a small team, and we have a lot of real-life responsibilities too. If you have experience in Rust or Svelte and would like to help out in developing it, please feel free to shoot a message in the #launcher channel in our Discord.
All in all, this update is quite exciting for everyone involved. Just like with the redesign, this is the culmination of months upon months of work, and modpack support is really a big stepping stone for what\'s still yet to come.
Remember: alpha means that it\'s still unstable! We are not expecting this release to go perfectly smoothly, but we still hope to provide the best modding experience possible. As always, the fastest and best way to get support is through our Discord.
Next stop: creator payouts!
' diff --git a/packages/blog/compiled/modpacks_alpha.ts b/packages/blog/compiled/modpacks_alpha.ts new file mode 100644 index 000000000..c8803ec21 --- /dev/null +++ b/packages/blog/compiled/modpacks_alpha.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./modpacks_alpha.content').then((m) => m.html), + title: 'Modrinth Modpacks: Now in alpha testing', + summary: + "After over a year of development, we're happy to announce that modpack support is now in alpha testing.", + date: '2022-05-15T00:00:00.000Z', + slug: 'modpacks-alpha', + thumbnail: true, +} diff --git a/packages/blog/compiled/modrinth_app_beta.content.ts b/packages/blog/compiled/modrinth_app_beta.content.ts new file mode 100644 index 000000000..d8df0cd81 --- /dev/null +++ b/packages/blog/compiled/modrinth_app_beta.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'The past few months have been a bit quiet on our part, but that doesn’t mean we haven’t been working on anything. In fact, this is quite possibly our biggest update yet, bringing the much-anticipated Modrinth App to general availability, alongside several other major features. Let’s get right into it!
Most of our time has been spent working on Modrinth App. This launcher integrates tightly with the website, bringing you the same bank of mods, modpacks, data packs, shaders, and resource packs already available for download on Modrinth.
Alongside that, there are a wealth of other features for you to find, including:
More features will, of course, be coming in the future. This is being considered a beta release. Nonetheless, we’re still very proud of what we’ve already created, and we’re pleased to say that it’s available for download on our website right now at https://modrinth.app. Check it out, play around with it, and have fun!
The second major thing we’re releasing today is a wide range of changes to our authentication system. Security is a top concern at Modrinth, especially following recent events in the modded Minecraft community when several individuals were compromised due to a virus. While Modrinth was not affected directly by this attack, it provided a harrowing reminder of what we’re working with. That’s why we’re pleased to announce three major features today that will strengthen Modrinth’s security significantly: in-house authentication, two-factor authentication, and scoped personal access tokens.
Until today, Modrinth has always used GitHub accounts exclusively for authentication. That changes now. Starting today, you can now connect your Discord, Microsoft, Google, Steam, and/or GitLab accounts to your Modrinth account. You may also forgo all six of those options and elect to use a good ol’ fashioned email and password. No problems with that! (If you’re curious, we store passwords hashed with the Argon2id method, meaning we couldn\'t read them even if we wanted to.)
' diff --git a/packages/blog/compiled/modrinth_app_beta.ts b/packages/blog/compiled/modrinth_app_beta.ts new file mode 100644 index 000000000..98109dbb5 --- /dev/null +++ b/packages/blog/compiled/modrinth_app_beta.ts @@ -0,0 +1,12 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./modrinth_app_beta.content').then((m) => m.html), + title: 'Introducing Modrinth App Beta', + summary: + 'Changing the modded Minecraft landscape with the new Modrinth App, alongside several other major features.', + date: '2023-08-05T20:00:00.000Z', + slug: 'modrinth-app-beta', + thumbnail: false, + short_title: 'Modrinth App Beta and Upgraded Authentication', + short_summary: 'Launching Modrinth App Beta and upgrading authentication.', +} diff --git a/packages/blog/compiled/modrinth_beta.content.ts b/packages/blog/compiled/modrinth_beta.content.ts new file mode 100644 index 000000000..f9f67b24a --- /dev/null +++ b/packages/blog/compiled/modrinth_beta.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'After six months of work, Modrinth enters Beta, helping modders host their mods with ease!
Six months ago, in order to fill a void in the modding community, the project that would eventually become Modrinth was founded. Modrinth was created to bring change to an otherwise stagnant landscape of hosts. Today, Modrinth enters Beta, a huge step forward for Modrinth!
Modrinth\'s brand new design, rolling out with the launch of Beta
If you\'ve checked out Modrinth in the past, here\'s the main things you\'ll notice that have changed:
Modrinth is still in beta, of course, so there will be bugs. In the coming weeks and months, we will be prioritizing fixing the issues that currently exist and continue refining the design in areas that are rough.
If you find any, please report them to the issue tracker: https://github.com/modrinth/code/issues
If you would like to chat about Modrinth, our discord is open to all here: https://discord.modrinth.com
' diff --git a/packages/blog/compiled/modrinth_beta.ts b/packages/blog/compiled/modrinth_beta.ts new file mode 100644 index 000000000..f56201ce8 --- /dev/null +++ b/packages/blog/compiled/modrinth_beta.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./modrinth_beta.content').then((m) => m.html), + title: 'Welcome to Modrinth Beta', + summary: + 'After six months of work, Modrinth enters Beta, helping modders host their mods with ease!', + date: '2020-12-01T00:00:00.000Z', + slug: 'modrinth-beta', + thumbnail: true, +} diff --git a/packages/blog/compiled/modrinth_servers_beta.content.ts b/packages/blog/compiled/modrinth_servers_beta.content.ts new file mode 100644 index 000000000..ed149b9ef --- /dev/null +++ b/packages/blog/compiled/modrinth_servers_beta.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + "It's been almost four years since we publicly launched Modrinth Beta. Today, we're thrilled to unveil a new beta release of a product we've been eagerly developing: Modrinth Servers.
Modrinth Servers aims to provide the most seamless experience for running and playing on modded servers. To make this possible, we have partnered with our friends at the server hosting provider Pyro. Together, we've developed fully custom software that gives us a unique advantage in scaling, offering new features and integrations that other hosts couldn't dream of.
For this beta launch, all servers are US-only. Please be aware of this if you are looking to purchase a server, as it may not be optimal for users outside of North America.
![\"A](\"./panel.jpg\")
We understand that entering the server hosting industry might come as a surprise given the number of existing providers. Here's what sets Modrinth Servers apart:
Your modpack shouldn't have to run slow. All our servers are powered by cutting-edge 2023 Ryzen 7 and Ryzen 9 CPUs with DDR5 memory. From our research, we couldn't find any other Minecraft server host offering such modern hardware at any price point, much less at our affordably low one. This ensures smooth performance even with the most demanding modpacks.
Download mods and modpacks directly from Modrinth without any hassle. This deep integration simplifies server setup and management like never before. With just a few clicks, you can have your server up and running with your favorite mods.
Unlike most other server hosts that rely on off-the-shelf software like Multicraft or Pterodactyl, Modrinth Servers is fully custom-built from front to back. This enables higher performance and much deeper integration than is otherwise possible. Our intuitive interface makes server management a breeze, even for newcomers.
Our team is committed to providing exceptional support. Whether you're experiencing technical issues or have questions, we're here to ensure your experience with Modrinth Servers is top-notch.
Modrinth Servers are offered in a very simple Small, Medium, and Large pricing model, and are priced based on the amount of RAM at $3/GB. Custom URLs, port configuration, off-site backups, and plenty of storage is included in every Modrinth Server purchase at no additional cost.
As this is a beta release, there's much more to come for Modrinth Servers:
And so much more... stay tuned!
We can't wait for you to try out Modrinth Servers and share your feedback. This is just the beginning, and we're excited to continue improving and expanding our services to better serve the Minecraft community.
From the teams at Modrinth and Pyro, with <3
" diff --git a/packages/blog/compiled/modrinth_servers_beta.ts b/packages/blog/compiled/modrinth_servers_beta.ts new file mode 100644 index 000000000..237161c99 --- /dev/null +++ b/packages/blog/compiled/modrinth_servers_beta.ts @@ -0,0 +1,11 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./modrinth_servers_beta.content').then((m) => m.html), + title: 'Host your own server with Modrinth Servers — now in beta', + summary: 'Fast, simple, reliable servers directly integrated into Modrinth.', + date: '2024-11-03T06:00:00.000Z', + slug: 'modrinth-servers-beta', + thumbnail: true, + short_title: 'Introducing Modrinth Servers', + short_summary: 'Host your next Minecraft server with Modrinth.', +} diff --git a/packages/blog/compiled/new_site_beta.content.ts b/packages/blog/compiled/new_site_beta.content.ts new file mode 100644 index 000000000..3b11bddf3 --- /dev/null +++ b/packages/blog/compiled/new_site_beta.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + "Update 04/02: Due to a number of (ridiculous) complaints we received such as “not being able to use the site on mobile” and “the ads are a bit much”, we have decided to halt the rollout of the beta site. Happy April 1st, everyone.
OwO hewwo evewyone! I'm super exdited to announth that Modwinth is getting a bwand new update! WOOHOO! But, befowe I dwelve into the detaiws, I want to apologize in advance because my grammar and spwelling might not be the best (teehee). Anyway, this new update is going to be sow awesome and is going to make Modwinth the best modding website evew!
But first, a quick message to all of our mobile users: We don't cawe about you anymore! insert evil laughter here We've decided to focus all of our efforts on desktop users, so we won't be supporting mobile devices anymore. If you want to use Modwinth, you'll have to buy a desktop or laptop computer! (LOL)
And that's not aww, we've also added a bunch mowe ads! Because, wet's face it, who doesn't wove ads? Am I wight? (hehe) We've added ads that will pop up evewy five seconds, so you won't miss them. And to make suwe you don't get bowed of seeing the same ad over and over again, we've made suwe to wotate them frequently. You'we welcome! UwU
Oh, and did I mention the nyew wayout and design? We've made it weally cool! YAY! We wanted to make suwe that UwU aww feel a sense of nyostalgia and weminisce about the good owd days of the intewnet. Wemembew those days when websites wooked wike they wewe made by a 5-yeaw-owd? Well, we've bwought that back! (WINKY WINK)
The Fitneshgwam Pacew Test is a multistage aewobic capabiwity test that pwogwessively gets mowe difficult as it continyues. The 20 metew pacer test will begin in 30 seconds. Nyya~ Meowmeow! Win the pacer test you must weach the othew end befowe the beep. Each time you hear the beep meow, uwu wun nyya to the othew end nya. The wun nya must be in wine with the beep. Meowmeow! The eawwier nya you wun, the mowe time you have to westa nya. If you faiw to weach the othew end befowe the beep nya meow, the test will end. So twy youw best and Gud wuck!
In suwummawy, we'we weally excited about the nyew changes and we hope UwU awe too! Modwinth is no wonger a pwace for everyone, but wather, for deskto-p users onwy. We've also added mowe ads than evew befowe and made suwe to make the wayout and design as tewwible as possibwe!
Enjoy! UwU
" diff --git a/packages/blog/compiled/new_site_beta.ts b/packages/blog/compiled/new_site_beta.ts new file mode 100644 index 000000000..357d8dcd5 --- /dev/null +++ b/packages/blog/compiled/new_site_beta.ts @@ -0,0 +1,11 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./new_site_beta.content').then((m) => m.html), + title: '(April Fools 2023) Powering up your experience: Modrinth Technologies™️ beta launch!', + summary: "Welcome to the new era of Modrinth. We can't wait to hear your feedback.", + date: '2023-04-01T08:00:00.000Z', + slug: 'new-site-beta', + thumbnail: true, + short_title: '(April Fools 2023) Modrinth Technologies™️ beta launch!', + short_summary: 'Power up your experience.', +} diff --git a/packages/blog/compiled/plugins_resource_packs.content.ts b/packages/blog/compiled/plugins_resource_packs.content.ts new file mode 100644 index 000000000..897f850a0 --- /dev/null +++ b/packages/blog/compiled/plugins_resource_packs.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'With the addition of modpacks, creating new project types has become a lot easier. Our first additions to our new system are plugins and resource packs. We\'ll also be working on adding datapacks, shader packs, and worlds after payouts are released.
Don\'t worry - this hasn\'t taken away an awful lot of development time from author payouts. Those are still being worked on!
With plugins, we\'re supporting five loaders and three proxies: Bukkit, Spigot, Paper, Purpur, Sponge, BungeeCord, Waterfall, and Velocity.
Several new categories have specifically been added for plugins, though mod categories can be used for plugins and vice versa.
This is a question we\'ve received quite often since we first announced our intention to host plugins, so let\'s break it down a bit.
Currently, there are three main platforms on which plugins can be downloaded from: Bukkit, Spigot, and Sponge\'s Ore. Notice the main issue there? These sites are bound to a specific loader. This isn\'t inherently bad - however, as forks and new projects spawn, there is a noticeable lack of flexibility in what can be hosted on a given platform. For example, Spigot is unable to host plugins which specifically depend on the exclusive features provided by Paper\'s API. Paper\'s solution to this is to build their own platform, but this simply perpetuates the same problem.
The best solution here is to create a separate platform which is unbiased and flexible enough to adapt to a changing ecosystem. Modrinth is the perfect candidate for this - after all, plugins are mods under a different name, and likewise mods are plugins under a different name.
No matter the situation, authors are always allowed to upload their plugins to multiple sites. Build automation is incredibly easy to set up, especially with "set it and forget it" build tools such as Minotaur.
No. Modrinth does not have the infrastructure to support this, and it\'s not currently planned. Author payouts are still being worked on.
Modrinth is taking a unique approach to this. While the search pages are separate, in reality, the backend is the same. You can select plugin loaders when creating a mod and you can select mod loaders when creating a plugin. The split only exists on the frontend so that projects like Chunky can share a single page across their versions.
Plugins which also have versions for mod loaders will be displayed under the /mod/ URL on the frontend. Plugins without mod loader versions are displayed under /plugin/.
The other thing we\'ve added support for is resource packs!
Previously we hinted at Bedrock resource packs being supported in addition to Java resource packs. We\'ve decided not to add Bedrock resource packs until we also add support for other Bedrock resources for various technical reasons.
Go browse our resource pack section!
Resource packs are capable of adding a wide range of different things, like fonts, sounds, and core shaders. We found that the current category system was inadequate to account for all of these, especially with the three maximum limit. Thus, we\'ve introduced a "secondary category" system, for categories which don\'t display by default but can still be searched. These secondary categories have a limit of 255 instead of three. Please add as many secondary categories as are relevant!
On search pages, "Features" have been split into their own header. Where categories for resource packs can be accurately described as themes, features instead show what exactly a resource pack adds. Resolutions have also been split into their own header, though selecting a pack resolution is optional.
Resource packs are able to set dependencies on other projects (even those which aren\'t resource packs), just like how modpacks are able to set dependencies on mods. It\'s worth noting that OptiFine is not on the platform, and thus you cannot set a dependency on that; however, you can set a dependency on any of the other alternative mods which are available on Modrinth, including Entity Texture Features, OptiGUI, Continuity, CIT Resewn, Animatica, or Custom Entity Models.
For a long time, version numbers have had a requirement to be unique within the same project. Alongside this update, we found it necessary to remove this restriction on version numbers. Thus, you\'ll no longer have to use something like 1.2.3+forge and 1.2.3+fabric if you have a project on multiple loaders - instead, you can just use 1.2.3.
To accommodate this, the frontend now appends the loaders and game versions onto the end of a URL if there are duplicates, and the Modrinth Maven now supports version IDs.
We do not recommend retroactively changing version numbers to remove this additional metadata, though. If you change your version numbers, the following will break:
Modrinth now supports LiteLoader for mods. It\'s nothing special, but it should help with some archival efforts.
We\'ve also deleted the Misc category as no one is going to want to filter by Misc in search. If you have any other suggestions for categories, feel free to suggest them in our Discord or Tweet at us!
The changes in this update are rather minimal when it comes to API-related stuff. Two new fields have been added to the project struct - approved, which is the timestamp of when the project was approved (null if it\'s not approved or unlisted), and additional_categories, another set of categories which are to be seen as less important than normal categories. You can read the secondary categories section for more info on it. If you wish to implement the headers in your API integration, the category list now has a header field.
As for the search result struct, created now matches the approved date rather than the published project field, and categories now also includes secondary categories. A new field, display_categories, matches only primary categories.
Differences between mod loaders and plugins will need to be hardcoded within your API integration for the time being if you wish to have them shown separately. This will be cleaned up in API v3 alongside a general cleanup of a lot of other small aspects of the API. If you have any suggestions for breaking API v3 changes, feel free to suggest them in our Discord. Development on API v3 is likely to begin before the end of the year.
We\'re very happy to be announcing this feature, even if it is minor in comparison to some of our other past and future announcements. Don\'t worry - author payouts are still being worked on, and will most likely be our next major announcement! We saw this as an opportunity to get a feature out with relatively little new code (since we\'d already done everything needed alongside modpacks), so we ran with it.
As always, feel free to provide feedback on our Discord, and please report any bugs you come across on our GitHub.
' diff --git a/packages/blog/compiled/plugins_resource_packs.ts b/packages/blog/compiled/plugins_resource_packs.ts new file mode 100644 index 000000000..cd80c3bbc --- /dev/null +++ b/packages/blog/compiled/plugins_resource_packs.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./plugins_resource_packs.content').then((m) => m.html), + title: 'Plugins and Resource Packs now have a home on Modrinth', + summary: + 'A small update with a big impact: plugins and resource packs are now available on Modrinth!', + date: '2022-08-27T00:00:00.000Z', + slug: 'plugins-resource-packs', + thumbnail: true, +} diff --git a/packages/blog/compiled/redesign.content.ts b/packages/blog/compiled/redesign.content.ts new file mode 100644 index 000000000..06d08078e --- /dev/null +++ b/packages/blog/compiled/redesign.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'After months of relatively quiet development, Modrinth has released many new features and improvements, including a redesign. While we\'ve been a bit silent recently on the website and blog, our Discord server has activity on the daily. Join us there and follow along with the development channels for the very latest information!
For both those who aren\'t in the Discord and for those who are, this serves as a status update for what exactly has been going on in our silence. There have been an unparalleled amount of changes, improvements, bug fixes, and new features being worked on since April 2021, and we are incredibly excited to share them with everyone. There are still many things we\'re still working on, such as modpacks, but we\'ve decided to hold back on that as there is still some fine-tuning that needs to be done on that front.
The frontend has received a considerable facelift. With designs made in part by falseresync (and a sprinkle of bikeshedding), we present to you, the redesign!
As they say, a picture tells somewhere around nine-hundred odd words. As such, this section will be heavily focused on screenshots of the pages rather than long descriptions.
A beautiful project page for Iris to match its beautiful shaders
On project pages, much of the focus has been shifted to the extended description rather than the metadata, which has been put over on the side. We\'ve also added an option to switch this from the left side to the right side in your user settings, if you so desire.
Pictures... pretty!
Developers can now add a Gallery section on each project page! Each uploaded image or GIF can have a title and description associated with them.
A changelog page for showing the difference between updates!
Version changelogs are automatically compiled together into a large changelog list. These are put in reverse chronological order, and are separated for Fabric and Forge versions.
Version creation has gotten an overhaul!
While dependencies have existed in the backend for a while, their implementation was a bit haphazard and was never widely used due to never being in the frontend. Thus, all previous dependencies have been wiped, and they have been redone better(TM). And hey, now you can add and see dependencies in the frontend!
The new settings panel for managing your profile and other visual settings
The dashboard has been reworked and reorganized: the "My mods" section has been merged into the profile page itself, and the "Settings" page has been split into "Profile" and "Security". There are also options for switching the project and search information from the left side of the screen to the right.
The notifications page is also now its own page separate from the dashboard, accessible only from the header. The notifications page also has a highly-requested "Clear all" button.
There have been a number of breaking changes in this update, and as such, the API number has been bumped. The /api/ prefix has also been removed, as it\'s redundant when the base API URL is api.modrinth.com. This means the production URL is now api.modrinth.com/v2 instead of api.modrinth.com/api/v1.
The major changes include the universal rename of mod to project, as well as the move of the mod endpoint to search. While version 1 will be supported until January 2024 and won\'t be removed until July 2024, we still highly recommend that applications migrate as soon as possible. For full migration instructions, see the migration guide on the docs site.
Minotaur is the tool for mod developers to upload their mod directly to Modrinth automated through Gradle. Minotaur received a considerable facelift and is now a lot more user-friendly. Previously, an example buildscript might look like this:
task publishModrinth(type: com.modrinth.minotaur.TaskModrinthUpload) {\n onlyIf {\n System.getenv().MODRINTH_TOKEN\n }\n token = System.getenv().MODRINTH_TOKEN\n projectId = \'AABBCCDD\'\n versionNumber = version\n versionName = "[$project.minecraft_version] Mod Name $project.version"\n releaseType = \'alpha\'\n changelog = project.changelog\n uploadFile = remapJar\n addGameVersion(\'1.18\')\n addGameVersion(\'1.18.1\')\n addGameVersion(\'1.18.2\')\n addLoader(\'fabric\')\n}\nThis exact same buildscript snippet, in Minotaur 2.0.0, can be written as the following:
modrinth {\n projectId = \'AABBCCDD\'\n versionName = "[$project.minecraft_version] Mod Name $project.version"\n releaseType = \'alpha\'\n changelog = project.changelog\n uploadFile = remapJar\n gameVersions = [\'1.18\', \'1.18.1\', \'1.18.2\']\n loaders = [\'fabric\']\n dependencies = [\n new ModDependency(\'P7dR8mSH\', \'required\') // Creates a new required dependency on Fabric API\n ]\n}\nNotice how it\'s now in a modrinth {...} block instead of creating a new task. The modrinth task is automatically created.
The loaders declaration in the new version isn\'t even needed if you\'re using Fabric Loom or ForgeGradle. The project version can be detected automatically, and the token uses the MODRINTH_TOKEN environment variable by default now. The game version and loader listings actually make sense now, and dependencies are possible!
Along with the major headlining features, there are also a number of smaller features, fixes, and improvements coming with the big update. Most of these need no more than a bullet to describe, so here\'s a bullet list of the smaller things!
draft status if they contain no versions. Additionally, a new archived status has been added.We\'ve been teasing modpacks for a long time now. While they\'re done for the most part, we\'ve decided to hold back on their release for the time being. We\'re working hard to get those done some time soon, and there\'ll be another post when those are ready for general consumption.
In conclusion, we hope that you\'re excited about this update as much as we are. We believe that, with how much work has been put into this update, it has definitely been worth the wait.
On a separate note, are you looking to contribute to Modrinth? Have you got experience with Rust or Svelte? We\'re hiring! Please reach out to Geometrically#8387 on Discord to apply for a position.
Thank you for reading, and may your dreams be filled with pineapples, tiny potatoes, and squirrels.
' diff --git a/packages/blog/compiled/redesign.ts b/packages/blog/compiled/redesign.ts new file mode 100644 index 000000000..9e9545a95 --- /dev/null +++ b/packages/blog/compiled/redesign.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./redesign.content').then((m) => m.html), + title: 'Now showing on Modrinth: A new look!', + summary: + 'After months of relatively quiet development, Modrinth has released many new features and improvements, including a redesign. Read on to learn more!', + date: '2022-02-27T00:00:00.000Z', + slug: 'redesign', + thumbnail: true, +} diff --git a/packages/blog/compiled/two_years_of_modrinth.content.ts b/packages/blog/compiled/two_years_of_modrinth.content.ts new file mode 100644 index 000000000..f825fbe0e --- /dev/null +++ b/packages/blog/compiled/two_years_of_modrinth.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Modrinth initially went into beta on November 30th, 2020. Just over a month ago was November 30th, 2022, marking two years since Modrinth was generally available as a platform for everyone to use. Today, we\'re proud to announce the Anniversary Update, celebrating both two years of Modrinth as well as the coming of the new year, and we\'ll be discussing our New Year\'s Resolutions for 2023.
Before you read this post, though, we recommend taking a look at our retrospective on Modrinth\'s history through 2020—2022. It just wouldn\'t be right to take a look at the present and the future without also taking a look at our past, seeing how far we\'ve come from our humble beginnings.
With that out of the way, this post primarily serves to announce a few of the smaller features we\'ve been working on after the release of creator monetization. We\'ve bundled these all together as the Anniversary Update.
Looking just at what\'s already done is boring, though, so we\'ll also be looking at what\'s yet to come. Modrinth\'s future is even brighter than any of us can imagine, so we\'ll be focusing on what we\'re gonna do in order to get to that bright future. If you\'ve ever made New Year\'s Resolutions, we\'re going to briefly discuss our resolutions for 2023.
Without further adieu, let\'s get right into what\'s new with this new year!
The long-awaited arrival of shader packs and data packs is now here on Modrinth!
Shader packs can be viewed in the shaders tab. This includes shaders that support Iris, Canvas, and OptiFine, as well as vanilla core shaders. (Even though they\'re installed via the resource pack system, we have decided to put Canvas and core shaders in shader packs since most users will not search in resource packs for shader packs, even if that\'s how they\'re installed.)
Data packs can be found in the data packs tab. These are implemented similarly to plugins, in that projects with a mod version can also upload a data pack version (and vice versa). Additionally, data pack authors can choose to have their data packs packaged as a mod using the handy-dandy button on the site.
Data packs can optionally upload a corresponding resource pack as a separate file. We discourage bundling data files and asset files in the same zip file.
The homepage has been completely remade, featuring a scrolling list of random projects from Modrinth. Feel free to use this to discover new projects—just make sure you refresh occasionally, because they loop after a little while until you refresh!
We\'re continuing to bring expansions to the creator dashboard introduced with monetization. The new Projects tab allows you to view all of your projects in a table and quickly access their information and settings.
The same page also introduces the ability to bulk-edit the external resource links without having to edit each page individually. For example, if your Discord invite expires, you used to have to edit each of your projects individually to add it back. Now you can just select the projects you want to edit the links for and edit them all at the same time!
Even better are the changes to the settings page for individual projects. Previously, the project settings page was disorganized and cluttered. The project settings page has been completely redone, inspired by GitHub\'s repository settings page.
Draft projects also now have a publishing checklist, making it more clear to authors as to what their next steps should look like. Red asterisks are items that must be completed before submitting and purple light bulbs are suggestions.
The layout of the individual version page has gotten a complete overhaul. It\'s much easier to just show the new UI in action rather than trying to explain it!
A screenshot of the way that individual versions look now:
That\'s not all, though. Version creation now automatically infers most details after you upload your first file. Try it out sometime—whenever you upload your first file, most stuff should already be filled in. This system is still in-development, so if you find any issues, please file an issue on GitHub.
Anywhere which lists projects, namely search and user pages, have gotten a great overhaul. You can choose between the classic list view, the grid view, and the gallery view.
By default, shader packs and resource packs use the gallery view, user pages use the grid view, and everywhere else use the list view. You can cycle through them near the top of each page or change them in your display settings.
The gallery image uses the featured gallery image on a project, so please ensure if you are a shader pack or resource pack author that you set a featured gallery image!
The existing UI for gallery image creation, editing, and deletion was flawed in many ways, so we threw out the old way of doing it and created a whole new system for this. It should be less prone to the many many bugs that plagued the previous implementation.
Our Discord server has a brand new channel: #new-projects. A webhook sends a message to this channel every time a new project gets approved. Check it out when you get a chance!
Now that we\'ve looked at everything accomplished over the past month and a half, let\'s take a look at our New Year\'s Resolutions—things we wish to achieve during 2023.
During 2023, our main focus will shift to the Modrinth launcher, code-named Theseus. Progress has been off and on for the past year and a half, but we intend to fully launch it before the end of the year. Theseus will bring a next-level experience to Minecraft launchers, bringing first-class support for Modrinth and unique features that would be difficult for other providers to parallel.
The release of the Theseus project will also mark the end of the "alpha" status for Modrinth modpacks. Stay tuned for more information about alpha tests and early adopters programs!
Another one of our focuses for this year is to put more work into our analytics system and in growing creator monetization through our Adrinth ad network. As of today, monetization is now out of beta, but we are still constantly working on ways to make Modrinth even better and easier to use for new and returning creators. Some of these improvements are big, like the project settings overhaul, while others are more subtle quality-of-life improvements, like the fixes to usage of duplicate version numbers.
This year, Modrinth hopes to introduce version 3 of our API with lots of fixes and smaller changes. While our plans are still work-in-progress for this, one of the things that needs to be done first is the removal of the old API v1, which was deprecated starting in January 2022. Here\'s our planned timeline for the removal of API v1:
As always, we will be interspersing other, smaller quality-of-life updates throughout the year even as we work on the big stuff. We also want to fix any bugs which might come up alongside any updates.
Modrinth was founded with the goal of creating a platform which keeps the broader modding community\'s interests at heart. Modrinth would not exist without the support of our users and of our contributors, and we thank everyone involved immensely for everything. Modrinth\'s development shall continue as long as the community is willing to support us on the way!
We would love to hear any feedback you might have. Feel free to get in contact on Discord, on Twitter, and on Mastodon.
' diff --git a/packages/blog/compiled/two_years_of_modrinth.ts b/packages/blog/compiled/two_years_of_modrinth.ts new file mode 100644 index 000000000..25fdfbe2a --- /dev/null +++ b/packages/blog/compiled/two_years_of_modrinth.ts @@ -0,0 +1,9 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./two_years_of_modrinth.content').then((m) => m.html), + title: "Modrinth's Anniversary Update", + summary: "Marking two years of Modrinth and discussing our New Year's Resolutions for 2023.", + date: '2023-01-07T00:00:00.000Z', + slug: 'two-years-of-modrinth', + thumbnail: true, +} diff --git a/packages/blog/compiled/two_years_of_modrinth_history.content.ts b/packages/blog/compiled/two_years_of_modrinth_history.content.ts new file mode 100644 index 000000000..eeca74046 --- /dev/null +++ b/packages/blog/compiled/two_years_of_modrinth_history.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'Let\'s rewind a bit and take a look at the past two years of Modrinth\'s history. We\'ve come so far from our pre-beta HexFabric days to today. A good portion of our pre-beta history can be found in the What is Modrinth blog post, but Modrinth obviously is not the same platform it was two years ago.
Modrinth\'s brand new design, rolling out with the launch of Beta
December was the release of the initial Modrinth Beta, bringing a completely different interface and the ability for mods to be created for the first time. This interface has since been completely discarded, but this is what Modrinth looked like for well over a year. It\'s hard to believe!
December also brought the introduction of the Minotaur Gradle plugin for the first time for upload automation. Minotaur today also looks nothing like it did when it was introduced, but it still accomplishes the same exact thing.
An announcement in mid-January brought several essential additions and improvements to Modrinth which we consider commonplace today. Among these were:
January also brought the introduction of Google AdSense onto Modrinth. The eventual results, including our switch after to EthicalAds, solidified Modrinth\'s stance that ads should be unobtrusive and generally friendly to users.
March brought the first introduction of the abilities to follow and report projects, as well as the automatic featuring of some versions depending on loader and Minecraft version. These systems have largely remained unchanged since their introduction, though the notification system will likely be getting a refresh come 2023.
After follows, reports, and all that jazz, Modrinth largely went silent for a good while. This time period had some of the largest growth Modrinth had ever seen, and yet it seemed Modrinth\'s development had ground to a halt. Modrinth Team members were dropping like flies until there was a point where there was a single person on the team. What happened?
For various reasons, whether it be lack of free time or a lack of interest in Minecraft in general, people ended up leaving to pursue other things. It\'s not quite as apocalyptic or barren as these descriptions make it seem, but it\'s more fun to describe it like this.
Picking up the remnants from what others had left behind, one man was destined to continue developing for Modrinth. The one who began the whole operation in the first place, Geometrically, stood up and began developing. Thus came the development of project types, gallery images, API v2, and modpacks.
Right around the corner came 2022. Perchance this would be the time for the silence to be broken? Indeed, the world would be able to hear about all that was brewing over the past few months.
Of course, this wasn\'t all introduced at once—it was a gradual rollout over several months. First was the introduction of v2 of Modrinth\'s API, allowing many breaking changes to occur, including namely the renaming of mods to projects. Wait, why was this necessary?
Up until this point, Modrinth only hosted mods. Project types, as we call them, allow projects to be given the designation of something other than mod; for example, modpack or resourcepack, like we have today. This simple field, alongside all of the infrastructure which was needed to support it, was the first step to allow modpacks on Modrinth.
Remember the interface introduced in December 2020? Let\'s scrap it! Actually, it wasn\'t entirely scrapped, but it got a treatment similar to the Ship of Theseus to the point that it was barely recognizable.
The former Modrinth homepage
Alongside this was the official announcement of API v2, as well as the introduction of the project gallery, the changelog tab, dependencies, and many other things. Here\'s the blog post announcement for the redesign!
February also brought the introduction of several new Modrinth Team members to the fold, including Prospector and triphora, both of whom are still on the team, alongside Hutzdog and venashial, who we thank for helping us through much of 2022.
A couple weeks after the redesign we pushed out some changes which included improvements to several tabs on project pages and many bug fixes. The blog post from that can be found here.
The next couple months were spent preparing for the release of modpacks. This is the first introduction of our "early adopters" program, still in use today, allowing a feedback loop of authors and other community members to create the best product that we can. Without early adopters, many of the features on Modrinth which you\'ve come to love, including modpacks, plugins, resource packs, would be less than ideal.
In May, we finally did the big release of modpacks on Modrinth. Well, in alpha, anyway—but that was less of a marker of instability and more a marker of being incomplete without the launcher. The modpack alpha release blog post can be found here.
When we first announced modpacks, the initial format had been set in stone for a couple years, and it had been decided that CurseForge links would be allowed within them. This got turned on its head due to an email sent to us by Overwolf. More information on that can be found on the Changes to Modrinth Modpacks blog post.
The summer of 2022 was largely dedicated to working on releasing creator monetization. First, though, we made a pit stop to introduce plugins and resource packs to Modrinth. Find that blog post here.
Plugins in particular were tricky since we had to account for projects which had both mod and plugin versions. It was at this point we realized that the project type system isn\'t entirely what we cracked it up to be, and we\'re hoping to completely replace it once API v4 rolls around, as far away as that may sound. For now, though, it will suffice.
With plugins and resource packs done, we continued working on creator monetization. This included a brief experiment with a different ad provider before we eventually switched to creating our own ad system.
November brought the actual beta release of creator monetization—here\'s the blog post for that. We are continuing to develop and refine this system to ensure authors continue to earn money from publishing projects on Modrinth.
That, of course, brings us to today\'s Anniversary Update! Now that you\'re done reading this, feel free to go back over to that post and read about everything that\'s new in the Anniversary Update so that I don\'t have to repeat myself. Take a look at our New Year\'s Resolutions for 2023 while you\'re at it, too!
' diff --git a/packages/blog/compiled/two_years_of_modrinth_history.ts b/packages/blog/compiled/two_years_of_modrinth_history.ts new file mode 100644 index 000000000..16cb7cc57 --- /dev/null +++ b/packages/blog/compiled/two_years_of_modrinth_history.ts @@ -0,0 +1,9 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./two_years_of_modrinth_history.content').then((m) => m.html), + title: 'Two years of Modrinth: a retrospective', + summary: 'The history of Modrinth as we know it from December 2020 to December 2022.', + date: '2023-01-07T00:00:00.000Z', + slug: 'two-years-of-modrinth-history', + thumbnail: false, +} diff --git a/packages/blog/compiled/whats_modrinth.content.ts b/packages/blog/compiled/whats_modrinth.content.ts new file mode 100644 index 000000000..e8745e4f8 --- /dev/null +++ b/packages/blog/compiled/whats_modrinth.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + "Hello, we are Modrinth – an open source mods hosting platform. Sounds dry, doesn't it? So let me tell you our story – and I promise, it won't be boring!
Before Modrinth was even thought of, there already were several giant platforms for mod hosting. However, most of them were too specialized, outdated, or transitively dependent on an uncaring hegemonic 3rd party. Authors and players were always in struggle. The community had to choose 2 out of 3: inconvenience, indifference, obsolescence. Urge for better service, either new or renewed, just founded or acquired arose.
Although demand for proper competition is the seed, the germ of Modrinth, the biggest role was played by the Fabric project. It set an example of a community-powered alternative. It was democratic, FOSS, listening to the community, and welcoming contribution and 3rd party initiatives. They have shown the modding community that they can evolve and adapt, be accessible and welcoming, cooperative, and caring.
And, oh boy, did they connect – the demand for competition grew so high, that at some point the community just exploded with novelty. During several months, almost a dozen projects were aiming to be the second Walmart, the third IKEA, the fourth Amazon for your mods. Here beings the story of HexFabrics... – wait, what? What's that?
HexFabric is an umbrella term for modern mod hosting technology. It got its name from Fabric, which at the point was poorly supported (if at all) by the major players on the stage. In practice, HexFabric is just a cozy Discord server, on which several projects have their deputizing channels.
Back on track – Lots of HexFabrics were founded almost simultaneously. Altar.gg, Astronave, Diluv, ModForest, Minerepo... and, most importantly, Fabricate.
Fabricate began its journey as a proprietary project indexing website by a single developer – Geometrically. It remained relatively unnoticed for a couple of weeks, and then it started gaining attention. This new website has amazing search! Yup, the whole thing was primarily about making seamless, gracious, appeasing smart real-time search. The community is now intrigued.
"But this looks awful! And it's proprietary!" – a few voices said. Among those voices were falseresync and MulverineX. They both had several objections to that and were pestering the original author. "FOSS is the true way for community project" and "Just use a license to prevent others from creating instances of your work," they told.
Yet Fabricate remained proprietary for a while. However, once the pressure on the author became high, they gave up and open-sourced their work. This was the birth of Modrinth. It did not get its name for a little while longer though.
Now that Modrinth was open source, it started gaining traction. Remember falseresync and MulverineX? They joined Geometrically on the branding site, and somewhere in the middle of the brainstorming process the logo and the name were born. At the same time AppleTheGolden, Aeledfyr, and Redblueflame began contributing to the actual code of the project, which is – nowadays known to everyone – in Rust. A solo suddenly became a team, ready for whatever future holds.
The newly born FOSS project is now evolving swiftly. Before our team arose the question: monolithic vs split app architecture. Monolithic would be easier to deploy and can serve pages quicker. The split architecture will simplify the development and allow for a feature-full user experience. The discussion was hot, and the sides were fierce. Nevertheless, the split pattern won. Now it was time to make proper backend and frontend apps.
The work first began with the backend. Aeled, Red, and Geo started detaching API methods from visuals. The team worked hard. Consequent to the API splitting from the GUI, it became getting new and exciting features. The first feature to be added was custom Modrinth mods – before that, the website only indexed the competitor's service.
However, for that to happen there had to be another step taken – migration from MongoDB to PostgreSQL. It was crucial for efficient data storage and complex relationships between projects. And the biggest propagator of that change was Apple, who introduced and successfully defended their case.
Thus, with custom mods, better yet search has been implemented. After search, user accounts with external log-in made their way into the project. Now it first creators started uploading their mods – a monumental achievement.
After the first creators came more – the community began taking Modrinth as a serious alternative hosting. At some point, uploads accelerated to the point that our team was forced to redo their plans and establish project editing and moderation considerably earlier than it could have been. Besides, creators need analytics, they need teams, they needed support system. So the backend developers tried their best to keep up and achieved their goals through enthusiastic labor and dedication.
Although, on the frontend side things weren't as bright, unfortunately. Once falseresync presented the new look and feel Modrinth should aim for, he was forced to dedicate less time to the project. As a consequence, the frontend was implemented rather haphazardly and was lacking in features compared to the backend.
However, this did not stop the project from evolving. The backend team has continued to expand on existing features, and after a long period of time, the savior descended on the frontend – Prospector, who rapidly became a crucial contributor and a part of the team. With new and comprehensive design guidance from falseresync and critique from MulverineX and the community, Prospector achieved feature parity with backend and greatly improved the website look and feel.
Improving the frontend wasn't an easy job: naughty CSS, runtime errors, the abundance of framework-related nuances – all were obstacles, and all were defeated. Through battles with web technologies, jokes about quirky styles, and hard work our team created the UI you see today.
You have to believe that the dots will somehow connect in your future. – Steve Jobs
With the story complete, we are proud to announce that the Modrinth beta will be coming out on November 30th, with a refreshed look and a feature-complete modding website! It is a tremendous achievement for us and the community, which we are very proud of.
It is heart-warming to admit that we're finally going officially online. We know it's not perfect yet. But regardless, we will continue our passion project as a team, and we will expand on it and make it only better!
Stay tuned!
" diff --git a/packages/blog/compiled/whats_modrinth.ts b/packages/blog/compiled/whats_modrinth.ts new file mode 100644 index 000000000..d9a86305f --- /dev/null +++ b/packages/blog/compiled/whats_modrinth.ts @@ -0,0 +1,10 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./whats_modrinth.content').then((m) => m.html), + title: 'What is Modrinth?', + summary: + "Hello, we are Modrinth – an open source mods hosting platform. Sounds dry, doesn't it? So let me tell you our story – and I promise, it won't be boring!", + date: '2020-11-27T00:00:00.000Z', + slug: 'whats-modrinth', + thumbnail: false, +} diff --git a/packages/blog/compiled/windows_borderless_malware_disclosure.content.ts b/packages/blog/compiled/windows_borderless_malware_disclosure.content.ts new file mode 100644 index 000000000..911344eb0 --- /dev/null +++ b/packages/blog/compiled/windows_borderless_malware_disclosure.content.ts @@ -0,0 +1,3 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const html = + 'This is a disclosure of a malicious mod discovered to be hosted on the Modrinth platform. It is important to not panic or jump to conclusions, please carefully read the Am I Affected? and Threat Summary sections.
If you run Windows and have downloaded a mod called "Windows Borderless" (specific files listed below) between May 4th, 2024 and May 6th, 2024 and have run the game with the mod installed, you are affected.
IMPORTANT NOTE: This mod is called, exactly, "Windows Borderless". There are other mods with similar names on Modrinth, which are NOT malware, such as "Borderless Mining", "Borderless", and "Borderless Mining Reworked".
If you have not downloaded that mod or do not run Windows, there is no reason to believe you are at any risk. We have released a detection tool available here which can scan your mods folder for the malicious files if you wish to make sure your instance does not have the mod. The tool is also open-source.
Download and run the detection tool here!
First, delete the mod entirely from your computer.
The mod harvested data stored by many Chromium-based projects such as Google Chrome, Discord, Microsoft Edge, and many other browsers such as Opera/Opera GX, Vivaldi, Brave, Firefox and over dozen more. Included in this data may be account tokens, stored passwords, banking information, addresses, and more.
In order to protect yourself, change all of your passwords, and keep an eye out on your bank accounts and credit cards.
Exposure level: Low, ~372 distinct IPs downloaded affected files. One Discord account is alleged to have been stolen due to this.
Malware severity: Medium (Discord, browser, and system info stealer, but does not self-replicate)
Projects affected:
| Name | Project ID | Former URL |
|---|---|---|
| Windows Borderless | ZQpQzwWE | https://modrinth.com/mod/windowsborderless |
Files affected:
| Name | SHA1 Hash | Version ID | Download count |
|---|---|---|---|
windowedborderless-v0.2 - 1.20.4.jar | 179b5da318604f97616b5108f305e2a8e4609484 | NkTbhEmf | 116 |
windowedborderless-v0.3 - 1.20.4.jar | 1a1c4dcae846866c58cc1abf71fb7f7aa4e7352a | v87dk8Q7 | 15 |
windowedborderless-v0.4 - 1.20.+.jar | e4d55310039b965fce6756da5286b481cfb09946 | pVfdgPhy | 68 |
windowedborderless-v0.4 - 1.20.+.jar | 2f47e57a6bedc729359ffaf6f0149876008b5cc3 | Wt4RjZ49 | 119 |
windowedborderless-v0.4.1_-_1.20.+.jar | 2f47e57a6bedc729359ffaf6f0149876008b5cc3 | oIlYelrb | 1 |
None of these files were included in any modpacks on the Modrinth platform, so you are only at risk if you downloaded the mod directly.
The Modrinth project "Windows Borderless" is submitted for review with a single file uploaded that does not contain any malware.
The "Windows Borderless" project is approved with only one file, which contained no malware.
A "Windows Borderless" version containing the file windowedborderless-v0.2 - 1.20.4.jar (mentioned in the table of affected files above) is published. This initial version of the malware did not include any credential or token stealing, but only sent identifying information about a user’s machine to a discord webhook.
Between May 4th, 4:01pm and May 6th, 3:46am, more new versions of the mod containing the malware were uploaded. These versions all contain credential and token stealers.
A user submits a report against the mod, alleging that their Discord account got compromised after using the mod.
The mod is investigated by Modrinth staff. We decompiled the mod and discovered that the mod contained malicious code. The threat is immediately obvious, so within a few minutes we take down the project, all CDN links related to the project, and all other projects by the same users.
In response to this incident, we are actively developing a shared system to effectively quarantine known malicious mods by creating a web API to allow launchers to check if any of the files a user has downloaded match any of the files in our known malware database, and return up-to-date information about any known malware.
We are also in the process with working with relevant law enforcement agencies to pass along all information we have.
In order to also more proactively increase safety, we\'re also investigating possible methods of sandboxing or algorithmically detecting malware patterns in Java software. While these are infamously tricky to implement on certain platforms, we hope to do our best in order to ensure the best security for the modding community.
' diff --git a/packages/blog/compiled/windows_borderless_malware_disclosure.ts b/packages/blog/compiled/windows_borderless_malware_disclosure.ts new file mode 100644 index 000000000..23b58c87f --- /dev/null +++ b/packages/blog/compiled/windows_borderless_malware_disclosure.ts @@ -0,0 +1,9 @@ +// AUTO-GENERATED FILE - DO NOT EDIT +export const article = { + html: () => import('./windows_borderless_malware_disclosure.content').then((m) => m.html), + title: 'Malware Discovery Disclosure: "Windows Borderless" mod', + summary: 'Threat Analysis and Plan of Action', + date: '2024-05-07T20:00:00.000Z', + slug: 'windows-borderless-malware-disclosure', + thumbnail: true, +} diff --git a/packages/blog/index.ts b/packages/blog/index.ts new file mode 100644 index 000000000..33a68a444 --- /dev/null +++ b/packages/blog/index.ts @@ -0,0 +1 @@ +export { articles } from './compiled' diff --git a/packages/blog/package.json b/packages/blog/package.json new file mode 100644 index 000000000..c192ad1d0 --- /dev/null +++ b/packages/blog/package.json @@ -0,0 +1,28 @@ +{ + "name": "@modrinth/blog", + "version": "0.0.0", + "private": true, + "main": "./index.ts", + "types": "./index.d.ts", + "scripts": { + "lint": "jiti ./check.ts && eslint . && prettier --check .", + "fix": "jiti ./compile.ts && eslint . --fix && prettier --write ." + }, + "devDependencies": { + "@types/html-minifier-terser": "^7.0.2", + "@types/rss": "^0.0.32", + "@types/xml2js": "^0.4.14", + "eslint": "^8.57.0", + "eslint-config-custom": "workspace:*", + "jiti": "^2.4.2", + "tsconfig": "workspace:*" + }, + "dependencies": { + "@modrinth/utils": "workspace:*", + "fast-glob": "^3.3.3", + "gray-matter": "^4.0.3", + "html-minifier-terser": "^7.2.0", + "rss": "^1.2.2", + "xml2js": "^0.6.2" + } +} diff --git a/packages/blog/public/a-new-chapter-for-modrinth-servers/thumbnail.webp b/packages/blog/public/a-new-chapter-for-modrinth-servers/thumbnail.webp new file mode 100644 index 000000000..a54d8c13c Binary files /dev/null and b/packages/blog/public/a-new-chapter-for-modrinth-servers/thumbnail.webp differ diff --git a/packages/blog/public/becoming-sustainable/abnormally-high-revenue.webp b/packages/blog/public/becoming-sustainable/abnormally-high-revenue.webp new file mode 100644 index 000000000..0fbefa983 Binary files /dev/null and b/packages/blog/public/becoming-sustainable/abnormally-high-revenue.webp differ diff --git a/packages/blog/public/becoming-sustainable/revenue.webp b/packages/blog/public/becoming-sustainable/revenue.webp new file mode 100644 index 000000000..712d5b1a8 Binary files /dev/null and b/packages/blog/public/becoming-sustainable/revenue.webp differ diff --git a/packages/blog/public/becoming-sustainable/thumbnail.webp b/packages/blog/public/becoming-sustainable/thumbnail.webp new file mode 100644 index 000000000..87c03025c Binary files /dev/null and b/packages/blog/public/becoming-sustainable/thumbnail.webp differ diff --git a/packages/blog/public/carbon-ads/thumbnail.webp b/packages/blog/public/carbon-ads/thumbnail.webp new file mode 100644 index 000000000..72937eb67 Binary files /dev/null and b/packages/blog/public/carbon-ads/thumbnail.webp differ diff --git a/packages/blog/public/creator-monetization/thumbnail.webp b/packages/blog/public/creator-monetization/thumbnail.webp new file mode 100644 index 000000000..e74257f46 Binary files /dev/null and b/packages/blog/public/creator-monetization/thumbnail.webp differ diff --git a/packages/blog/public/creator-update/collections.jpg b/packages/blog/public/creator-update/collections.jpg new file mode 100644 index 000000000..1e822763f Binary files /dev/null and b/packages/blog/public/creator-update/collections.jpg differ diff --git a/packages/blog/public/creator-update/oauth.jpg b/packages/blog/public/creator-update/oauth.jpg new file mode 100644 index 000000000..1d8d1a378 Binary files /dev/null and b/packages/blog/public/creator-update/oauth.jpg differ diff --git a/packages/blog/public/creator-update/organizations.jpg b/packages/blog/public/creator-update/organizations.jpg new file mode 100644 index 000000000..42f135c7c Binary files /dev/null and b/packages/blog/public/creator-update/organizations.jpg differ diff --git a/packages/blog/public/creator-update/payout-methods.jpg b/packages/blog/public/creator-update/payout-methods.jpg new file mode 100644 index 000000000..8e3717e73 Binary files /dev/null and b/packages/blog/public/creator-update/payout-methods.jpg differ diff --git a/packages/blog/public/creator-update/project-analytics.jpg b/packages/blog/public/creator-update/project-analytics.jpg new file mode 100644 index 000000000..a566a226f Binary files /dev/null and b/packages/blog/public/creator-update/project-analytics.jpg differ diff --git a/packages/blog/public/creator-update/thumbnail.webp b/packages/blog/public/creator-update/thumbnail.webp new file mode 100644 index 000000000..0096172d1 Binary files /dev/null and b/packages/blog/public/creator-update/thumbnail.webp differ diff --git a/packages/blog/public/creator-update/user-analytics.jpg b/packages/blog/public/creator-update/user-analytics.jpg new file mode 100644 index 000000000..a554c43ed Binary files /dev/null and b/packages/blog/public/creator-update/user-analytics.jpg differ diff --git a/packages/blog/public/creator-update/user-orgs.jpg b/packages/blog/public/creator-update/user-orgs.jpg new file mode 100644 index 000000000..fab723916 Binary files /dev/null and b/packages/blog/public/creator-update/user-orgs.jpg differ diff --git a/packages/blog/public/design-refresh/project-page.webp b/packages/blog/public/design-refresh/project-page.webp new file mode 100644 index 000000000..d422f3b41 Binary files /dev/null and b/packages/blog/public/design-refresh/project-page.webp differ diff --git a/packages/blog/public/design-refresh/thumbnail.webp b/packages/blog/public/design-refresh/thumbnail.webp new file mode 100644 index 000000000..946148fc6 Binary files /dev/null and b/packages/blog/public/design-refresh/thumbnail.webp differ diff --git a/packages/blog/public/download-adjustment/country-download-counts.jpg b/packages/blog/public/download-adjustment/country-download-counts.jpg new file mode 100644 index 000000000..067dd0e55 Binary files /dev/null and b/packages/blog/public/download-adjustment/country-download-counts.jpg differ diff --git a/packages/blog/public/download-adjustment/country-page-views.jpg b/packages/blog/public/download-adjustment/country-page-views.jpg new file mode 100644 index 000000000..2e9c1b50e Binary files /dev/null and b/packages/blog/public/download-adjustment/country-page-views.jpg differ diff --git a/packages/blog/public/download-adjustment/downloads-table.jpg b/packages/blog/public/download-adjustment/downloads-table.jpg new file mode 100644 index 000000000..d8e1fccb4 Binary files /dev/null and b/packages/blog/public/download-adjustment/downloads-table.jpg differ diff --git a/packages/blog/public/download-adjustment/new-sisyphus.jpg b/packages/blog/public/download-adjustment/new-sisyphus.jpg new file mode 100644 index 000000000..a2245e52a Binary files /dev/null and b/packages/blog/public/download-adjustment/new-sisyphus.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/download-icon.jpg b/packages/blog/public/knossos-v2.1.0/download-icon.jpg new file mode 100644 index 000000000..b75585e63 Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/download-icon.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/dropdown-caret.jpg b/packages/blog/public/knossos-v2.1.0/dropdown-caret.jpg new file mode 100644 index 000000000..8fbf864c2 Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/dropdown-caret.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/expand-gallery.jpg b/packages/blog/public/knossos-v2.1.0/expand-gallery.jpg new file mode 100644 index 000000000..8dac16332 Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/expand-gallery.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/following.jpg b/packages/blog/public/knossos-v2.1.0/following.jpg new file mode 100644 index 000000000..ffc419500 Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/following.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/styling.jpg b/packages/blog/public/knossos-v2.1.0/styling.jpg new file mode 100644 index 000000000..14ae57b60 Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/styling.jpg differ diff --git a/packages/blog/public/knossos-v2.1.0/thumbnail.webp b/packages/blog/public/knossos-v2.1.0/thumbnail.webp new file mode 100644 index 000000000..f1b92f17e Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/thumbnail.webp differ diff --git a/packages/blog/public/knossos-v2.1.0/version-filters.jpg b/packages/blog/public/knossos-v2.1.0/version-filters.jpg new file mode 100644 index 000000000..87f772c0b Binary files /dev/null and b/packages/blog/public/knossos-v2.1.0/version-filters.jpg differ diff --git a/packages/blog/public/licensing-guide/thumbnail.webp b/packages/blog/public/licensing-guide/thumbnail.webp new file mode 100644 index 000000000..cec9981e7 Binary files /dev/null and b/packages/blog/public/licensing-guide/thumbnail.webp differ diff --git a/packages/blog/public/modpack-changes/thumbnail.webp b/packages/blog/public/modpack-changes/thumbnail.webp new file mode 100644 index 000000000..110af1f00 Binary files /dev/null and b/packages/blog/public/modpack-changes/thumbnail.webp differ diff --git a/packages/blog/public/modpacks-alpha/thumbnail.webp b/packages/blog/public/modpacks-alpha/thumbnail.webp new file mode 100644 index 000000000..1e7826ca6 Binary files /dev/null and b/packages/blog/public/modpacks-alpha/thumbnail.webp differ diff --git a/packages/blog/public/modrinth-app-beta/app.jpg b/packages/blog/public/modrinth-app-beta/app.jpg new file mode 100644 index 000000000..d32e6c1de Binary files /dev/null and b/packages/blog/public/modrinth-app-beta/app.jpg differ diff --git a/packages/blog/public/modrinth-app-beta/auth.jpg b/packages/blog/public/modrinth-app-beta/auth.jpg new file mode 100644 index 000000000..d3674e521 Binary files /dev/null and b/packages/blog/public/modrinth-app-beta/auth.jpg differ diff --git a/packages/blog/public/modrinth-beta/new-design.jpg b/packages/blog/public/modrinth-beta/new-design.jpg new file mode 100644 index 000000000..98d8d6093 Binary files /dev/null and b/packages/blog/public/modrinth-beta/new-design.jpg differ diff --git a/packages/blog/public/modrinth-beta/thumbnail.webp b/packages/blog/public/modrinth-beta/thumbnail.webp new file mode 100644 index 000000000..566f979ff Binary files /dev/null and b/packages/blog/public/modrinth-beta/thumbnail.webp differ diff --git a/packages/blog/public/modrinth-servers-beta/panel.jpg b/packages/blog/public/modrinth-servers-beta/panel.jpg new file mode 100644 index 000000000..4a2c3a583 Binary files /dev/null and b/packages/blog/public/modrinth-servers-beta/panel.jpg differ diff --git a/packages/blog/public/modrinth-servers-beta/thumbnail.webp b/packages/blog/public/modrinth-servers-beta/thumbnail.webp new file mode 100644 index 000000000..340baa69e Binary files /dev/null and b/packages/blog/public/modrinth-servers-beta/thumbnail.webp differ diff --git a/packages/blog/public/new-site-beta/thumbnail.webp b/packages/blog/public/new-site-beta/thumbnail.webp new file mode 100644 index 000000000..75a547070 Binary files /dev/null and b/packages/blog/public/new-site-beta/thumbnail.webp differ diff --git a/packages/blog/public/plugins-resource-packs/thumbnail.webp b/packages/blog/public/plugins-resource-packs/thumbnail.webp new file mode 100644 index 000000000..89f039335 Binary files /dev/null and b/packages/blog/public/plugins-resource-packs/thumbnail.webp differ diff --git a/packages/blog/public/redesign/adorn.jpg b/packages/blog/public/redesign/adorn.jpg new file mode 100644 index 000000000..cb516746a Binary files /dev/null and b/packages/blog/public/redesign/adorn.jpg differ diff --git a/packages/blog/public/redesign/consistency.jpg b/packages/blog/public/redesign/consistency.jpg new file mode 100644 index 000000000..5e5d29f5b Binary files /dev/null and b/packages/blog/public/redesign/consistency.jpg differ diff --git a/packages/blog/public/redesign/iris.jpg b/packages/blog/public/redesign/iris.jpg new file mode 100644 index 000000000..5d5f2c522 Binary files /dev/null and b/packages/blog/public/redesign/iris.jpg differ diff --git a/packages/blog/public/redesign/jellysquid.jpg b/packages/blog/public/redesign/jellysquid.jpg new file mode 100644 index 000000000..7cf593b62 Binary files /dev/null and b/packages/blog/public/redesign/jellysquid.jpg differ diff --git a/packages/blog/public/redesign/notifications.jpg b/packages/blog/public/redesign/notifications.jpg new file mode 100644 index 000000000..12d71a50a Binary files /dev/null and b/packages/blog/public/redesign/notifications.jpg differ diff --git a/packages/blog/public/redesign/profile-settings.jpg b/packages/blog/public/redesign/profile-settings.jpg new file mode 100644 index 000000000..a0e7f3e20 Binary files /dev/null and b/packages/blog/public/redesign/profile-settings.jpg differ diff --git a/packages/blog/public/redesign/thumbnail.webp b/packages/blog/public/redesign/thumbnail.webp new file mode 100644 index 000000000..56125a1a4 Binary files /dev/null and b/packages/blog/public/redesign/thumbnail.webp differ diff --git a/packages/blog/public/redesign/version-creation.jpg b/packages/blog/public/redesign/version-creation.jpg new file mode 100644 index 000000000..c45109ccd Binary files /dev/null and b/packages/blog/public/redesign/version-creation.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/bulk-edit.jpg b/packages/blog/public/two-years-of-modrinth/bulk-edit.jpg new file mode 100644 index 000000000..5443d90da Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/bulk-edit.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/gallery-ui.jpg b/packages/blog/public/two-years-of-modrinth/gallery-ui.jpg new file mode 100644 index 000000000..f2bb2493d Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/gallery-ui.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/landing-page.jpg b/packages/blog/public/two-years-of-modrinth/landing-page.jpg new file mode 100644 index 000000000..0dfca6b26 Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/landing-page.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/project-settings.jpg b/packages/blog/public/two-years-of-modrinth/project-settings.jpg new file mode 100644 index 000000000..af3dca3c6 Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/project-settings.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/project-webhook.jpg b/packages/blog/public/two-years-of-modrinth/project-webhook.jpg new file mode 100644 index 000000000..184b93aba Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/project-webhook.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/projects-dashboard.jpg b/packages/blog/public/two-years-of-modrinth/projects-dashboard.jpg new file mode 100644 index 000000000..11981054b Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/projects-dashboard.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/publishing-checklist.jpg b/packages/blog/public/two-years-of-modrinth/publishing-checklist.jpg new file mode 100644 index 000000000..d8de372fc Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/publishing-checklist.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/search-gallery-view.jpg b/packages/blog/public/two-years-of-modrinth/search-gallery-view.jpg new file mode 100644 index 000000000..fe218292d Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/search-gallery-view.jpg differ diff --git a/packages/blog/public/two-years-of-modrinth/thumbnail.webp b/packages/blog/public/two-years-of-modrinth/thumbnail.webp new file mode 100644 index 000000000..af2b32cd1 Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/thumbnail.webp differ diff --git a/packages/blog/public/two-years-of-modrinth/version-page.jpg b/packages/blog/public/two-years-of-modrinth/version-page.jpg new file mode 100644 index 000000000..77841c8a7 Binary files /dev/null and b/packages/blog/public/two-years-of-modrinth/version-page.jpg differ diff --git a/packages/blog/public/windows-borderless-malware-disclosure/thumbnail.webp b/packages/blog/public/windows-borderless-malware-disclosure/thumbnail.webp new file mode 100644 index 000000000..692e56589 Binary files /dev/null and b/packages/blog/public/windows-borderless-malware-disclosure/thumbnail.webp differ diff --git a/packages/blog/tsconfig.json b/packages/blog/tsconfig.json new file mode 100644 index 000000000..92e7710b9 --- /dev/null +++ b/packages/blog/tsconfig.json @@ -0,0 +1,9 @@ +{ + "extends": "tsconfig/base.json", + "include": [".", ".eslintrc.js"], + "exclude": ["dist", "build", "node_modules"], + "compilerOptions": { + "lib": ["esnext", "dom"], + "noImplicitAny": false + } +} diff --git a/packages/blog/utils.ts b/packages/blog/utils.ts new file mode 100644 index 000000000..06d1d587b --- /dev/null +++ b/packages/blog/utils.ts @@ -0,0 +1,40 @@ +import { execSync } from 'child_process' +import * as path from 'path' + +let REPO_ROOT_CACHE: string | null = null +export function getRepoRoot(): string { + if (REPO_ROOT_CACHE) return REPO_ROOT_CACHE + return (REPO_ROOT_CACHE = execSync('git rev-parse --show-toplevel').toString().trim()) +} + +export function repoPath(...segments: string[]): string { + return path.join(getRepoRoot(), ...segments) +} + +export async function copyDir( + src: string, + dest: string, + logFn: (src: string, dest: string) => void = () => {}, +): Promise