Hodges' Model: Welcome to the QUAD: web design

Hodges' model is a conceptual framework to support reflection and critical thinking. Situated, the model can help integrate all disciplines (academic and professional). Amid news items, are posts that illustrate the scope and application of the model. A bibliography and A4 template are provided in the sidebar. Welcome to the QUAD ...

Showing posts with label web design. Show all posts
Showing posts with label web design. Show all posts

Monday, January 02, 2023

Out of hand ...

This blog is a pain, as is twitter.

I've known for ages -

H2CM new website - A short-form project brief

Twitter on hold: Blog a trickle ... 

Dries! I promise ...  (Sorry!)

I've known since the start of W2tQ back in April 2006. The web - software is change.
 
Blogging and twitter are a distraction.
 
The blog has helped to frame ideas. I can see now though (hindsight eh!), how unprepared I was in 2014 for a PhD, not just financially (self-funded), but having a question. I've had a project since 1988, but what's the Question?
 
People get in touch (SPAM reaches the inbox) with web design, SEO service offers. They point to how 'ill' my website / blog is. No website/blog are specified, no business address, details, there's a personal/business name that doesn't reflect the email signature.

I know that 'analysis' of the blog reveals a pile of errors, missed opportunities. And, yes; there is a much better online solution to drive income ...?

So, after the past year and especially last month, 2023 will be much much quieter on W2tQ. What will be posted?
  • Book 'reviews'
  • Quotes, insights from books I'm clearing as relates to Hodges' model
  • Occasional timely insights from press / media*
  • Conferences, Calls for papers, Journal news
  • Q&A with other people about h2cm; critique of the model (well you never know!)
  • Update on draft papers, and new citations

So, yes similar threads but the volume must be much, much less.

Twitter will likewise be less, but that doesn't mean - like many - I'm running elsewhere.

I'll be reading, writing, drawing 👍, following webinars and specific YouTube sessions ... studying and will pick up Drupal, github and Pharo. There's a hosting account to put to work, or at least experiment with. Over the past year my thinking about Hodges' model has (imho) progressed. I'm quite excited about what might follow. I'm also daunted, by the dual challenges of the 'development stack' (Drupal is at version 10 and counting...) on the one hand, and logic - relational analysis on the other.

Many thanks for your interest thus far.

HAPPY NEW YEAR TO ALL.
 
*Oh gee! I replied to a thread on #HIFA yesterday and tweeted this a.m.. It would be remiss of me not to pick this up, so post to follow soon.

Monday, April 12, 2021

DrupalCon Summits: Higher Education & Healthcare

DrupalCon Attendee
DrupalCon North America 2021 started today and the programme includes  several summit events; two of particular interest next week:

Higher Education Summit

Using Drupal at a college or university? Attend this summit to connect with other Higher Education Drupal users, typically web developers, managers, communicators, graphic designers,  editors and the like. 

Learn from peer Drupal users and experts, working in a variety of contexts in the higher education sector, about the ever-changing Drupal and web landscape, including new trends and current best practices. 

Expect small group discussions, lightning talks, a keynote, and other formats allowing you to engage with your peers. 


The DrupalCon Higher Education Summit is informal, and focuses on best practices, case studies, and discussing solutions to the unique situations inherent to higher education.

Who should attend?

The DrupalCon Higher Education Summit is open to all higher education staff, volunteers, and service providers who are using, or considering using, Drupal as part of their technology stack. This summit is not intended for vendors to pitch new business. 

https://events.drupal.org/drupalcon2021/summit/higher-ed 


Plus:

Healthcare Summit

The healthcare space is now, more than ever, a critical area for all development communities. Digital communication and technologies offer the promise of improved access for patients, but building good solutions requires a solid foundation in accessibility, security and compliance.

Whether you are at a pharma working towards the next vaccine or therapy, a hospital network treating patients with AND without COVID, an insurance company making sure all patients have access to critical healthcare during this tough time, there is much for you to gain from this summit.

Join us for a day of facilitated peer-to-peer problem solving combined with industry leaders sharing their experience solving common challenges like building a digital roadmap for a healthcare system, vaccine distribution platforms, and building user-centered patient experiences.

Who should attend? 

Anyone interested in hearing how companies and the community are creating rich Digital Experiences in the Healthcare space and all levels of colleagues in the Pharma, Medical, Clinical, Hospital, Payers, Caregivers and Healthcare Professional space.

https://events.drupal.org/northamerica2021/summit/healthcare 


Tuesday, December 15, 2020

Blog, Twitter, Drupal, Reading and Writing ...

It is over a year - October 2019 - since I updated on the above

First, let's get the elephant sorted. The elephant is the 'new website'. A non-trivial task in so many ways, not just physically, but psychologically, giving rise to frustration, embarrassment but still an exciting and promising 'project'.

The IT literacy I do possess allied with conference and media engagement suggests I should give up trying to build this myself and pass the 'requirement' and 'specification' to real software developers - and stop acting the goat (is that elephant smiling?). 

Lockdown has been a great opportunity to crack-on with the website, so no excuses. Hopefully the posts over the past year can still represent learning, growth and progress.

At the start of 2020 I was hoping to do some p/t tutoring. COVID-19 upset that plan and with it planning for a pilot study and engaging with prospective partners. I am ready to pick this up, but in terms of Drupal I have to refer back to 2019...

Learning Drupal 8
At DrupalCamp London 2019 I won 'Learning Drupal 8' in a raffle. I replied to Dora who emailed the news, but don't think I thanked the company here So thank you to Inviqa and the many other sponsors who make these events possible.

Drupalcamp London: And all that jazz

I attended this year 13-15 March, pre-lockdown (obviously) and the tone was somewhat muted. Many people were unable/unwilling to travel. I felt ridiculous myself being in London (in February too) and a nurse. That feeling was magnified when pre-booked I found myself in the basement again for jazz. Like everyone at present, I miss London and so many other places. Human nature being what it is, during lockdown 1 & 2 on reflection there was a sense of relief in having run the gauntlet in February and early March.

Next year, DrupalCamp London will be online. 

Last week and last minute, I signed up for DrupalCon Europe, not in Barcelona but online. Still sorting (reducing) papers, I can see how through Drupal versions 7 to 8, the platform is focused upon 'enterprise solutions'. While I'm not an Enterprise (but would love to be a crew member), the project that is Hodges' model warrants the potential to scale.

DrupalCon Europe was a confusing experience - in a  positive sense. I missed the journey, the Basilica Santa Maria del Pi, the Guitar concerts and much more. As many of us have discovered, I was pleased to avoid the additional costs of travel and accommodation. Given this, my saying that the 250 Euros was worth it, has a less hollow ring. I missed even more the buzz of the community, which was still very much evident online. I'm looking forward to the NWDUG online meeting on the 22nd.

I know (!!) I've said this before: but I really, really need to stop blogging, tweeting and exercise this itch to the exhaustion of possibility. I've a co-authored draft to complete for submission and (two) books to read for review. So that will be an ongoing thread. Finally I will also make use of the text above.

With each abandoned (messed-up) Drupal 'dev' site, I've carried forward the legacy HTML pages that are Brian Hodges' original lecture notes. Following DrupalCon it would be progress to have more tangible outputs to carry forward, apart from being able to get to were I was much quicker. Having a content strategy is one take-away c/o the sessions that I plan to secure.

Noting the two most recent additions to the bibliography, if I can help you use Hodges' model, please let me know (I may need the distraction).

Wherever you are - take care; and for me if this is the journey - that's great too. I'd like to think there is some learning to be had here - even if not in the form of a reflective workbench.


Friday, October 16, 2020

Persistent or Global navigation: Hodges' model

Interfaces are hardly novel these days, even our acknowledging them is a moot point. An interface that is effective will be transparent to the 'user' who is able to get on with the task, the process that is their purpose. For web design, medical devices and

There are many posts on 'interfaces' here on 'Welcome to the QUAD' from 2007 to 2020:

Hodges model: What is it? [2] It’s an interface... 

(Contrast this view, perhaps, with recent posts on Hodges' model as a matrix.)

VerbAtlas 1.0 - Semantic Role Labeling and beyond! c/o Roberto Navigli 

Don't Make Me Think (2006)
- and the tag 'interfaces' (59).
 
Hodges' model remains an interface to me.
 
The homepage for the website 1998-2015 presents Hodges' model - as the interface - to the user (visitor).

In revisiting (before it visits the charity shop) Steve Krug's Don't Make Me Think (2006) reference to persistent navigation or global navigation (p.62) reinforces the fact that humanity needs an interface for health and care. Two qualities that such an interface needs include:
  1. Persistence in being Cognitive (isn't everything?) but in the sense here of being simple and so ready-to-mind.
  2. Being Global as in Global Health, plus Universal Health Coverage, generic, applicable to all persons, contexts and situations.

Sunday, May 20, 2018

Drupal - update: users, roles, content and permissions

I just thought I'd provide an update on the new site.

There's still nothing new on the hosting account. I managed to update on localhost from 8.5.0 to 8.5.3. As I went to the Manchester Drupal Sprint two weekends ago I had a couple of errors. Webform was proving awkward but that was probably me the way I tried to remove it in order to update. It appears there have been some problems, but switching on "Logging and errors" I had more errors that weekend and working through with advice and support at the Sprint things resolved!

Poking around has been really useful and thus far I've not had to start from scratch. Webform is updated but I realised previously I have only scratched the module's surface. Then there is Paragraphs! This is the challenge with Drupal and the range of modules available as explained at DrupalCon Nashville. I know, I know, I've picked up pen and paper and am fleshing out users, roles, content and permissions. This is a distraction. There has always been help available - that's the Drupal community. I've someone to chat with now and looking forward to updating Richard and help to get the new site live. Richard was at Szeged my first Drupalcon in 2008. I remember the advice of Chris, Dan and James back then and Phil, Nathan and others since: Just do it!

So I can't keep scribbling on paper - or here...


Sunday, April 08, 2018

A new Paradigm? No just Paragraphs...

While I have not had the practical reason to apply it (to my shame) I have known of 'maintenance mode' for donkey's y-ears. I have been listening. As tweeted earlier this week, I've been trying to remove Webform so I can update / replace it. I'm avoiding core 'experimental' modules in an attempt to avoid future problems. I'd managed to remove webform bootstrap, but trying to delete from the usual Drupal interface did not work. I checked the tables and those for webform were empty. Impatience set-in and I removed the folder within modules. That was the big mistake. For a time there, I could not access the localhost site on my laptop. I thought it had gone...

I had a MySQL backup and imported this while a CTRL 'Z' restored the folder. This did the trick. I have the HTML source for the archive pages as files too.

At several Drupal events Paragraphs has been presented as very useful site building module. With four 'basic pages' whatever follows will benefit from and no-doubt demand more thought about content types. Checking out some videos Paragraphs really does seem to fit the bill when allied with field group.

I'm looking forward to the local Drupal meetup in Manchester this Tuesday.

Thursday, March 08, 2018

Drupalcamp London: And all that jazz

Drupalcamp London was a bootcamp literally in light of the weather. This affected the schedule a bit but it was well worth attending.

The first session on my list was not the intended module development but:

Flexible content editing with paragraphs and Drupal 8 - with Baddý Sonja Breidert who stepped in at short notice. We were encouraged to look at Open Doors as an example of Paragraphs being deployed. The fact that there were 25 types of paragraphs prompts the thought - not so much how many would I would need but the users? Apparently, paragraphs are not that user friendly to edit. Navigation was indicated 'Manage Display' - 'Preview' - 'Paragraph'. The 'environment indicator' flagged whether the site in use was live or dev: a reminder. A future tip included not using entities, but media for anything reusable. Reusable paragraphs were applied to banner and images, using simple entities. There were some special functions (and specific modules) in the table of contents, entity embed, entity browser, insert view and add map.

In considering when to use paragraphs this connects with choosing content types - another key question for me. There was a lot more in what was a 'changed session'. I'll check the slides / videos were available and for those below. The three keynotes were excellent too:

Let’s take the best route - Exploring Drupal 8 Routing System

Drupal in the era of microservices

"Hi user, I am Drupal. How can I help you?"

Accelerating Drupal projects with Thunder: a case study

In 'Make your site findable' dutchyoda Dick Rensema pulled me up short. So, I will check out the metatags module and use this from the outset. As for being findable - it's also best to have separate text and images not have both within a WYSIWYG editor. Another point is to 'make it long'. That sits well for the archive pages for Hodges' model.

Lunchtime on Sunday was preceded with gambry on Plugin API, a key idea being:

ENTITY - Same model different data
PLUGIN - Same "thing" type different ways

This was a captivating, dense, rich session and one to revisit.

Finally, the 0930 start in London helped as I'd been up late. Ronnie Scott's is an amazing experience, the second house from 1030 doors open through to 0300: I left at 3 thanks also to Resolution 88.




Sunday, December 24, 2017

Focus on Theory - wither the website (gulp)

"A subtler effect of ego is one that doesn't threaten reputation so much as how you prioritize what is important. The threat is based on a sense that your opinion, approach, and perspective are the only ones with merit. While arrogance is one outcome of these elements, a much subtler risk that can bubble to the surface is becoming too focused on theory.

...
Unfortunately, some folks have something of a love affair with theory. Many of these people write extensive blog entries, give very generic (though well-meaning) presentations, and often seem to think that their primary role is to impart knowledge to others and sound as wildly academic as possible. But there is no secret ingredient in growing community. What makes a great community leader is experience: trying new ideas and concepts and learning from the successes and mistakes." p.17.

Bacon, J. 2012. The Art of Community, Building the New Age of Participation (2nd ed.)  CA, O'Reilly. (1st edition)

@jonobacon

Saturday, April 30, 2016

Buses, Students, Tech and Models of Care

I continue to be surprised, informed and stimulated by the many contrasts and similarities between nursing and information technology. A constant encounter as a mentor is hearing accounts about student nurses and their learning experience. After 12-18 months since beginning their student career what are student's learning, being taught? And yes: nursing theory and models of care still seem twee, out-of-date, out-of fashion.

Change is inevitable of course; in tech if you are not on-board (as in the web), there is a progression of buses and you can get on at any time. At least I hope that's the case. As Web Design magazine asks: "How will CSS be styling the web in 2017, 2018 or 2019?" So for students there are many university blocks, lectures, clinical placements, mentors...: so many buses. Hopefully they really do get on-board sooner rather than later.

The snapshot of evidence as I have it re. models of care, nursing theory and reflection suggests there is quite a vacuum at a time when there is both a need for a tool like Hodges' model and an opportunity.

There are valuable lessons in the history of models of care while we relish the challenges of the future. Those lessons are still relevant as the nursing community and its practitioners constantly travel between the mechanistic and humanistic forms of knowledge that nursing demands.

Technology changes all the time and with it, the buses, the roads and even the bus stops. Clearly, we need our students to be as well equipped as possible. Not to deal with change, then it is too late. We need future practitioners to be able to critique potential change. This is crucial when future change involves nursing itself and nursing's values.

Tuesday, May 27, 2014

From: Slow is beautiful (Bloomstein, net, July 2014)


The quotes below are from a one page article in the July issue of net magazine. The message is that while efficiency in online experiences is critical especially in ecommerce and business there is still a place for 'slow' and content that asks questions (I hope so):

"Second thoughts undermine efficient ecommerce experiences. But if we only value efficiency, we ignore opportunities for learning and validation that characterise effective, less transactional experiences.

... (How several brands - "Foster Good Decisions")

DESIGN FOR QUESTIONS

These content types and design patterns aren't necessarily the fastest way for users to complete transactions. Instead, they help users engage with purchases with greater confidence, satisfaction and certainty. When content pushes us to weigh options and wrestle with difficult concepts, it pushes us to ask questions - and place greater weight on their answers."

It does not take a giant leap of imagination to consider this in health and social care contexts?

Margot Bloomstein, .net, July 2014, Issue 255, p. 42.

Friday, February 03, 2012

Drupal ScienceCamp Cambridge 20-21st Jan 2012

Two weeks ago Drupal ScienceCamp was a great success thanks to the organisers and sponsors. There were about 60 attendees with a European flavour too. Being a Science Park we had to circumvent the fence, the alternate access gates closed over the weekend. The three of us who left the hotel soon became six ... as we walked around to the very smart venue - Napp Pharmaceuticals Limited.

On the Saturday I attended sessions on responsive design, Drupal modules, Less CSS (at this point I wish I could have split in two Drupal search and Solr Wizardry had very positive comments), From flipcharts to Drupal Features, and Migration, upgrading and moving house. All very helpful.

Sunday was spontaneously self-organising. People offered to deliver sessions and meetings in a BoF - birds of a feather format, others requested the things they were seeking. Whether a sign of my time in Drupal [v. 4.7], or possibly Drupal's ever increasing diffusion or both; seven of us gathered around mental health and disability.
More on this to follow.  ...

Saturday, July 10, 2010

Drupal musings 7: HTML5, CSS3 ... & Mr Hodges meets Drupal

At Manchester airport in May I noticed Web Design Essentials (WDE). Reasons of cost £14.99 and weight meant it was put back on the news stand. The content was excellent! Back in the UK a week later, no sign of it in the supermarket. I found a copy this week at WH Smiths and made the 'investment' - a belated holiday treat.

This is gold mine of nuggets on HTML5, design - wireframes, user experience (UX), fonts and typography:

http://www.font-face.com/
http://fontdeck.com/


- personas, CSS3, jQuery and much more. Now I think about it UX has been around for quite a while, it's a sure sign of how web design has matured such that practitioners can and must focus on the experience. There's another blog post there contrasting UX in web design with UX in health services. Reading about the use of personas in design and planning for a site might also deserve a specific post. As WDE indicates there are companies dedicated to UX. I do not have that luxury and yet I do have to define my initial target audience and their anticipated experience.

The web design related listing I maintain at LINKS I (Intrapersonal) are being updated as a result of the leads in WDE.

Through the scheduling and poll services of Doodle (thanks Chris) and with the Drupal NW England list I'm checking on which day in the autumn - November - is best for a group of volunteers to help jump start the new site. Everything is sorted now for Drupalcon next month.

Tuesday, May 25, 2010

Curriculum design and the value of whitespace

The best websites are often variously described as clean, slick, easy to navigate and access. They are considered 'best' often as a consequence of appreciating the need for whitespace. This means of course that they are also minimalist, uncluttered, easier to style consistently and they often have plenty of free space. The Google site and resulting interface is a prime example, to the extent it has become a recognised brand characteristic.

The pressures on curricula almost preempts the phenomena of student cramming. Without careful planning and discipline curricula can be jammed so full that there is no slack, no whitespace.

As a result there is also no space to reflect (Clouder, 2009).

Reference:
Lynn Clouder (2009) Promotion of Reflective Learning, Teaching and Assessment through Curriculum Design, Occasional Paper 10, Connecting Reflective Learning, Teaching and Assessment, Edited by Helen Bulpitt and Mary Deane, Higher Education Academy. p.11.

Additional links:
Whitespace programming language

Sunday, April 27, 2008

Drupal tinkering - Salamander's in the sand

I keep thinking of drawing a line in the sand as to when the new Drupal site will go live, but then a curious clucking sound takes over and my arms flap uselessly at my sides. The image below is a screenshot using the Salamander theme for Drupal 6.2. As you can see I have not altered the themes default logo, or the colour scheme; but I'm starting to find my way around the menus at last.

I've started to add other users and as you can see have created a forum with topics and posts. The rail ticket image is neither transparent, nor exactly territorial in disposition. It should be possible to set a default vertical and horizontal spacing for images in the archived content. There is another choice to be made in which drop capitals format to adopt. Having read through jQuery in Action, it is time to revisit the book and really experiment.


Assuming there is a community out there - a series of forums on Hodges' model must be at the heart of the new site, but this begs the question of what tools would a community of Hodges' model users need? Drupal's content types can be extended, but how much effort (if any) should go into such resources? Should they be ready-rolled, or should the community identify the need, specify the requirements and produce the goods? Can an MSWord.doc h2cm template provide a start, or is a more adventurous seed required?

So far several people have used the model for their studies or in specific clinical areas. It makes sense then to try to produce a content type that can be configured by the user for these purposes. It makes even better sense to invite registered users to post their contributions. While I continue to piece the new site together, I must investigate the available Drupal modules and Open-EHR. I had heard of 'Open-air' before in passing and last week at Harrogate learned of it in more detail. I wonder what form and scope the archetypes take? Open-EHR may be far too sophisticated for our purposes, but now is a good time to check.

Sunday, April 20, 2008

Book: "Building Powerful and Robust Websites with Drupal 6" - review

David Mercer's Drupal: Creating Blogs, Forums, Portals, and Community Websites introduced me to Drupal 4.7. When I learned of a new Mercer title from Packt I offered to review Building Powerful and Robust Websites with Drupal 6. If you are impatient and read only the first and/or last para of things then to cut to the chase - if you are new to Drupal and content management systems you need this book. So, go and buy it now!

I've been learning Drupal on-and-off (as spare time allows) since last summer. Reading this latest Mercerian effort I've undoubtedly benefited from reading the Drupal 4.7 text. The 4.7 title definitely got me up and running as a Drupal novice, so this formula and style is familiar to me. There are some physical changes: the paper on this latest offering (my copy at least) has better contrast. I could not find the exact font details, but the print size is larger and so there are fewer words per line which naturally helps readability. Consequently, the 4.7 book's 267 pages translates to 362 pages as measured to the last page of the index.

As a Drupal newbie myself I've struggled due to:

  • The whole client-server set-up and creating a database driven community.
  • Drupal's likeness to an iceberg:
    • what you can see - themes, modules, users, forums
    • what you can't see the MySQL, PHP, CSS, server, template and other files...
    • Oh yes, and the things that are on the water-line - blocks, menus, 'nodes and content'
  • Drupal files and folder structure
    • The location of core Drupal elements vs contributed elements (and your content)
  • Security, access and permissions
    • managing users
  • Upgrading and configuration
    • Drupal is very much a work-in-progress
  • Customisation - themes, styles, being 'original' - extending Drupal.
The first fifty pages provide an introduction to Drupal, how it all started with its creator Dries Buytaert; plus installing server software and Drupal itself. Several pictures of the Drupal website highlight this as a pivotal resource with its forums and great sense of community. Mercer had me wondering that you may not be pushing the envelope if you don't need help at some stage.

On page 32 'The Drupal Environment' a sentence states that readers '... might well prefer to dive straight in and make modifications to your Drupal site.' This seems a bit premature to me, as six pages later we are concerned with obtaining and installing Drupal. As this is my first book review the adopted convention is a stolen sentence or two from Packt's summary of the book, with my thoughts:

Chapter 1 introduces you to the world of Drupal and looks at where Drupal comes from, where it’s going, and what it can offer you. - The Drupal community is an invaluable resource and in addition to reading and struggling I've attended a user group, were everyone has something to offer and there is much enthusiasm and skills on tap. So Mercer highlights the web and forums as a source of support and might possibly have made more (even without specific details) of the number of local Drupal user groups and events. Nonetheless, this thorough introduction is capped off with an explanation about Drupal's status as an open source project and the licence. This more than anything explains Drupal's dynamic credentials. Guidance is provided here on building a website - including 'phone a friend' - and don't forget paper and pencil for planning and developing ideas.

Chapter 2 deals with how to get everything you need up and running on a development machine and also briefly looks at how all the requisite technologies gel together to produce a working Drupal site. ... - Going for a combined package, I tried ApacheTriad and XAMPP before settling on WAMP5 for the Apache server, MySQL and PHP5 software. The thing is don't give up. I installed-scratched Drupal a couple of times; my excuse - I'd give it some time ... and then leave it alone. ... Like many things in life, you need to devote and invest time on which to build your knowledge and skills (even a 10-15 minute session can help). This chapter is very informative whichever server approach you adopt. As the author advises - keep that admin password safe! Mercer's task here must be helped I believe by the Drupal 6 install process. Although not yet 'automatic' it has been greatly improved.

Chapter 3 sees us adding functionality to the newly created site. ... - At this point David Mercer had me wondering: I've heard that a lot of people try Drupal and other CMSs and give up. If there were CMS exit questionnaires what would they reveal? A DHTML menu module is used as a module example and needing to find this again it is there in the comprehensive index. Blocks and menus take some getting used to, well for me anyway. It is not necessarily that they are very complex - they are just cussed on 1st, 2nd, even 3rd acquaintance. If you forget to activate a block, a menu will not show. There are graphic handles for drag-and-drop operations within menus, which helped me to finally grasp things. Mercer's advice to check through the modules that are available for your version is well worth the effort. Yes, the number of modules can be overwhelming, but the diversity and scope provide a reason to forge on and there's more to follow.

Chapter 4 looks at the most general settings that all Drupal administrators need to contend with. ... - This chapter could be titled 'chicken or egg', since you need to understand the functionality of Drupal in order to commit to developing your site. There are a lot of options for site configuration and again it's good advice to take the time and check out the available settings, displayed here in pictures with descriptions. Try to appreciate early on the role of clean urls (and path aliases p.325); using two browser windows can help too.

Chapter 5 concerns itself with the topic of access control. ... - This chapter I will certainly be re-reading. It has prompted me to realise that for my new site a forum is vital. Although I've some static content to archive, this would be a waste of Drupal's power. Here roles are covered, with emphasis on planning and creating an access policy p.116. Throughout the book you are reminded about only giving users the permissions they need to perform task x, y or z and NO more. Mercer points out that what roles you have and what your site can 'deliver' overall is also dependent on administration. Are you a one-admin band or will you have some help? It is always difficult to anticipate the future, hence the need to plan an access foundation upon which you can build.

Chapter 6 gets to the heart of the matter by beginning the book's coverage on content. ... - This chapter sheds light blog entries, book pages, forum topics and pages with these content types just the beginning. The learning here is not just the 'what', but 'how' to administer content, plus distinguishing (or not) between nodes and content. When you are working on your site and styles remember the 'input format' section of this chapter - again really useful. I wondered why my drop capitals and table effects were not showing. It was just that some HTML tags were not allowed through the filter.

Throughout the book the work flow approach helps instill confidence by hand-holding step-by-step and yet also encouraging you to experiment alone. Another insight for me here is the wider potential of Drupal's RSS aggregator. You also realise how quick the publishing turn-around is these days, with the pictures of the feed aggregator dated 02/05/2008. p.166. I have in mind a collaborative book on Hodges' model, so the five pages devoted to the book content type proved essential reading. There are graphic handles for drag-and-drop operations within books, in addition to the menus as mentioned previously.

Chapter 7 gives you the edge when it comes to creating engaging and dynamic content. While this chapter doesn't require you to be an expert in HTML, PHP, and CSS it does introduce you to the basics and shows how, with a little knowledge, extremely powerful and professional content can be created. ... - There are some Drupal pearls here: taxonomy, the content construction kit (CCK) and HTML, PHP and content posting. There's even a brief intro to HTML. Time also for considered reading with descriptions of terms, vocabularies, thesauri and related Drupal elements. With some awareness of clinical terminologies and having read this and other Drupal sources perhaps I'm underestimating the power of Drupal?

The CCK section has me a little puzzled. My next task is to install CCK in Drupal 6.2 as Mercer suggests to see if it works. At the time of writing this review though the Drupal site states they are creating a preliminary, development version [of CCK] for D6 soon. As Mercer acknowledges the CCK is dependent on another module called Views, which is still not yet ready for version 6. In a way something like this is to be expected of a book that is first off the blocks. Mercer still sets the CCK up nicely though, as I'm tantalised by the possibilities, especially when combined with Views as I saw demonstrated at the NW England Drupal user group.

Chapter 8 gives you a run down of how attractive, functional interfaces are created in Drupal through the use of themes. ... - Time to get the hands dirty; first though as with the modules I've followed Mercer's advice and checked through the available themes. You could be excused for believing it is a waste of time poring over all the themes (although not that many are available for D6 as yet). On the other hand let physics work for you and (like me) you will gravitate towards a couple of themes. If bones are essential for structure, support and locomotion, then chapters 8 & 9 provide the meat of the book and Drupal.

Chapter 9 really adds the icing on the cake by looking at a host of more advanced topics. From dynamic and responsive content using JavaScript and native jQuery support to supporting opened and implementing actions and triggers, you learn to enhance your website and add that something special. ... - I blame Mercer 4.7 (plus some exciting demos) for prompting me to invest in a specific jQuery book. (The user group directed me to the seminal Drupal book - the 'Pro' title.) jQuery accounts for a brief but very effective five pages, that I hope to incorporate into my test site efforts very soon. Drupal 6 has seen a major emphasis on internationalization and localisation. This is very welcome functionality for me, that Mercer serves over about 15 pages. My new website must be global in reach, Drupal can deliver and Mercer shows the way. Translation files are still in the future for this Drupal student, but for languages, cacheing, throttling and performance I know where to go for help. OPENID could be a real scoop for user uptake and is covered in just over four pages and begs further investigation. The book is peppered throughout with urls and tips for more resources and reading.

Chapter 10 takes a pragmatic look at the type of tasks in which you will need to be proficient in order to successfully run and maintain a Drupal site. ... - Having backed up the database and run cron jobs manually, there is one major thing I've still to do and that is the non-trivial task of upgrading. The single appendix deals with deployment.

I've a lot yet to prove in terms of learning Drupal and demonstrating proficiency (a deployed website would help!). I'm convinced though that Mr Mercer is helping me move forward with this latest very instructive Drupal book. Significantly there is quite a team behind this title. I wholly endorse this summary from the Packt site:
Written in the same style as the original Drupal title, this book is a pragmatic look at the steps necessary to get a website up and running. Drawing on years of writing experience, David Mercer utilizes a friendly, engaging style that is both clear and concise – perfect for the Drupal newbie.

Good luck - I hope this review helps!

(Many thanks to Packt Publishing for the book copy and acknowledging their support of my blog: Welcome to the QUAD).

Sunday, February 17, 2008

Drupal 6 themes and tools

Of the themes I have downloaded that work with Drupal 6 Four Seasons and Bluebreeze look worth pursuing. Transferring over the style sheet used in Drupal 5 with Denver caused quite a few problems as expected. Commenting out some of the global styles one-by-one and noting the effects can't avoid the sense of work to be done. Here is D-6 Bluebreeze:

BlueBreeze theme
In the above image, the panel on the left is one of the modules downloaded and enabled. There are no more than two users at present, so I'll disable this for future use. The fixed-width version of Bluebreeze may be needed as off to the right there's yet another tab - 'Book'. I'm going to bring over the draft glossary page, it might prompt me to add some terms.

One of the tools that should prove itself has placed a tick box 'Themer info' in the lower left corner of the screen as illustrated below.

Themer InfoWhen activated you:

Click on any element to see information about the Drupal theme function or template that created it.

There's a problem though when I try to access 'modules' -

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 347727 bytes) in C:\....module on line 1291.

Mmmm.

Monday, February 11, 2008

Box & Grid fonts plus Wicker People - blog banner.

As regular readers will be aware I've been after a decent banner for W2tQ.

I came across this site specialising in free fonts:

- and putting this resource together with a photo taken locally this is the result:


I do hope the Celtic influence does not scare anyone, but Hodges' model is a conceptual framework...

Sunday, January 27, 2008

Reflections on Drupal Denver theme

Customising Drupal themes is a central skill in the Drupal and other communities. The number of contributed and updated themes are a great testimony to the specific expertise people develop. In tackling a project Drupal developers put a team together across the spectrum of required skills and this includes someone proficient with themes.

I want the new site to look different and reflect the unique structure and content of Hodges' model, but I don't want to spend all my time grinding a mirror for the telescope. I want to be out there observing - even if that's just with binoculars and the naked eye.

I've found the Denver theme quite appealing in its simplicity and functionality:


If you click&check the above image in detail you'll see I need to sort the banner (transparent?) another image would be preferred. There are several menus too: the tabs, left and right side bars plus breadcrumb trails. I've finally defined a new site within Dreamweaver [MX], so I can also focus on the style sheet(s).

Wouldn't you know it - I just checked and Denver isn't currently listed as a Drupal 6 theme. Forever a realist - this is always going to be an issue so ....

Tuesday, December 18, 2007

HTML -> XHTML & accessibility in my hands

My copy of Jeremy Keith's "DOM Scripting: Web Design with JavaScript and the Document Object Model” was published in 2005. Sat on the shelf for a year or so (don't let the library list fool you), finally reading it cover2cover.

I've developed bad habits over the past year or so, especially when updating the four links pages (no small task). Sometimes I'm using upper case HTML tags, on other occasions lower case. For HTML that's no problem, but Keith advises that if you have the future of the web in mind XHTML insists that all tags must be closed and tags plus attributes must be typed in lower case (p.149).

So, the revisions for the Drupal site and on the 'old' site will be XHTML compliant from now on; that's a lot of tags to change.

Keith's brilliant book also describes step-by-step Javascript functions, e.g., to list abbreviations and (as I mentioned recently) making use of ID and CLASS. The potential of using the DOM to create content is going to have me day dreaming (but not while I'm driving).

Keith has woke me up regards my accessibility requirement too. I knew I was missing something! Here I am wondering about what Drupal modules can do for me, but where have I been? I hadn't come across 'accesskey' before (p.171). Well no time like the present! Just what I (and future visitors!) need. My apologies to visitors in need of keyboard links, these will be provided in future.

Monday, October 29, 2007

Drupal: steep curve - still climbing ....

Drupal tinkering
Just trying to get an idea of what Drupal can do. It really is powerful (in the right hands!). There's no text as yet - or what is there - is not formatted. Still not sure about the content beyond the Archive comprising Brian's course notes, my intro and (updated) reflections; the Book and the h2cm Chronology.

Weird that A, B, C ... just wish it was easier.

The book may need to wait, but is I believe a great global project - wish I were a midwife....