I would like the ability to rename existing web font projects. I would also like the ability to duplicate existing web font projects.

Being unable to rename an existing web font project introduces risk and (what I think is) unnecessary busy-work to my web-based projects.

My company publishes educational curricula to variety of platforms both printed and digital. All are produced as HTML templates which are proofed in a web browser and which rely upon Adobe web fonts for their typography.

It is quite common that we don’t know at the onset of a project how many versions and platforms of a given curriculum we might have, but we need to be able to clearly communicate the distinct purpose and version of a given web font project as that curriculum grows and evolves into different platforms or iterations.

For example, most recently we started a project for a curriculum intended for print publishing I’ll call My English Lessons. I created a web project called My English Lessons Fonts in Adobe Fonts and used the corresponding ID in the HTML templates for that curriculum. Because the final form of this project was intended for printing, not web hosting, there were a bunch of typographic needs specific to book publishing (like page numbers, title pages, running heads) that we supported in the My English Lessons Fonts web project. The project had 15 fonts, total. A few of the texts mentioned in the curriculum had Spanish characters, so we had to dial in the specific language support settings for each font in the project, too.

When we found out that we were going to be publishing My English Lessons online, we needed a new version of the fonts project, but without all the extra typography that would make a web site ungainly to load.

We needed to give this new version of the My English Lessons Fonts web project a name — like My English Lessons Website Fonts — that was specific to the web, so that the purpose of the web project was clear. To prevent any confusion as to the purpose of the original web project, we also needed to rename the original fonts project to My English Lessons Book Fonts.

To accomplish this with the current Adobe Fonts feature set, I had to create a new web project for My English Lessons Book Fonts and manually add all 15 fonts/weights/styles, each with their own font family settings, emulating My English Lessons Fonts. It’s very easy to miss a weight or style, so I had two browser windows with my Manage Fonts settings side by side, so that I can compare. The font lists don’t fit on a single screen even on a sizable monitor, so there is much scrolling and loss of context as the weights/styles get separated from the names of the font family.

I then have to replace the My English Lessons Fonts ID with the My English Lessons Book Fonts ID in my HTML templates. I try to keep the place where that is necessary to only one line of code, but that can’t always be the case for reasons.

For a period of time, I have to maintain both My English Lessons Fonts and My English Lessons Book Fonts in my Adobe Fonts projects as the HTML templates go through the code review, QA, and deployment process. Once the updated templates are live, I can delete the now obsolete My English Lessons Fonts project from Adobe Fonts.

Then I have to create a new web font project manually for My English Lessons Website Fonts making sure to manually add only the fonts/weights/styles that are necessary for content.

My brain explodes when I think I might need to do this all again exponentially because we introduce a version 2 and need to include a version number or year or something in the web project names.

With the ability to (at the very least) rename and (ideally) duplicate an existing web project, I wouldn’t have to know the future of a project at inception. I could have accomplished the evolution of a single generically named project to two variants of that project — and not had to do any code updates!!! — in less time than it’s taken me to write this darn feature request.

I hope you seriously consider this feature request! I’m not sure how practical it would be for us to continue using Adobe web fonts projects at scale, otherwise.