Open-Source-Orchard-Core-Extensions
Open-Source-Orchard-Core-Extensions copied to clipboard
Lombiq
Looking for some useful Orchard Core extensions? Here's a bundle solution of all of Lombiq's open-source Orchard Core extensions (modules and themes). Clone and try them out!
[OSOE-353](https://lombiq.atlassian.net/browse/OSOE-353) [OSOE-353]: https://lombiq.atlassian.net/browse/OSOE-353?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[NEST-365](https://lombiq.atlassian.net/browse/NEST-365)
Go through the _create-jira-issues-for-community-activities.yml_ workflows in all submodules, and set `suffix-issue-titles: "false"`. We don't actually need to include the component in the Jira issue titles since it's also readily visible...
... after it is edited by pnpm. Add these lines to all _.gitattributes_ files in OSOCE and the template repository: ```gitattributes # Keep the LF in pnpm-lock.yaml files to prevent...
This solution should also serve as a demo of all our modules. Probably the best would be to add a setup recipe that enables configures everything for a demo so...
Currently, we commit the wwwroot folders instead of building them during publishing with [Gulp Extensions](https://github.com/Lombiq/Gulp-Extensions), which is bad. Instead, we should build static resources as we do in the OSOCE...
[LMBQ-318](https://lombiq.atlassian.net/browse/LMBQ-318)
[LMBQ-340](https://lombiq.atlassian.net/browse/LMBQ-340) [LMBQ-340]: https://lombiq.atlassian.net/browse/LMBQ-340?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Hi @DemeSzabolcs Before I continue along this path I wanted to check with you first on my current approach: See also: https://github.com/Lombiq/UI-Testing-Toolbox/pull/354 Currently to make sure that it's backwards compatible...
[OSOE-819](https://lombiq.atlassian.net/browse/OSOE-819) Also see: https://github.com/Lombiq/Helpful-Libraries/pull/251