Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Drupal Challenge Drupal Challenge
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • Jobsity
  • Drupal ChallengeDrupal Challenge
  • Wiki
  • Home

Home · Changes

Page history
Update Home authored Mar 09, 2023 by Ariel Kanelson's avatar Ariel Kanelson
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
+2 -2
  • Home.md Home.md +2 -2
  • No files found.
Home.md
View page @ 0e03be8b
......@@ -84,10 +84,10 @@ Recommendation: on MacOS and Windows, enable the [mutagen](https://ddev.readthed
Tips:
* Provide ALL information, step by step, on the root readme file for how to install from scratch your Drupal Challenge using DDEV. Try to follow your own steps on a new clone to ensure it works. These will be the same steps the evaluator will follow. When creating another clone of the repo, before starting ddev, change the `.ddev/config.yaml` name attribute to avoid collision names.
* Provide ALL information, step by step, on the root README file for how to install from scratch your Drupal Challenge using DDEV. Try to follow your own steps on a new clone to ensure it works. These will be the same steps the evaluator will follow. When creating another clone of the repo, before starting ddev, change the `.ddev/config.yaml` name attribute to avoid collision names.
* Use all Drupal best practices you know, the evaluator will take them into account. Add standard Drupal comments and feel free to comment on your own custom code when you think it is worth it or adds value.
* Create a clean structure architecture in Drupal showcasing your knowledge of site-building to store and relate the different pieces of data you will retrieve from the API and the proper use of Drupal entities. If you need to install any contributed module, install it by using composer. Put any custom code into a custom module.
* Provide steps for the evaluator on how to ingest content into the website. Think about which cases is it better to ingest data and when to consume data in real-time from the API. Do not send your database, structure, configuration, and content must be imported.
* Provide steps for the evaluator on how to ingest content into the website. Think about which cases is it better to ingest data and when to consume data in real-time from the API. Do not send your database; the structure, configuration, and content must be imported.
* Provide all the information for the evaluator on how to configure the API credentials or what steps need to follow to make the API connection to work.
* Provide a good, cohesive front-end with proper theming to demonstrate your knowledge of working with Twigs templates, use of CSS and responsiveness, Javascript, hooks and preprocessors, and other Drupal 8/9/10 functionality. Put all your theming code, assets, styles, and templates into the provided dc theme.
* For some challenge feature solutions, you might need to be creative. The challenge instructions are crystal clear. In case you have doubts or questions, take your own assumptions. Document them on the README file to let the evaluator know your decisions.
\ No newline at end of file
Clone repository
  • Drupal Challenge Instructions
  • Home