Everyone agrees menu links should be entities. Jury is out on Menus => Let us do menu links to start with and that will inform subsequent thought. We can, nevertheless, say that the original idea of menus as bundles of menu links is off the table.
I believe as fago is currently using the terms:
Property: A compound data element on an Entity (basically what we call "Fields" in Drupal 7).
Field: A special case of a Property that is user-added rather than defined by the module that declares the Entity type.
Everyone agrees menu links should be entities. Jury is out on Menus => Let us do menu links to start with and that will inform subsequent thought. We can, nevertheless, say that the original idea of menus as bundles of menu links is off the table.
I believe as fago is currently using the terms:
Property: A compound data element on an Entity (basically what we call "Fields" in Drupal 7).
Field: A special case of a Property that is user-added rather than defined by the module that declares the Entity type.
When I look through these two lists I see a lot that is developer focused. Better internal and external APIs are definitely targeted at developers and those are 2 of the 11 goals for Drupal 7. When it comes to Drupal 8 configuration management and web services are both things that have a definite impact on coders. The html 5 initiative was for front end developers. Without even digging down into these initiatives I can see a top down approach of developers as a target audience.
When I look through these two lists I see a lot that is developer focused. Better internal and external APIs are definitely targeted at developers and those are 2 of the 11 goals for Drupal 7. When it comes to Drupal 8 configuration management and web services are both things that have a definite impact on coders. The html 5 initiative was for front end developers. Without even digging down into these initiatives I can see a top down approach of developers as a target audience.
Drupal 8's trajectory of a first class REST server built on Symfony is very admirable. If they pull it off might even use it #symfony_live
— Code In A Box (@codeinabox)
@crell's talk makes me want to hug Drupal. Amazing how deeply they've embraced outside libs. An example for the rest of us #symfony_live
— Ryan Weaver (@weaverryan)
not afraid to admit I didn't have much love for Drupal... having said that, Drupal & Symfony looks like a great leap forward #symfony_live
— Chris Rickard (@chrisrickard)
Drupal 8's trajectory of a first class REST server built on Symfony is very admirable. If they pull it off might even use it #symfony_live
— Code In A Box (@codeinabox)
@crell's talk makes me want to hug Drupal. Amazing how deeply they've embraced outside libs. An example for the rest of us #symfony_live
— Ryan Weaver (@weaverryan)
not afraid to admit I didn't have much love for Drupal... having said that, Drupal & Symfony looks like a great leap forward #symfony_live
— Chris Rickard (@chrisrickard)
We will open the core sandbox and meta issue soon, once the above dependencies are resolved or worked around, so that contributors can begin to explore what it means for Views to be in core.
We are planning one last major sprint before feature freeze in the week preceding BADCamp. (Pantheon will be hosting this sprint; more details soon.) The BADCamp sprint will be our chance to coordinate our final push to make Views core-ready. Once Views is committed to core, all further work will take place in our sandbox and the Drupal core issue queue.
Gives content access permissions to users for content that references the users with User reference or Entity reference.
This is great if you want your content authors to be able to choose additional authors, or choose who can view their content, as well as being able to display the list of authors or viewers within your content, or in views displays.
“In the month leading up to the redesign, we saw that as many as 18% of our users were on mobile devices. Drupal has many available solutions for implementing responsive design, which serves the same content across devices, formatted for the appropriate screen size. We’ve been able to deliver the same site for both mobile and desktop, optimized differently, including videos and forms. As a result of doing things responsively, we’ve seen a major increase in the rates of people on mobile devices filling out forms.
“Drupal is a champ at integrating with other systems.