Include page on CC WP

[susannaanas]

The dashboard will be embedded in the CC Summit website. Considerations to take into account:

• The router in the Dashboard React app needs to be able to link to pages within the app.
• URLs from outside the page and the app must be routed to the correct pages.
• The layout of the page must occupy maximum estate on the page while abiding to site specs.

To do

• Contact tech support
• Create new page https://summit.creativecommons.org/hack4openglam-dashboard-2021/
• Copy code from 2020 dashboard
• Modify: Header display:none ja html padding:0
• Add to menu
• Modify .htaccess (support needed)
• Linkki

[susannaanas]

Already happened: A page has been created in CC WP for the new dashboard

[brylie]

For context, I received a request to modify the .htaccess file via email:

.htaccess modification request

> Hack4OpenGLAM Dashboard is a SPA-app, that takes advantage of React Router. We are planning to embed the React app under /hack4openglam-dashboard/ WordPress-page. To make our app’s routing mechanism work on the CC Summit’s website, we need to add something like the following into summit.creativecommons.org’s .htaccess: ``` RewriteEngine on RewriteBase /hack4openglam-dashboard/ RewriteRule ^/$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-l RewriteRule ^.*hack4openglam-dashboard/.* /hack4openglam-dashboard/ [L] ``` > Please be careful with this htaccess-configuration, as I have not tested it yet. The goal is to route everything in /hack4openglam-dashboard/* to a single page: /hack4openglam-dashboard/, which is responsible for handling the routes client-side. If this isn’t possible, we can alternatively try to stick to using hashbang URL routing, which may not need additional configuration. Thank you in advance. (Mikael Hannolainen)

The .htaccess approach would create some administrative overhead and introduce boundary issues between projects. In effect, we would need to

• clone the h4og-dashboard repository on the summit server
• pull remote changes on the summit server for each new release of the h40g-dashboard
• apply .htaccess configuration (assuming Apache server) to the summit server
  • introducing potential conflicts, instability, or security concerns

Alternative proposal

If possible, we should treat this repository as a stand-alone project. We can use a static hosting service such as GitHub pages to automatically bundle and serve the latest project changes. This approach would be more "conventional" and would have the following benefits:

• clean separation between projects (no .htaccess changes or code-mixing)
• lower administrative overhead (latest changes are automatically deployed from the desired branch)

[brylie]

Ping @TimidRobot

[brylie]

@susannaanas mentions the 2020 Hack4OpenGlam dashboard is currently deployed to the Summit website.