-
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
Add scrolling-padding-top: 100px; to docs template #3
Comments
I think most of the website do not even have the latest template. The only thing I know it's located somewhere outside of Joomla. |
Hello Patrick Jackson I want to work on this issue. |
@wilsonge can you add the right files in the repository so we can update the template parts via a PR? |
@mysteriouspla issues like these are part of Joomla's website management, so aren't issues you can work on. If you're looking at participating in contributing more to Joomla get in touch. @wilsonge any chance of getting to this so that the UX on the docs template is improved? |
@wilsonge could you add this request to Hutchy68/Jforeground#6 so that it's ready for inclusion when WikiMedia get updated. |
Hello Sir, |
@karan-vaishnav nothing to work on here - this is an issue that @wilsonge needs to address by just adding the appropriate line of CSS to the template. |
sir I want to Contribute can you guide me |
This is not an issue to contribute to @utkarsh-shrivastav77 Start here to find out more about ways you can contribute to Joomla. |
I'm closing this because we will reuse this repository for the upcoming joomla next documentation. |
@conconnl as per the PR's from last October:
joomla/joomla-websites#1546
https://github.com/joomla/jdotorgtemplate/issues/181
It looks like the addition of scroll-padding-top that was added to the main templates has not made it across to the jdocs template.
Can you added it to resolve the issue raised today in JDocs Working Group on Glip with the jumping to an anchor on the page tucking underneath the sticky header.
The text was updated successfully, but these errors were encountered: