You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the workflow for updating the CKAN header and footer is very manual. it involves scraping the WordPress site HTML and copying the relevant HTML into a CKAN template file. then adjusting CSS classes to match existing ones in CKAN. Inevitably there has been some small CSS change in WordPress that requires significant tweaking to the CKAN CSS to make it all look the same.
Solution:
find a way to pull menu changes and CSS from WordPress into CKAN. perhaps a shared CSS file that is used for both WordPress and CKAN sides of the header/footers? HTML would still need to be pulled across but this could also be a shared file. Would mean doing away with the mega-menu plugin in WordPress likely. That would work for pacific and Atlantic but may not work for OGSL
Alternatives:
???
Additional context:
???
The text was updated successfully, but these errors were encountered:
this pr adds a command line command to pull the menu from a wordpress site that has implemented our api change into a file usable by ckan. It utilizes a template file so that individual RA's can customize there menu as needed.
to start the sync, run:
ckan --config=/etc/ckan/production.ini menu create url template output [echo=false]
Currently, the workflow for updating the CKAN header and footer is very manual. it involves scraping the WordPress site HTML and copying the relevant HTML into a CKAN template file. then adjusting CSS classes to match existing ones in CKAN. Inevitably there has been some small CSS change in WordPress that requires significant tweaking to the CKAN CSS to make it all look the same.
Solution:
find a way to pull menu changes and CSS from WordPress into CKAN. perhaps a shared CSS file that is used for both WordPress and CKAN sides of the header/footers? HTML would still need to be pulled across but this could also be a shared file. Would mean doing away with the mega-menu plugin in WordPress likely. That would work for pacific and Atlantic but may not work for OGSL
Alternatives:
???
Additional context:
???
The text was updated successfully, but these errors were encountered: