Docs Layout Update #91
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Part 1 of dividing my last PR into multiple sections. - Created a `JS` folder for structure organization. - Created a file called `scripts.js` that holds all scripts in one place, for easier maintenance in the future. - The script contains reusable / utility functions like `loopAddClass`, `loopRemoveClass` and `loopToggleClass`. - There's already functions inside this file that at the moment might not point to anything, but everything will tie together at the end.
The sidebar will be populated with link anchors to sections/titles of the page, via JS
- Added a Scroll To Top button
- Created a popup for the home {{ content }}, since that's a one time message that only needs to be shown to users once.
- HTML5 conversions
- First wave of `site.baseurl` links implementation from @arjunsuresh 's PR
…alphabetically - Current visited page is now highlighted at the navigation bar. - Continue fixing internal links (Arjun's PR). - Mobile resposiveness.
rxchun
changed the title
rxchun
added a commit
to rxchun/q2a.github.io
that referenced
this pull request
Jun 18, 2025
Note: This is supposed to be an extension for the last PR q2a#91 This PR introduces a new feature that enhances plugin visibility and compatibility display: - Fetches all plugin repository links and retrieves their metadata. - Stores metadata locally using localStorage for performance, and also not bombard fetches to `raw.githubusercontent.com` on every page request. - Dynamically generates a footer section for each plugin with: - Repository update date - "Q2A Tested With" tag based on the plugin’s `max_q2a` metadata.json key, if available. This helps users quickly assess which plugins are compatible with their Q2A version and when they were last updated. I also added a message to the Plugins & Themes pages, explaining that "outdated" plugins doesn't necessarily mean that they don't work. Some of them just don't require to be updated as frequently. Also, everybody can create PRs to update the `max_q2a` version of a plugin they know it works, because they're using it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part 1 of dividing my last PR into multiple sections.
JSfolder for structure organization.scripts.jsthat holds all scripts in one place, for easier maintenance in the future.loopAddClass,loopRemoveClassandloopToggleClass.