“专业人士”如何做到这一点?设计和编码网站?

发布于 2024-09-12 18:38:31 字数 286 浏览 7 评论 0原文

大多数现代“专业”网页设计师如何开始/设计/编码网站?

我意识到技术的范围和差异很大,我只是在寻找一些可靠的、可靠的策略或方法。

例如,“我知道大多数人都会与客户一起绘制一个粗略的设计,然后进入 Photoshop 并创建它,然后将其切片,然后手动编码......”等等。显然,答案不一定是这样的通用的。

我知道编码员并不总是设计师,但我想听听这两个领域的典型方法。

我现在正在学习网页设计和编码,我的主要问题是了解各个部分,而不是所有内容的总和——不知道如何“应该”创建一个成熟的多页面网站。

How do most modern "pro" web designers go about starting/designing/coding a site?

I realize that techniques will range and differ drastically, I'm just looking for some solid, relied-on tactics or approaches.

For example, "I know most draw out a rough design with the client, then go into photoshop and create it, then slice it up, then code it by hand..." etc. Obviously an answer doesn't have to be this generic.

I know coders aren't always the designers, but I'd like to hear typical approaches from both spectrums.

I'm learning web design and coding right now, and my main problem is knowing the parts, but not the sum of everything -- not knowing how one is "supposed" to go about creating a full fledged, multi-paged site.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

野侃 2024-09-19 18:38:31

这是一个非常广泛的问题,没有简单明了的答案。然而,你走在正确的轨道上。一切都以用户开始和结束……他们的目标是什么以及他们如何实现目标?他们应该完成任务还是查找信息?

  • 每个设计过程都从策略开始。问问自己网站的目的是什么以及用户的需求是什么。如果没有明确的战略,项目更有可能失败。
  • 其次,定义网站的范围。网站有哪些内容要求和功能规范。
  • 继续讨论网站的结构。我们现在关注信息架构(标签、导航、组织和搜索)和交互设计。市场上有各种技术和工具来了解用户如何将标签与信息相关联,例如导航等。可以在早期阶段执行初始用户测试,以验证项目是否走在正确的轨道上。
  • 完成上述所有操作后,就可以开始在纸上绘制站点了。某些元素将在哪里,以及用户将如何与网站交互。您还可以使用 Balsamiq Mockup 等绘图工具来构建骨架
  • 最后,您实现表面;颜色、图像和真正的编码开始。进行可视化,并希望进行更多的用户测试。

但请记住,设计并不是一个直接的过程。您必须迭代每个设计步骤,在这些层之间来回移动,直到获得良好的结果。

最后,针对目标受众对网站进行一些测试。用户测试使一切变得不同。

参考资料和更多内容请阅读:Jesse James Garrett:用户体验的要素

This is a very wide question, not having a simple and clear answer. However, you are on the right track. It all starts and ends with the users... what are their goals and how are they expected to reach their goal? Should they complete tasks or find information?

  • Every design process start by a strategy. Ask yourself what is the purpose of the site and what are the user needs. Without a clear strategy, projects are more likely to fail.
  • Second, you define the scope of the site. Which content requrements and functional specification do the site have.
  • Moving on to the structure of the site. We are now concerned with Information Architecture (Labeling, Navigation, Organization and Search) and Interaction Design. On the market there are various techniques and tools to find out how user relate labels to information, like to navigate and so on. The initial user tests can be performed in this early stage to verify that the project is on the right track.
  • When all the above have been done, its time to start draw the site on a piece of paper. Where will certain elements be, and how will users interact with the site. You can also use a drawing tool like Balsamiq Mockup to build the skeleton.
  • Last, you implement the surface; colors, images and the real coding begins. Visualization takes place, and hopefully more user tests.

Remember though, design isn't a straight forward process. You have to iterate through every design step, moving back and forward between these layers, until you have a good result.

Finally, do some tests of the site targeting the intended audience. User tests make all the difference.

Reference and more to read: Jesse James Garrett: The Elements of User Experience.

思念绕指尖 2024-09-19 18:38:31

我喜欢自下而上地设计我的网站/应用程序。也就是说,我首先分析问题域并将其转换为数据模型(例如 SQL 数据库)。然后我在其之上构建一个数据访问层和业务逻辑,然后是一些表示逻辑(通常是一些通用代码,可以调用业务逻辑函数并通过某种模板泵送纯数据),最后是定义外观和感觉。

用于实际的图形设计;要么我自己做,在这种情况下我倾向于直接编写 HTML 和 CSS,要么由其他人为我做,提供静态 HTML,我将其转换为模板。

I like to design my web sites / applications bottom-up. That is, I start by analyzing the problem domain and translating it into a data model (e.g. an SQL database). Then I build a data access layer and business logic on top of that, then some presentation logic (typically some generic code that can call business logic functions and pump plain data through some sort of template), and finally the templates and stylesheets that define the look and feel.

For the actual graphics design; either I do it myself, in which case I tend to write HTML and CSS directly, or someone else does it for me, delivering static HTML which I turn into templates.

和我恋爱吧 2024-09-19 18:38:31

网站和网络应用程序之间有天壤之别。许多网站客户并不真正知道他们想说什么,他们只是想在网络上以某种形式存在。找出要放什么内容通常是困难的部分。

因此,对于网站,我从美观开始。我在 Photoshop 中制作了一个模型,只有在获得批准后,我才开始用纯 html 和 css 对其进行编码。这将制作第二个模型,然后再次将其放置在客户面前。然后我开始编写后面的任何逻辑(如果需要,因为通常静态就足够了)。

对于网络应用程序来说,情况通常相反。通常我并不真正负责那里的外观,所以我们从逻辑域和单元测试开始。正确测试后端后,我们开始将前端固定在其上。在这些应用程序中,美观通常让位于功能,因此模拟不太重要(至少在我的项目上)。无论如何,除了标头之外,通常都是面板、按钮和组合框。

再说一遍,我不是专业设计师。

There's a world of difference between a website and a web-application. A lot of website clients don't really know what they want to say, they just want to have some form of presence on the web. Finding out what content to put on there is usually the hard part.

So for the website I start with the aesthetics. I make a mockup in photoshop, and only when that has been approved I start coding it in plain html and css. This makes the second mockup, which is then laid before the client again. Then I start writing any logic behind (if needed, since often, static is enough).

For web-apps it's often the other way around. Usually I'm not really in charge of the looks there, so we start with the logic domain and unit testing. After the backend is properly tested we start bolting the front-end on it. On these apps, aesthetics usually take a back seat to functionality, so mocking is less important (on my projects at least). It's usually all panels and buttons and comboboxes anyway, except for the masthead.

Then again, I'm not a pro designer.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文