Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rethinking website purpose and generation #26

Open
ema-pe opened this issue Nov 27, 2024 · 0 comments
Open

Rethinking website purpose and generation #26

ema-pe opened this issue Nov 27, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation refactoring

Comments

@ema-pe
Copy link
Collaborator

ema-pe commented Nov 27, 2024

Currently, this repository is configured to generate a static website via GitHub pages (using Jekyll) at unimib-datai.github.io/dfaas. Jeckyll takes all markdown files, even from subdirectories like simulation or framework, converts them to HTML and publishes a static website. From the default page there are some links to the other subprojects. I have the feeling that there is no added value in having a website in this form, because all information can be retrieved directly from the repository. We should also rewrite the documentation, but that is another issue.

In my opinion, I prefer not to have a GitHub page, it is better to point directly to the repository where the code and documentation can be found. Otherwise, if we want to keep a website, I would spin off a new dedicated branch or create a new repository under the group.

@ema-pe ema-pe added documentation Improvements or additions to documentation refactoring labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation refactoring
Projects
None yet
Development

No branches or pull requests

1 participant