Dreamweaver is anything but dreamy

 While, practicing what I have already learned about HTML and CSS gave me some understanding how Dreamweaver works, there was still a lot to figure out. If I wanted to take full advantage of the software there was more to be done. I used some tutorials again, those two to be precise, but felt like I am already running a bit behind with that project, so I chose specific segments to watch and opted out from going through their full content. It was particularly useful to know more about the interface of the programme, how to take advantage of it being quite intuitive and pointing out my mistakes. Most of all it introduced me to Bootstrap. I think this is the moment, when I feel confident enough about what I have already learned, to explore the idea of using Bootstrap and Java script in my website.



Despite the name the programme is anything but dreamy. It has a lot of features that can be really useful, but also can behave in a really unpredictable way, if you do not dedicate some time to learn how to properly use it. I had issues with duplicated sheets, with the programme creating links for me I did not understand, with constantly forgetting to save changes and then wondering why nothing is changing in my practice files. The split view was fun at first, but the more code you put, the more it is actually annoying because you get limited view of what you are doing. If you are not careful you might press some of the suggestions the programme gives you by mistake and then to wonder why everything changed. In other words - you need to pay a lot of attention at every step. On the other hand there are things I really liked. For example - when you are working on your CSS file elsewhere you can end up connecting the wrong element or no element as you wrote it wrong - not here, as Dreamweaver only gives you the options of elements that are in your source code. So far I am using it only on my exercise files and have not yet started the actual website, but getting to know the programme is something I expect to really help me in the process of completing this assignment. I already found that its Live View and Design View can be different from what a browser interprets from your code after. So, I will have to find a way around that in order to be able to see how my pages are actually looking. It is also too much at times, so many functions I probably will not use. But I am really glad I started with HTML and CSS leaning. As intuitive as Dreamweaver is, you might end up taking advantage of all the suggestion it makes and, if the end result is not a good one, your only option is to start from scratch. I am pretty sure that I will be able to spot my mistakes now, being aware how the programme language works. At this point I feel that I have done what I can to improve my technical abilities, and it is time to finally pay more attention to the concept of my website. 

Comments

Post a Comment

Popular posts from this blog

Flowcharts, Wireframes and Mood board

Image
In preparation to make my Prezi presentation, that will give an idea how I am approaching this, what I am going for and how I plan to execute it, I decided to start with my flowchart, wireframes and mood board. I am using Adobe XD for that and, more or less, this part of my project is connected with my visual and content design research. I think that going through the whole process of creating those is making this one thing certain  - this is just a start. I should not expect to be able to do exactly what I will set out to do in the presentation, but if I do not set out any framework, within which I will work, then I will be all over the place. When I am doing something that requires a method, no direction is my worst enemy. Wireframes are how your pages will look like, the flowchart is how it all comes together in a website. I already have an idea, in terms of functionality, so this was kind of fun to do. I am finally able to visualise where I am going with this.   At this po...
Read more

Technical Process - how it all came together (Part I)

Image
First of all I need to make a note of something - my browser has never been abused to this extend with searches that start with 'How to...' ! There are elements that need including in this website and I had to learn how to do that. Most of the answers I found in  W3schools , but I used other sources as well. Anywhere they had an answer to my question really. I started by designing my Index page. I already knew that I did not want too much there - navigation bar, some info about me and my logo. After going through Boostrap platforms, trying to figure out how to start, I saw this web design and decided I will use some bits and pieces from it. Just to get me started and to have some frame to work with, which I can always change after to fit my vision, but also my technical abilities. First thing I realised - the split function of Dreamweaver that allows you to see what you are doing is good, but only when you are exercising. Once I started doing this I switched to code mode, as o...
Read more

Image, Text and (not) Music

Some time ago I read Roland Barthes's Image-Music-Text and I loved it. Semiotics and how our reality is created within societies and cultural norms has been something I was interested in long before I came to University. So I started thinking - what my website will be trying to say about me and about art? How to optimise the use of images and text, so it conveys a message, it creates a context? I have to admit that putting an abstract together with technology can be confusing, but big part of content design is how you engage with the users. At this point there is one thing that is clear - my website will not be text heavy, yet I will try to convey my passion for modern and contemporary art through at least some text, and showcase it with images.  From the start I had the idea of the "My life in Exhibitions" page, that I will populate with images from the best exhibitions I visited in the last two years. Text, that was different story..We all have different ways of positio...
Read more