google / closure-templates

A client- and server-side templating system that helps you dynamically build reusable HTML and UI elements

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Documentations on developers.google.com return 404

jimbojetlag opened this issue · comments

I know Closure Template and Closure Library are not super popular outside of Google, but the way Google handles them I cannot fault the community.

All sidebar links under https://developers.google.com/closure/templates/ return 404, example:

https://developers.google.com/closure/templates/concepts/templates

2019 now - still not fixed..

Mentioning a few folks that have helped on the most recent issues. We use closure templates as a customer-facing customization language and refer them to this documentation site. Having the documentation broken for months makes our company look bad.

@iteriani @lukesandberg @mikesamuel

Google is a very different company to what it used to be.

fwiw, we're moving the documentation to Github so that it syncs with our pushes.

@iteriani Looks like the documentation site has disappeared again. Even if you want to maintain the source of truth in Github, perhaps you can leave up an Overview page on the main Google site? That is exactly what Closure Compiler does. Currently, the Closure Tools page makes it look like Templates are not a thing -- https://developers.google.com/closure/ has 4 blocks for Compiler, Stylesheets, Linter, and Library.

I appreciate that ya'll are trying to open Soy development up, but I really miss the previous state with bi-annual drops of code coming with updated documentation. I appreciated these properties of the previous situation that are no longer the case:

  • Explicit Releases with release notes, so we aren't picking commits at random and can see what changed without reviewing the commit log.
  • Related to the above, you guys are making backwards-incompatible changes like removing support for param declarations in soydoc. The effect is that updating to a newer commit requires a whole-codebase migration on my side. As a dependency that pervades my company's codebase, I value stability over new features. Honestly, I thought Soy was pretty much "finished" and was happy with it. Without visibility into the roadmap or what's being released, it feels like an update treadmill without the commensurate benefit.
  • Reliable and GREAT documentation. It was well written, comprehensive, attractive, easy to browse.

Anyway, hopefully someone takes this into account, although I suspect the train has left the station. In my opinion Closure Templates is the best templating technology around so I'd love to see it succeed in the open source community.

Thanks,
Rob

I'll fix the link on developers.google.com if that's the only issue.

My apologies for the abrupt changes to release. It's mostly due to inexperience as ownership of the Closure templates repository has been transferred to me recently and I am trying to figure out how to make the sync between google and github maintainable.

I can give an update on some of status relating to Soy.

On the client-side, we are attempting to gear up for an eventual migration to TypeScript emit (over several years), so we are trying to kill off features to make this easier. On that end, we may have to rethink certain things like proto support or soy plugins. In addition, we are trying to figure out how to deprecate one Javascript backend in favor of the other.

On the server-side, we are trying to add HTML validation features and hooks for logging. We are also trying to improve our server-side rendering technology, as it is not fast enough.

I think what sounds reasonable is some note into how we executed our migration guides and possibly releasing some of our migration tools.