mstekl commented on pull request #90:
URL: https://github.com/apache/ignite-website/pull/90#issuecomment-967344028
1). Would it be possible to get some documentation about how to update,
build & deploy the site? Probably most of the Ignite community have zero
experience with Pug & web dev tools, and will not know how to run this site
locally to make content updates, as well as build & deploy. Also would be
helpful to include some basic guides on how the community could make changes to
CSS if needed, and recompile on their own.
2). Same thing would be necessary for those sections that will require
regular updates, like for example the Upcoming/Past events.
3). I noticed all of the Google Analytics events are not anymore. @dmagda,
could you please confirm if we'd like to continue collecting stats and which
ones? I guess at least the ones for download page are important, am I right? We
used to have something like this:
`onclick="gtag('event', 'download', {'event_category':
'apache_ignite_source_download', 'event_label':
'apache-ignite-2.11.0'});">apache-ignite-2.11.0-src.zip</a>`
4). Regarding downloads.html file, the compiled .html doesn't include part
of the original CGI scripts used by Apache infra. As an example, links to
binaries on the older website are composed like this:
href="[preferred]/[distdir]/2.11.0/apache-ignite-2.11.0-src.zip
And there are some components to select the downloads mirrors, like on
below. Please copy behavior from older .html file
```
<form action="/download.cgi" method="get" id="SelectMirror">
Selected mirror:
<select name="Preferred" onchange="submit()">
[if-any http]
[for http]
<option value="[http]" [is http preferred] selected="selected"
[end]>[http]</option>
[end]
[end]
[if-any ftp]
[for ftp]
<option value="[ftp]" [is ftp preferred] selected="selected"
[end]>[ftp]</option>
[end]
[end]
[if-any backup]
[for backup]
<option value="[backup]" [is backup preferred] selected="selected"
[end]>[backup] (backup)</option>
[end]
[end]
</select>
<input type="submit" value="Change"/>
</form>
```
5). According to this new structure of the repo, the webroot dir is set to
be `public/`. And I'm not sure if it's possible with Apache's infra to serve
the website from that dir instead of the root dir, because of other files .
Would it be possible to refactor the repo in such way that the Pug source files
are placed on a dir like `_source/` and setup the build script to output the
final files into the root dir?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
