cross-language-cpp/cross-language-cpp.github.io

Djinni github pages published at djinni.xlcpp.dev

cross-language-cpp.github.io's Issues

Update link to mobilecpp.slack

The once-working Heroku app showing the self-registration URL is no more.

Therefore, we need to update the URL to a working one.
Preferably to the self-registration itself.

publish raw files of new djinni logo

As a maintainer I want to give easy access to the new logo as a resource that can be modified and used by anyone easily.
For that I want to publish the raw .afdesign file(s) and multiple variations of it as png & svg in the documentation.

minor stuff that needs improvement

Every time I visit the page I spot some small error.
This issue is a collection of these minor bugs that need to be fixed in the next update:

• Footer does not reach bottom. The lighter gray bar at the bottom should be removed.
  
• Link to intellij plugin docs in setup.md is broken
• Search index should not include landing page. When one searches "IDL", the first result is the marketing blabla from the landing page
• <kbd> tags are not readable in dark mode:
  

Don't auto update submodules to HEAD

Currently every night an action is executed, that pulls the latest HEAD of each submodule. In case of the djinni-generator this recently had the effect that documentation for a unreleased change was published.

As a user I'd like the website to always show the documentation of the latest released version of each component. I'd also like to see which version of the component is currently documented (maybe with a small badge on the top of the page, that shows the version of the component + a link to the release).
Optionally I'd like to be able to switch to the documentation of an older version of the component-documentation.

Add list of apps that use djinni

As a project maintainer I'd like to promote djinni as "not yet dead" and "more popular than you might think" in this repository, to attract new users & contributors. To do so, I'd like to add a section like "These companies rely on djinni" or "these apps rely on djinni" to the README.
This will help us as a community to have a higher chance to thrive in the long term.

TODO:

• collect an initial list of apps/developers using djinni that are willing to be promoted on our repo (doesn't matter if they already use our repo in the first place)
  • ask @a4z & @bojanin if their companies would be willing to be listed
  • I am planning to publish an app, but it's a toy project and will probably take a while to go public... :P
  • contact Dave Hagedorn if he'd like TextNow to be listed. (thanks to @a4z for sharing this podcast)
• decide if and how the collected information should be presented (list of companies vs list of explicit apps)
• prepare a first version of the listing

improve preview-ability of submodule changes

As a developer I want to be able to easily preview my changes. To make sure everything is fine, I want them to be as close as possible to what they will look like in production.

Currently all submodules do just have a minimal mkdocs configuration file & will render with the default mkdocs theme. This can lead to inaccuracies in the preview if I edit the documentations of just one submodule repository, without rendering the full documentation page. Certain features/plugins are not supported/enabled in the submodule mkdocs configurations.

To achieve a setup closer the the real configuration in each repository, the docs should be configured to render with the current theme from the main documentation repository by default (material for Mkdocs), and with the same plugins activated.