-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TopMenu hardcoded not CDN #2
Comments
Yup. It doesn’t use bootstrap so it can’t use the direct markup in the cdn. Code is here https://github.com/Hutchy68/Jforeground/blob/master/jForeground.skin.php#L105 can have a look when I’m back :) |
If we have the code in this repository, then I could create a PR for the needed changes. |
Does @Sandra97 outstanding PR actually look to have taken care of most of the syncing of the menu content? Though created in 2018, it's not been merged. |
I'm closing this because we will reuse this repository for the upcoming joomla next documentation. |
What exactly is the upcoming joomla next documentation? |
proof of concept to use docusaurus as replacement for the mediawiki. For the moment carlos starts and tries to convert the cms help pages to docusaurus. |
@HLeithner Who else is involved in this process? Is this supposed to be a one-man-show and the team is left out? |
please talk to the documentation team lead @carlitorweb , I expected that it is a team effort. I don't want todo documentation (since someone told me I'm too "complicated" but thats another story) I just provide the infrastructure I have been ask for. |
The fact is that we were in discussion and the team still had different opinions about how the future documentary should be structured. For a fortnight now, the talks have come to a standstill. There were indeed good arguments against Docsaurus and they were not settled. |
Then it's good that this is a proof of concept repository and not a final decision. |
The Topmenu seems to be hardcoded and not via the CDN.
Therefore is very outdated, which will create confusion for our users.
The text was updated successfully, but these errors were encountered: