v1.5.6-beta

Fixes to upgrades from the Compositor, to the first publish of an imported site, and to the site menu.

Fixes

• Your own files deleted in an upgrade — When you upgraded Telar from the Compositor, files you had added inside folders that also contain Telar's files were deleted, such as your images in assets/images/ or a theme in _data/themes/. Now only files that were part of your site's previous Telar release are deleted. If that release can't be identified, nothing is deleted.
• The first publish of an imported site — In its commit message, every story, object, page and glossary term appeared as added, although they were already in your repository. Now only what you changed in the Compositor since the import appears there. For sites imported before this release, everything still appears as added in the first publish's commit message.
• Home in the site menu — With Home shown in the navigation bar on Home and Pages, it was still left out of the published menu. The menu is now published as you see it in the Compositor. On a site published before this release, the menu appears once as a change on the Publish page, so you can publish the Home item.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Correcciones a la actualización de Telar desde el Compositor, a la primera publicación de un sitio importado y al menú del sitio.

Correcciones

• Archivos tuyos que se borraban al actualizar — Al actualizar Telar desde el Compositor, se borraban archivos que habías agregado en carpetas donde también hay archivos de Telar, por ejemplo, tus imágenes en assets/images/ o un tema en _data/themes/. Ahora solo se borran los archivos que formaban parte de la versión de Telar que tu sitio tenía antes de actualizar. Si no se puede saber cuál era esa versión, no se borra nada.
• La primera publicación de un sitio importado — En el mensaje de commit, todas las historias, objetos, páginas y términos del glosario aparecían como agregados, aunque ya estaban en tu repositorio. Ahora solo aparece lo que cambiaste en el Compositor después de importar el sitio. En los sitios importados antes de esta versión, todo aparece todavía como agregado en el mensaje de la primera publicación.
• Inicio en el menú del sitio — Aunque Inicio estuviera visible en la barra de navegación del Compositor, no aparecía en el menú publicado. Ahora el menú se publica tal como lo ves en el Compositor. En los sitios publicados antes de esta versión, el menú aparecerá una sola vez entre los cambios de la página Publicar; cuando lo publiques, Inicio quedará en el menú del sitio.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.5.5-beta

A redesigned check against GitHub, fields that show they can be edited and protect what they change, and messages that say what actually happened.

Changes made on GitHub

• One review for changes made on GitHub — When someone edits your site directly on GitHub, the status at the top of the page says so, and one review lists each change with its own choice: keep GitHub's version or the Compositor's. A change made only on GitHub starts on GitHub's version; a change made in both places waits for you to choose. The review opens over the page you are on, from the status, the Publish page or the Upgrade Telar page.
• Three states instead of one — "Changes on GitHub" appears only when a commit since your last publish changes something the Compositor keeps. A site not yet published from the Compositor says so, and a check that could not be made, for example while GitHub is limiting requests, says that instead of claiming changes.
• Everything in one place — Files the Compositor could not read, images added on GitHub with no object, and stories or terms deleted on GitHub all appear in the same review as items to decide. The Objects page no longer has a sync of its own.
• Collaborators and instructors see the state and who chooses, without controls they cannot use.
• An imported site's first publish reviews the edits made on GitHub since the import instead of overwriting them.
• An About page in two languages — When a site holds both about.md and acerca.md, the Publish page asks which one to keep.

Editing

• Fields that look editable — Page titles, glossary term titles, and the title, subtitle and byline on a story's title card show that they can be edited before you hover over them.
• IDs and addresses that ask first — Story and term IDs, page addresses, and the Site URL and Base URL are locked until you choose Change. Typing is limited to the characters the site can use, the consequence is stated, and nothing changes until you confirm. A page address the site already uses for something else is refused.
• Story settings open in a panel beside the stage.
• A new object's ID is shown before you upload, and the ID you see is the one it keeps.
• Your About page — While your site's About page still has the text every new Telar site starts with, the Publish page suggests making it your own, with a link that opens the page in the editor. It does not stop you publishing, and it goes away once you change the text.

Fixes

• Sites whose project sheet has no story_id column — Importing such a site dropped its stories, and its first publish then took them off the live site. Stories are now read by their order number, as Telar reads them.
• Stories marked Draft — When a publish would take stories off your live site, the Publish page now names them.
• The glossary definition of "telar" — Telar shipped the definition of the term telar in English and Spanish, one after the other. When you upgrade Telar from the Compositor and that definition is unchanged, only the paragraph in your site's language is kept, on GitHub and in the Compositor. If someone edits it while the upgrade is running, their version is kept.
• Checks that missed your latest edits — Choosing Check again on the Publish page now takes in what you last wrote in the editor. If that could not be saved first, the page says so.
• Messages that claimed what had not been checked — The Publish page lists only the checks it ran; the Upgrade Telar page says what an upgrade can change and how its build ended, and no longer tells a site already on the latest release that it was just upgraded; onboarding no longer finishes when it could not check your settings; and the object delete dialog says what each choice does.
• Sites never published from the Compositor — The unpublished-changes window, opened from the status at the top of the page, now says the site hasn't been published from the Compositor yet, instead of showing a dash where the date would be.
• Checking an object's IIIF manifest — On the Objects page, the line under a newly added IIIF object says whether its manifest loaded. If it couldn't be loaded, or what loaded isn't a manifest, it tells you to open the object and check its Source URL.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Una nueva revisión de los cambios hechos en GitHub, campos que se ven editables y que piden confirmación antes de un cambio con consecuencias, y mensajes que dicen lo que de verdad pasó.

Cambios hechos en GitHub

• Una sola revisión para los cambios hechos en GitHub — Cuando alguien edita tu sitio directamente en GitHub, el indicador de estado de la parte superior de la página lo avisa, y en una sola revisión ves cada cambio y eliges, para cada uno, si usar la versión de GitHub o conservar la del Compositor. Si un cambio se hizo solo en GitHub, ya viene elegida la versión de GitHub; si se hizo en los dos lados, la revisión espera a que elijas. Puedes abrirla desde el indicador de estado, desde Publicar o desde Actualizar Telar, y se abre encima de la página en la que estás.
• Tres estados en lugar de uno — "Cambios en GitHub" solo aparece cuando un commit posterior a tu última publicación cambia algo que el Compositor gestiona. Si el sitio todavía no se ha publicado desde el Compositor, el indicador lo dice. Si no se pudo revisar GitHub, por ejemplo porque GitHub recibió demasiadas solicitudes en poco tiempo, el indicador lo dice en lugar de anunciar cambios.
• Todo en un mismo lugar — Los archivos que el Compositor no pudo leer, las imágenes que se agregaron en GitHub sin un objeto asociado y las historias o términos del glosario que se eliminaron en GitHub aparecen en la misma revisión, para que decidas qué hacer con cada uno. La página Objetos ya no tiene una sincronización aparte.
• Colaboradores/as y docentes ven qué cambió en GitHub y quién va a decidir, sin botones que no pueden usar.
• La primera publicación de un sitio importado revisa los cambios hechos en GitHub después de la importación, en lugar de sobrescribirlos.
• Una página Acerca de en dos idiomas — Si un sitio tiene about.md y acerca.md, la página Publicar pregunta cuál conservar.

Edición

• Campos que se ven editables — Los títulos de las páginas, los títulos de los términos del glosario, y el título, el subtítulo y la firma de la Portada de una historia se ven editables sin necesidad de pasar el cursor por encima.
• Cambiar un ID o una dirección pide confirmación — Los ID de historias y términos, las direcciones de las páginas, la URL del sitio y la URL base quedan bloqueados hasta que haces clic en Cambiar. Solo se pueden escribir los caracteres que el sitio puede usar, el Compositor te explica qué va a pasar y nada cambia hasta que confirmas. Tampoco se acepta una dirección de página que el sitio ya use para otra cosa.
• Configuración de la historia se abre ahora en un panel al lado de la vista previa.
• El ID de un objeto nuevo aparece antes de subirlo, y es el mismo que queda guardado.
• Tu página Acerca de — Mientras tu página Acerca de conserve el texto con el que empiezan todos los sitios nuevos de Telar, la página Publicar te sugiere reescribirla y te da un enlace para abrirla en el editor. La sugerencia no impide publicar y desaparece en cuanto cambias el texto.

Correcciones

• Sitios cuya hoja de proyecto no tiene la columna story_id — Al importar un sitio así se perdían sus historias, y la primera publicación las quitaba del sitio publicado. Ahora el Compositor identifica las historias por su número de orden, como hace Telar.
• Historias marcadas como borrador — Si al publicar van a desaparecer historias del sitio publicado, la página Publicar ahora dice cuáles.
• La definición de «telar» en el glosario — Telar traía la definición del término telar en dos párrafos, uno en inglés y otro en español. Al actualizar Telar desde el Compositor, si nadie ha cambiado esa definición, queda solo el párrafo en el idioma de tu sitio, tanto en GitHub como en el Compositor. Si alguien la edita durante la actualización, se conserva la versión editada.
• Verificaciones que no tenían en cuenta tus últimos cambios — Al hacer clic en Verificar de nuevo, en la página Publicar, las verificaciones ahora tienen en cuenta lo último que escribiste en el editor. Si eso no se pudo guardar antes de verificar, la página lo dice.
• Mensajes que afirmaban lo que no se había revisado — La página Publicar muestra solo las comprobaciones que de verdad hizo. Actualizar Telar dice qué puede cambiar una actualización y cómo terminó la construcción del sitio, y si el sitio ya tenía la versión más reciente, ya no dice que se acaba de actualizar. La configuración inicial ya no se da por terminada si no pudo comprobar los ajustes del sitio. Y el diálogo para eliminar un objeto explica qué hace cada opción.
• Sitios que nunca se han publicado desde el Compositor — La ventana de cambios sin publicar, que se abre desde el indicador de estado de la parte superior de la página, ahora dice que el sitio todavía no se ha publicado desde el Compositor, en lugar de mostrar una raya donde iría la fecha.
• Comprobar el manifiesto IIIF de un objeto — En la página Objetos, la línea bajo un objeto IIIF recién agregado dice si se cargó el mani...

v1.5.4-beta

Faster page loads, and two fixes to upgrading Telar on a site.

Fixes

• Pages load faster with several sites — Every page read the full content of each of your sites from the database, though none of it was shown. Pages now read only what they display, which matters most for people with several sites or large ones.
• An upgrade that stops with an error — If preparing an upgrade stopped with an unexpected error, publishing, uploading objects and upgrading stayed blocked on the site for up to five minutes. They are now available again at once.
• A site with no recorded Telar version — The upgrade page treated a site whose Telar version the Compositor had no record of as up to date. It now reads the version from the site's files and offers the upgrade when one is due.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Páginas más rápidas y dos correcciones al actualizar Telar en un sitio.

Correcciones

• Páginas más rápidas cuando tienes varios sitios — Cada página cargaba desde la base de datos todo el contenido de todos tus sitios, aunque no mostraba nada de eso. Ahora cada página carga solo lo que muestra, y la diferencia se nota sobre todo si tienes varios sitios o sitios grandes.
• Una actualización que se detiene por un error — Si al preparar una actualización ocurría un error inesperado, podías quedar hasta cinco minutos sin poder publicar el sitio, subir objetos ni actualizar Telar. Ahora todo vuelve a estar disponible de inmediato.
• Un sitio sin versión de Telar registrada — Si el Compositor no tenía registrada la versión de Telar de un sitio, la página de actualización lo trataba como si estuviera al día. Ahora lee la versión en los archivos del sitio y ofrece la actualización cuando corresponde.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.5.3-beta

Fixes to upgrading Telar on a site, and to opening Start after importing one.

Fixes

• Upgrading goes straight through — Once an upgrade is prepared, the Compositor sends it to GitHub at once, instead of stopping at a confirmation screen that could appear empty. If the connection is lost while the upgrade is being prepared or sent, the page says whether your site was changed and what to do, where before it could fail with an error.
• When the build after an upgrade fails — The page now says that your site's files are on the new Telar version and which step of the build stopped, and that running the build again doesn't repeat the upgrade. If GitHub Pages is turned off for the repository, the page says so and offers a button that turns it on and runs the build again.
• Telar's development files on their own card — Sites made from the template carry Telar's automated tests and copies of its upgrade tools. An upgrade that removes them now lists them on a separate card that explains what they are, instead of among the files to remove. JavaScript files are counted as site scripts rather than stylesheets.
• Trying an upgrade again right away — Leaving the upgrade page while an upgrade was being prepared blocked a new attempt for up to five minutes, with a message that blamed another operation. A new attempt now replaces your own unfinished one. If your earlier upgrade is still being saved to GitHub, the page says so and when to try again.
• A site reverted on GitHub — When a site's files are put back to an earlier Telar version on GitHub, the Compositor now records that version and the upgrade page offers the latest one, instead of treating the site as up to date.
• Start after importing a site — Start could take up to 16 seconds to open after importing a site, because the page was loading data it never shows. It now opens promptly, and the button that leads to it after an import shows that it's working.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Correcciones al actualizar Telar en un sitio y al abrir Inicio después de importar uno.

Correcciones

• La actualización va directo a GitHub — Cuando la actualización queda preparada, el Compositor la envía a GitHub de inmediato. Antes se detenía en una pantalla de confirmación que podía aparecer vacía. Si se pierde la conexión mientras se prepara o se envía la actualización, la página dice si tu sitio cambió y qué hacer. Antes podía terminar en un error.
• Cuando falla la construcción después de actualizar — La página ahora dice que los archivos de tu sitio ya quedaron en la nueva versión de Telar, en qué paso se detuvo la construcción y que volver a construir el sitio no repite la actualización. Si GitHub Pages está desactivado en el repositorio, la página lo dice y ofrece un botón que lo activa y vuelve a construir el sitio.
• Los archivos de desarrollo de Telar, en su propia tarjeta — Los sitios creados a partir de la plantilla traen las pruebas automáticas de Telar y copias de sus herramientas de actualización. Cuando una actualización los elimina, ahora aparecen en una tarjeta propia, "Archivos de desarrollo de Telar", que explica qué son, y ya no en la lista "Archivos a eliminar". Además, los archivos JavaScript ahora aparecen en "Scripts del sitio" y no en "Hojas de estilo".
• Volver a actualizar enseguida — Si salías de la página de actualización mientras se preparaba, podías quedar hasta cinco minutos sin poder intentarlo de nuevo, y el mensaje lo atribuía a otra tarea en curso en el sitio. Ahora un nuevo intento reemplaza el que dejaste sin terminar. Si tu actualización anterior todavía se está guardando en GitHub, la página lo dice y te indica cuándo volver a intentarlo.
• Un sitio devuelto en GitHub a una versión anterior — Si en GitHub alguien devuelve los archivos de un sitio a una versión anterior de Telar, el Compositor ahora registra esa versión y la página de actualización ofrece la más reciente. Antes trataba el sitio como si estuviera al día.
• Inicio después de importar un sitio — Inicio podía tardar hasta 16 segundos en abrirse después de importar un sitio, porque la página cargaba datos que nunca muestra. Ahora se abre enseguida, y el botón "Ir a Inicio", al final de la importación, indica que la página está cargando.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.5.2-beta

Fixes on Start, after setting up a site, and in the story editor.

Fixes

• A new site opens on Start — After creating or importing a site, the setup's last screen now leads to Start, which walks a new site through its first steps, instead of Site settings. A site that needs an upgrade first also leads to Start once the upgrade is done, and someone whose sites are all set up and who opens the setup again is taken to Start rather than Objects.
• Work together on Start — A site's convenor now finds a Work together card on Start with a large button for inviting collaborators, in place of the small button at the top of the page. On a shared site, a second card links to the contribution record, where everyone on the project can see what each person has added and written.
• Guides in the story editor — The labels that explained the frame, the text limit and the area a visitor sees are now small tags on the step's image, each opening a short explanation when pressed. The Show guides button hides them along with the frame. The frame's explanation opens by itself the first time someone opens the editor, and on a phone an explanation with no room beside its tag opens under the top bar.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Correcciones en Inicio, al terminar de crear o importar un sitio y en el editor de historias.

Correcciones

• El asistente termina en Inicio — Al crear o importar un sitio, el botón de la última pantalla del asistente ahora lleva a Inicio, la página que guía los primeros pasos de un sitio nuevo. Antes llevaba a Configuración del sitio. Si el sitio usa una versión anterior de Telar, el asistente pide primero actualizar Telar, y al terminar la actualización el botón también lleva a Inicio. Y quien vuelve a abrir el asistente cuando ya tiene todos sus sitios configurados llega ahora a Inicio, y no a Objetos.
• Trabajar en equipo desde Inicio — Quien coordina un sitio encuentra ahora en Inicio una tarjeta "Trabajar en equipo" con un botón grande para invitar colaboradores. La tarjeta reemplaza el botón pequeño que había en el recuadro de bienvenida, en la parte de arriba de la página. En un sitio compartido, una segunda tarjeta lleva al registro de participación, donde todo el equipo puede ver lo que cada persona ha agregado y escrito.
• Guías en el editor de historias — Las frases que explicaban el marco, el límite del texto y la zona que ve quien visita el sitio ahora son pequeñas etiquetas sobre la imagen del paso, y al hacer clic en cualquiera de ellas se abre una explicación breve. Al desactivar el botón Mostrar guías se ocultan las etiquetas y el marco. La explicación del marco se abre sola la primera vez que alguien entra al editor. En el celular, si una explicación no cabe junto a su etiqueta, aparece debajo de la barra superior.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.5.1-beta

Fixes on the glossary page.

Fixes

• Glossary kinds in the interface language — On a site whose language differs from the interface's, the glossary page named the standard kinds by the site's labels, so an English interface on a Spanish site listed "Palabra clave" among English controls. The kind picker, the term list and the "Kinds of glossary term" window now name the standard kinds in the interface language, and the preview still shows the label the site's visitors see. A site's own kinds keep the label its configuration gives them.
• New term button — The button showed the + sign twice.
• Term filter — With one term in the glossary, the filter now reads "Filter 1 term…".
• Editor and preview side by side — The term editor and the reader preview now share the page evenly, and the preview fills its half, so a definition with headings, lists or images can be read in full as the site will show it.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Correcciones en la página del glosario.

Correcciones

• Tipos de término en el idioma de la interfaz — Cuando el idioma del sitio no coincidía con el de la interfaz, la página del glosario mostraba los tipos estándar con la etiqueta en el idioma del sitio: en un sitio en inglés con la interfaz en español aparecía "Key term" en medio de controles en español. Ahora el selector de tipo, la lista de términos y la ventana "Tipos de término del glosario" nombran los tipos estándar en el idioma de la interfaz, y la vista previa sigue mostrando la etiqueta que ven quienes visitan el sitio. Los tipos propios del sitio se siguen mostrando con la etiqueta que tienen en la configuración.
• Botón Nuevo término — El botón mostraba el signo + dos veces.
• Filtro de términos — Cuando el glosario tiene un solo término, el filtro ahora dice "Filtrar 1 término…".
• Editor y vista previa lado a lado — En la página del glosario, el editor del término y la vista previa ahora ocupan cada uno la mitad de la página. Antes la vista previa era una columna estrecha y de altura limitada; ahora llena toda su mitad, así que una definición con títulos, listas o imágenes se puede leer completa, tal como se verá en el sitio.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.5.0-beta

The teaching release: course projects with join codes and shared object collections, a per-contributor record of group work, and publishing opened to every member of a group. The story editor is rebuilt around a stage that shows each step as a visitor will see it. Edits made on GitHub are now read back before a publish instead of being overwritten, and a large set of fixes stops authored content from being lost between the Compositor and the published site.

New features

• Course projects — A convenor can mark a project as a course and share its objects with every group site that joins it. Students join with a reusable join code, either while creating a site or later from Site settings; course objects are tagged in each site's objects list and cannot be deleted there. The Course tab lists the sites in the course and manages its join codes. Please contact us if you are an instructor and would like to try this feature.

• Instructors and staff codes — Courses have an Instructor role, shown with its own badge and left out of member counts. A convenor can issue a staff code, which a co-instructor or teaching assistant redeems under "Join a course as staff" on the account page; they are then added to every group site in the course, including sites that join later. Removing a staff member from the course removes them from every group site at once. When a site leaves the course, the course's staff are removed from that site's team.

• Every member can publish, upload and upgrade — Publishing, uploading objects and upgrading the site are no longer limited to the convenor: collaborators and instructors can do all three. Commits are made by the Compositor's GitHub App, with the publisher named in the commit message. Thanks UCSB INT 138LA students for your feedback!

• Repository access held by GitHub — The Compositor now adds each new member as a collaborator on the site's GitHub repository. GitHub requires the person to accept an invitation; it appears in the site-status pill and when they open the project, and they can accept it there without going to GitHub. The "Repository access" page shows convenors each member's state (access, invitation pending, invitation lapsed, none) and lets them reissue an invitation or withdraw access. Removing a member withdraws the access the Compositor gave. Members who joined before this release are not added automatically.

• Contribution record — Each project has a record of who made and wrote what: items added, items written in, words written, and time spent in the Compositor, with the idle threshold stated beside it. Cataloguing objects counts as its own row. Every measure says what it does not capture, nothing is ranked or totalled, and everyone with access to the project can see it, in its own view and in the collaboration sidebar. It can be downloaded as a CSV, one row per person with a column for each measure; anyone with access to the project can download it. Authorship for content written before this release is recovered where the collaborative document still holds it and shown as unknown where it does not.

• The story editor shows the step as published — The image viewer now fills the editor, and the step card, layer panels and controls sit over it as they do on the site from Telar 1.8.0: beside, below or over the object depending on the window, with video and audio steps laid out as the site lays them out. Title and section cards appear on the stage, a dashed line marks where the published card cuts the text, and the question, answer and layer-button label are edited in place, with pencil buttons beside each. Steps can be reordered from the keyboard. Capture now measures framing against the image and the region beside the card, so a captured view replays where the author left it; the capture viewer can no longer be rotated or mirrored, since a step records neither, and a click on the image no longer zooms.

• Layer panels preview as the site renders them — Accordions, tabs, carousels, bibliographies, footnotes and KaTeX maths preview as the site will publish them, and the step answer renders through the same rules. Glossary callouts can be inserted from the Widget menu and preview as the site places them.

• Footnote button — The layer panel toolbar has a Footnote button. It inserts the reference at the cursor and the note where the site will read it, and says so when the cursor is somewhere a note cannot go.

• Answer length measured in lines — An answer may have up to 18 lines and five paragraphs, counting 53 characters to a line and two lines for each paragraph break. The editor shows the count as you write, answers over 15 lines publish in slightly smaller type, and a publish is blocked for an answer the site would cut, with a pointer to the layer panels for the detail.

• Change a story's or an object's ID — "Change ID" renames a story (its files, its row in the project sheet and its steps together) or an object (its files and every step that uses it). The editor still opens a story from an address that uses an earlier ID.

• Custom object fields — Custom columns in objects.csv are shown and edited on the object page, in the sheet's column order. Two people editing different custom fields of the same object no longer lose one of the edits. A publish blocked by a column the framework refuses offers to remove that column from the story, from every object or from every glossary term.

• Glossary kinds — Each glossary entry has a kind, chosen from the standard kinds and the site's own, beside the entry title and as a column in the entry list; the preview shows the kind above the title. "Edit kinds" on the Glossary page adds and removes the site's own kinds, published to _config.yml.

• More object formats — Audio files (MP3, OGG, M4A), PDF and WEBP can be uploaded. The upload dialog says "file" for what is picked from your disk and lists the accepted formats, and shows a placeholder rather than a preview for formats a browser cannot display.

• Page chooser for multi-page objects — Picking a multi-page object for a step opens a chooser with page thumbnails and a page-number box, and a Change button in the bar reopens it. A new step starts from the previous one.

• Imports from any default branch — Importing a repository whose default branch is not main now offers to rename it, or to make an existing main the default, instead of sending you to GitHub. An import the GitHub App cannot reach returns you to the connect step with your choices kept.

• Colliding columns resolved in the Compositor — When two columns Telar reads as one each hold values, the upgrade, sync, first import and story restore let you choose which to keep, and commit the choice so the site's next build passes. Sheets named in Spanish (proyecto, objetos, glosario) are read as the site reads them.

• Build workflow repair — The publish warning about an out-of-date build workflow now has an "Update the build workflow" button.

• Restoring a project whose saving has stopped — If the Compositor stops saving a project's changes, the site-status pill says so and why, and the convenor can restore it from the last save.

• Bug reports carry the site — The bug reporter records the repository, the site's Telar version, recent commits made outside the Compositor and the last failed publish, and asks what changed recently. Server error messages are never attached, since the issue is public.

Fixes

• Edits made on GitHub are read, not overwritten — The sync and publish checks now read step CSVs, layer files and page files, not only the sheets. A story or page changed on GitHub is listed with a choice of version, and a publish no longer replaces a file the Compositor has not read. Object order in objects.csv, and object rows changed on GitHub, are carried in the same way.

• Files keep their own layout — Publishing keeps each CSV's column order, header spelling, comment and instruction rows, and custom columns, including empty ones and custom columns in project.csv. A page keeps its whole front matter, with only the title edited. An imported story keeps the order of its steps and layers.

• A failed read is never taken for a missing file — The import, sync, restore and publish now refuse with the file named when GitHub cannot be read, instead of treating the file as absent and offering every row as removed. Files over 1 MB can be read, and a file that is not valid UTF-8 is named with how to repair it.

• Objects work finishes on the server — Uploaded objects are registered as soon as their commit lands, not when the uploader's tab sees the build finish, and a publish finishes any objects work still owed before reading. An object counts as ready only once its tiles exist on the deployed site. Deleted objects no longer return, and deleting an object removes every row carrying its ID and its files.

• One language per site — A site is in one language, so the Compositor keeps one file per page. A new site starts without the template's other-language page files, and an imported site's other-language page files are dropped on import and deleted from GitHub the next time you publish.

• Upgrades — An upgrade delivers the site's menu only where it has none, adds framework-owned page settings without touching the author's, stamps the release date the framework declares, and is checked against the latest release before it commits. The post-upgrade screen lists only the steps that apply to you, and the upgrade page names the site it acts on. The upgrade page lists every file the upgrade deletes, and an upgrade that would delete one it did not list stops before changing anything. The steps after an upgrade are shown in the interface language.

• Characters that break a build — Characters a Telar build rejects, such as those carried in text pasted from a PDF, are removed on paste and before every co...

v1.4.5-beta

A security patch: one onboarding action did not check project ownership.

Fixes

• Project unlinking now requires ownership — The onboarding flow's unlink action, used to discard a partially created site and start over, checked only that the named project existed — not that it belonged to the signed-in user. Any signed-in user who knew or guessed a project's internal id could delete that project. The action now requires the caller to be the project's convenor, refuses everyone else, and the refusal does not reveal whether a project exists.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Un parche de seguridad: una acción del asistente de creación no verificaba la propiedad del proyecto.

Correcciones

• Desvincular un proyecto ahora exige ser su coordinador/a — La acción de desvincular, que sirve para descartar un sitio a medio crear y empezar de nuevo, solo comprobaba que el proyecto existiera, no que perteneciera a la persona que hacía la solicitud. Cualquier persona con la sesión iniciada que conociera el identificador interno de un proyecto podía borrarlo. Ahora la acción exige que quien la ejecuta sea coordinador/a del proyecto, la niega a las demás personas, y la respuesta no revela si el proyecto existe o no.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

Telar Compositor v1.4.4-beta

A patch release: an upgrade interrupted partway through could not be retried.

Fixed

• An interrupted upgrade can now be retried. An upgrade is written in two commits — your site's content first, then its workflow files and version number. When a passing GitHub error stopped the second from landing, the site was left stranded between two versions, and every retry failed the same way: it repeated instructions to remove files the earlier attempt had already removed, which GitHub does not allow. Retrying now skips removals that have already taken effect, so an interrupted upgrade finishes on the next try.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Novedades

Una versión de mantenimiento: una actualización interrumpida a medio camino no se podía reintentar.

Corregido

• Ahora puedes reintentar una actualización interrumpida. Una actualización se hace en dos commits: primero el contenido del sitio y luego sus archivos de flujo de trabajo y el número de versión. Cuando un error pasajero de GitHub impedía que el segundo llegara, el sitio quedaba a medio camino entre dos versiones y todos los reintentos fallaban igual: repetían la orden de eliminar archivos que el intento anterior ya había eliminado, algo que GitHub no permite. Ahora los reintentos omiten las eliminaciones que ya surtieron efecto y la actualización termina en el siguiente intento.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.

v1.4.3-beta

A patch release: a Google Sheets warning that wouldn't go away, and the KaTeX configuration file missing from framework upgrades.

Fixed

• The stale "Google Sheets is enabled" warning clears. On a site that had switched from Google Sheets to the compositor, the settings page could keep warning that Google Sheets was the content source even though it was already disabled and builds were using compositor content. The page now checks the repository configuration before warning and corrects its records — an affected site rights itself the next time you open its settings.
• Disabling Google Sheets can no longer be undone by a background save. Turning it off during a publish could be silently reverted by a background save from an open editing session — which is how the stale warning came about. The change now reaches the live collaborative document as well.
• Framework upgrades deliver the KaTeX configuration file. Upgrading a site to Telar v1.6.0 or later shipped the layouts and scripts that read the new _data/katex.yml, but not the file itself, leaving LaTeX formulas unrendered. It is now delivered with upgrades and restored at publish if missing. Note the file belongs to the framework: local edits to it are replaced on upgrade, as in the framework's own upgrade script.

Acknowledgments

Telar is developed by Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, and students and scholars at the UCSB Archives, Memory, and Preservation Lab, the UT Archives, Mapping, and Pedagogy Lab, and Neogranadina.

We gratefully acknowledge the support of the Caribbean Digital Scholarship Collective, the Center for Innovative Teaching, Research, and Learning (CITRAL) at the University of California, Santa Barbara, the UCSB Library, the Routes of Enslavement in the Americas University of California MRPI, and the Department of History of The University of Texas at Austin.

---

Novedades

Una versión de mantenimiento: un aviso de Google Sheets que no se quitaba y el archivo de configuración de KaTeX que faltaba en las actualizaciones.

Corregido

• El aviso obsoleto de que Google Sheets está activado desaparece. En un sitio que había pasado de Google Sheets al compositor, la pestaña Ajustes del sitio podía seguir avisando que Google Sheets era la fuente del contenido, aunque ya estaba desactivado y el sitio se construía con el contenido del compositor. Ahora la página consulta la configuración del repositorio antes de avisar y corrige sus registros: un sitio afectado se arregla solo la próxima vez que abras sus ajustes.
• Desactivar Google Sheets ya no se deshace con un guardado en segundo plano. Al desactivarlo durante una publicación, un guardado automático de una sesión de edición abierta podía revertirlo sin aviso; de ahí venía el aviso obsoleto. Ahora el cambio también queda en el documento colaborativo en vivo.
• Las actualizaciones ahora entregan el archivo de configuración de KaTeX. Al actualizar un sitio a Telar v1.6.0 o posterior llegaban las plantillas y los scripts que leen el nuevo _data/katex.yml, pero no el archivo, y las fórmulas en LaTeX dejaban de verse. El archivo ahora llega con la actualización y se restaura al publicar si falta. Ten en cuenta que el archivo pertenece a Telar: si lo editas, la actualización lo reemplaza, igual que lo hace el script de actualización de Telar.

Agradecimientos

Telar es desarrollado por Adelaida Ávila, Ana María Cárdenas Gasca, Juan Cobo Betancourt, Natalie Cobo, Santiago Muñoz, y estudiantes e investigadores del UCSB Archives, Memory, and Preservation Lab, el UT Archives, Mapping, and Pedagogy Lab, y Neogranadina.

Agradecemos el apoyo del Caribbean Digital Scholarship Collective, el Center for Innovative Teaching, Research, and Learning (CITRAL) de la University of California, Santa Barbara, la UCSB Library, el Routes of Enslavement in the Americas University of California MRPI, y el Departamento de Historia de la Universidad de Texas en Austin.