-
Notifications
You must be signed in to change notification settings - Fork 2
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
use this project for Drupal side #1
Comments
IMHO we should only have one website ( the drupal one ) and here is the right place for it |
I think it was @nebulak opposing yesterday. He wanted "a simple, static page". I'm fine with both. |
@ligi : The Drupal page is used as our backend(+API-Endpoint) and gets filled with a lot of articles in different languages... So at the moment, if you visit the normal Drupal-Website it's just a big chaos. I would create the info page/website using Github pages to seperate our backend/api and the normal website. IMHO, if we only use Drupal I see the risk that someone who just wants to edit a page, could make a mistake and makes our API temporarily unusable... |
I agree, that we should have a very simple landing page. Probably, this won't be drupal.
I think, this is a separate problem of the API. It should fail softly. Opening own issue: refugeehackathon/refugeetransit-api#4 |
I'd say we follow this proposal for using the project: refugeehackathon/refugeetransit-design#1 and put the public project description here on GitHub Pages
The text was updated successfully, but these errors were encountered: