@jschatz1 Yes! Would it be possible to have custom HTML elements like the one below? I can add them as images first and they can be translated later, too.
@cperessini For now, the simple solution seems to be just add images first only as needed. Lets only add custom HTML elements if they are truly needed. Other than that, is there anything else blocking for this issue? Thanks!
@awhildy Great, we'll use images then. This page is created with HAML and I'm not familiar with the way it works, so I'll ask for @annabeldunstone's help when she's back from vacation.
@cperessini Are you still working on this? Let me know if I can help any way. Not sure what the end goal is for this release but I see it was added to 8.14 cc @awhildy
Good catch @tauriedavis. @cperessini is gone on vacation, but I believe when he gets back, he was prioritizing some other issues that I think we should get done first. I'm going to move this to backlog for now.
Agreed, @tauriedavis! I really want to do that. I started with just markdown in the UX Guide as it was an easy way to get started, but the goal should be to combine them all together so we can have the interactive controls and the written guidance on usage/etc. side-by-side. One of the challenges may be that docs.gitlab.com is markdown, and it seems like we are moving more to just using docs.gitlab.com (https://gitlab.com/gitlab-org/gitlab-ce/issues/18739). However, with our own CSS framework (https://gitlab.com/gitlab-org/gitlab-ce/issues/24071) maybe it is easy to show our controls without the guide being a part of the core ruby app? I might not know what I'm talking about though