As an exercise on Front-End Development, The UI Team took a screenshot from instagram.com and treated it as if it were a design mockup.
We then proceed to deconstruct its Structure and Skeleton (Elements of UX) thru Information Architecture, Interaction Design, Information Design. The knowledge that arose in this deconstruction was used in building the HTML and CSS.
We, as Visual Designers, have experienced how time-consuming it was to build the Front-End of a design mockup basing only on a simple image.
The Design Handoff warrants to have more than the Brand Guidelines, Style Guide. It must also have some form of Information Architecture and Interaction Diagram that could greatly make Front-End Development faster.
HTML could accommodate Intentions Oriented Programming (IOP).
IOP is based on intentions rather than constructs.
Code could be validated but a deeper level and meaning depends on the intentions of the programmer.
After creating your first site under a Main Site, preview it and you will see icky defaults.
Here’s a list of what to setup so you would be on your way blogging:
- Week Starts On
- Permalink (Post Name)
- Appearance > Customize
- Header Image (hide)
- Posts > Categories
- Change “Uncategorized” to “Updates”
- Also update the slug
- Pages > All Pages
- Change “Sample Page” to “About”
- Also update the slug
- Posts > All Posts
- You could either change the Hello World post into your own welcome message or completely delete it.
Check your site again to see if everything’s looking good.
Bet you also hated this:
That looks redundant. No need to put up with it.
Here’s how to remove the “blog” slug from the permalink of your main site in a WordPress Multisite sub-directory installation:
First, Edit Permalink
- Go to Network Admin > Sites
- Click “Edit” on the Main Site (don’t click the actual name of the Main Site)
- On the Edit Site page, go to the Settings tab
- Look for the section of Permalink Structure
- Remove “/blog”
- Save Changes, of course
Last, Refresh Permalink
- Now go to the Dashboard of your Main Site
- Go to Settings > Permalink (this section is different from the first step)
- Choose Custom Structure and in the field, enter “/%postname%/”
- Again, Save Changes
That will refresh your permalink structure and in the last step, the permalink will probably revert back to Post Name instead of Custom Structure (although they are the same using”/%postname%/”).
Go to your site and check if the index and post pages are working properly.
In designing the user interface (UI) of an app, it is common to start with the design of the populated state of the UI. As designers, we envision perfect scenarios, common flows, and predictable results. This, understandably, contains the bulk of work a designer has to face. It contains all sorts of issues that need to be addressed.
In turn, we might neglect designing for the different states of the component or the whole system that we are designing.
In general, here are the different states a component might be in:
I am currently making a curriculum for the basics of HTML and CSS.
Revisiting CSS Levels, I have written in the past about it:
The important thing to remember is to pattern it after the Levels of HTML wherein we must begin with Accessibility and Usability in mind.
And from there on, we build towards Visual Design.
Using this as basis, one could argue that Colors and Typography are “nice-to-haves”.
Can your design stand in black and white?
Can your design stand in a serif font?
Yes, it should.
I categorize <a> into two: Links and Actions.
Links will take you to another location, mostly for information while Actions could also do the same but with a more targeted purpose.
Links can be left alone in CSS – because they are buried in paragraphs or sitting beside other texts. Actions require styles that will enhance their usability – like padding to increase its active area (easier to click).
Does the HTML markup of your website has an accessibility function in the form of “Skip to Content”? If yes, then you would notice that it is located at the topmost of the markup. This is as such in order to make it the first focus when using keyboard to navigate.
Now you may ask, “Shouldn’t the document title be at the topmost of the document?”
Not when you put this accessibility function into the context of its intended use. The user, upon arriving at your website might have come from a link or have typed a URL into the web browser. That could’ve acted as the document title that ensures the user where s/he is.
The second part of this context is the user being able to go directly to the content – skipping every element that isn’t part of his or her purpose for visiting the website.