Drupal

Building a complex member website

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 11:24

Hi all,

Looking for some advice around a project on my plate. The project is a association website with member login/logout, protected content, and personalization. Myself and my devs don't have much experience with Drupal outside of some tutorials.

I would love to hear recommendations to get started and estimates for how long a project like that would normally take an experienced Drupal developer versus a beginner Drupal developer (in terms of hours).

Thanks in advance

submitted by /u/tk_developer
[link] [comments]

DrupalCon Nashville 2018: Configuration Management for Humans

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 11:16

Configuration management for Drupal 8 is a pain point for many. In this presentation, Tim Broeker from Electric Citizen provides some insights on how to take on this challenge.

submitted by /u/drupaleer
[link] [comments]

Commerce Admin Checkout

drupal.org - Modules - Mon, 04/23/2018 - 10:50

This module allows a site administrators to use Drupal Commerce checkout to create orders for customers. This is useful if you have customizations to your checkout workflow (custom panes, etc) that you don't want to recreate on the admin side of Commerce.

This module includes 2 checkout panes:

Categories: Drupal

Weekly Drupal beginner questions thread

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 10:08

Ask your newbie questions here! No judgement!

(Check out the weekly post schedule in the sidebar)

submitted by /u/AutoModerator
[link] [comments]

ComputerMinds.co.uk: Rebranding ComputerMinds - Part 3: Website design

drupal.org aggregator - Mon, 04/23/2018 - 08:47

Now that we had settled on the branding and had established and planned exactly what we needed to create, I could start looking at designing the new website.

I wanted a clean, spacious site with a modern look and feel. I always keep a close eye on changing design trends and it was important that for our site I was careful to design something that would age well.

Over the years, Photoshop was my go-to software choice when designing, but after becoming increasingly frustrated by slow workflow I recently switched to using Sketch for larger projects. Sketch uses a modular, symbol based design where elements are quickly and easily reused. This makes edits super easy - changing the design of a button would change it everywhere it is used, not allowing inconsistencies to creep in.

Document setup involved ensuring some useful plugins were installed, then creating a new document with the standard Sketch template ‘Web Design’. This template gives you three pages to get going - one for assets (symbols), one for a style guide and one for the actual designs. Pages in Sketch are basically just canvasses but having these three allows easy navigation and quick workflow. An adjustment to the layout settings to ensure we had the correct size grid and we could almost get going.

The last thing I did was to, in the style guide page, create some simple shapes of all the colours from the branding guidelines that I created previously. I then created styles with these colours. This way, the colours would be consistent and if they ever changed it was easy to change them in one place, and not every item that used them.

Starting with the desktop header (as a symbol so it could be reused on each page), I immediately threw in the compact logo, without the word ‘ComputerMinds’. This was following on from an earlier decision to move away from the company name being so prominent. The address bar would always show the name anyway. After years of always seeing company logos on the left of the header, I wanted to move away from this. The recent rebrand of The Guardian saw a move away from this too, the new logo firmly positioned on the right of the header. Now, we had something most didn’t, a symmetrical logo. This meant we could have a symmetrical header by placing the logo in the middle.

Next up came the footer, also a reusable symbol. As we weren’t using the company name in the header this was a perfect opportunity to use a larger logo. Keeping it clean, I added the compact logo, contact information, social links, 2 menus and legal information, meeting requirements.

Once the the header and footer of a site are designed it really begins to look like a website. Before I could design any other page elements I needed to design something that would also be seen on almost every page - buttons. And with buttons come form elements. I've seen a recent trend with buttons with square corners and with either block colours or simple line borders. For our site I wanted something a little different so added a subtle shadow and simple movement on hover.

As with many of our recent development projects, we wanted to use tiles. This would allow us to create pages using tiles as building blocks, which is exactly what we’ll need for most pages. So these were designed next. As mentioned earlier, I wanted to create a more engaging experience for users by encouraging more visual content. With this in mind I created a collection of tile designs that incorporated large images and video and used the full width of the screen, bleeding off of the grid. These also used consistent, large headings and body text.

As well as visually engaging tiles, it was also necessary to create tiles to communicate through text alone. Using the colour palette created in the branding phase, I designed tile types that would allow variation visually through background colours, leaving the text to be communicated clearly. It’s also worth noting the prominence given to headings. Purposefully large to work well with whitespace, the headings make it absolutely clear what the visitor is reading.

During the designing of the tiles, I was also always thinking of the pages the site would have to be sure that the tiles were designed with the likely content in mind. Creating each tile type as a symbol in Sketch allowed me to quickly create page designs for multiple pages and adjust styles centrally.

In addition to these pages, we also required designs for pages that would not be made using tiles. A big part of our site and one we’re proud of is our many articles. Starting with a single article page I wanted to design a page that focussed the viewer on the content, without distraction. To achieve this I created white space either side of the content, narrowing the page and focussing the viewer (you're locked in right now, aren't you!). I also incorporated a title tile to display the article title clearly and created a header and footer for the article with all information the viewer might expect. These title tiles are also used on most pages of the site, making it absolutely clear which page you are on and adding further consistency. 

So the design was now complete. We had headers, footers, tiles, form elements, headings, body and more in all screen sizes. Such as the way we operate at ComputerMinds, this was all subject to adjustment as the project grows and more people get involved the requirements may change. As I said before, this is not a problem when using Sketch with the reusable elements.

Next up, we were to try something new - creating the front end using a pattern lab!

Categories: Drupal

Step-by-step site building with Drupal

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 07:20

I'll start building my first Drupal site soon, and are looking for best practices to base my planning on. I'm sure there are many considerations I should be aware of in advance, before starting to build the site.

I came across https://www.drupal.org/site-building, in which there seems to be some very useful information. But what I'd ideally want is a step-by-step approach to follow, so that I can be sure that I do things in the right order - without such a approach, I'm not confident I'll see all the possible caveats in the planning phase. As a Drupal newbie, I don't know which topics to cover in my planning, as I don't know the right questions to ask myself.

Do you know of any such step-by-step site building list, that will make me think through everthing I need to in the planning phase?

submitted by /u/kenneho
[link] [comments]

OpenPublish no longer active, is there anything like it?

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 06:17

I’d like to launch a newspaper. I want to easily upload images and text and titles, and have Drupal automatically handle everything else (e.g designing the front page, publishing articles in a nice flow, and other things). OpenPublish seems to be just that but it has been discontinued.

submitted by /u/MrOaiki
[link] [comments]

Name redactor

drupal.org - Modules - Mon, 04/23/2018 - 03:53

This module implements a PET (Privacy Enhanching Technology) that lets the user to hide personal data from search engines.

It is part of The PET project. For more information, visit The PET project website.

Categories: Drupal

Tim Millwood: Getting started with React and Drupal

drupal.org aggregator - Mon, 04/23/2018 - 02:20
Getting started with React and Drupal

Over the weekend I decided it was long overdue that I learnt React, or at least understood what all the fuss was about, so with npm in hand I installed yarn and started my quest.

We're going to use Create React App to setup our base React install. First install then run the command to create a react app called "drupal-react":
npm install -g create-react-app
create-react-app drupal-react
cd drupal-react

You can now run npm start (or yarn start) to start your app locally and open it in a browser. Here you'll see a React default page, this is all created from a React component called "App". If you take a look at the file src/App.js you will see the component and how the render() method returns the page HTML as JSX. We need to replace to the code returned here to show some Drupal nodes, so how about replacing it with (or just adding) <NodeContainer />. This will call a new component, so at the top of app.js we will also need to import that, so with the other import code add import NodeContainer from './NodeContainer';.

Now to create the NodeContainer component. First we need to add the Axios library which we'll use to query the Drupal REST API, run npm install axios --save. Then create the file src/NodeContainer.js, and in there add the following code:
import React, { Component } from 'react'
import axios from 'axios'

class NodeContainer extends Component {
  constructor(props) {
    super(props)
    this.state = {
      nodes: []
    }
  }

  componentDidMount() {
    axios.get('http://example.com/api/nodes')
    .then(response => {
      this.setState({nodes: response.data})
    })
    .catch(error => console.log(error))
  }

  render() {
    return (
      <ul>
       {this.state.nodes.map((node) => {
          return(
           <li={idea.nid}>{node.title}</li>
          )
        })}
      </ul>
    )
  }

}

export default NodeContainer

At the top of the file React and Axios are both imported, the class for NodeContainer is then created. The constructor method is where we add the state node, componentDidMount() is called to get the nodes from the View /api/nodes, which then gets rendered as an unordered list.

To create the /api/nodes view install the core Rest module. This will allow you to create a "REST Export" view. Here the path can be set to /api/nodes, and you can select nid, and title.

As long as you left npm start running, you should be able to go back to your browser, and view a nice list of Drupal nodes being rendered in React.

Next, routing, to make these node titles clickable! 😱

timmillwood Mon, 23/04/2018 - 07:20 Tags drupal planet drupal-planet drupal drupal8 drupal 8 drupal development react reactjs javascript Add new comment
Categories: Drupal

Update problems from 8.4.5 to 8.5.2 :'( Help?

Drupal - Open Source Content Platform - Mon, 04/23/2018 - 01:56

I keep getting HTTP Result Code: 200 Debugging information follows. Path: /update.php/start?id=2756&op=do_nojs&op=do StatusText: OK ResponseText: Fatal error: Declaration of Drupal\visitors\Form\Settings::buildForm() must be compatible with Drupal\Core\Form\FormInterface::buildForm(array $form, Drupal\Core\Form\FormStateInterface $form_state) in /public_html/modules/visitors/src/Form/Settings.php on line 0

Anyone know what that might mean?

submitted by /u/ed523
[link] [comments]

govi_test

drupal.org - Modules - Sun, 04/22/2018 - 21:30

test

Categories: Drupal

Pages