I love Bootstrap which is a wonderful framework to create a modern and mobile friendly website. But it is a little too large and excessive to me. Currently I am trying to create some small websites. Would I get better off by writing my own CSS codes for the mobile friendly purpose?
It's convenience for the visitor vs the developer.
Using the Bootstrap framework will cause the web developer to save time at the inconvenience of a slower site.
Remember, no matter how big the site, you're probably not even going to be using all of the functions.
Related
I want to make a mobile friendly version of my website, but I have this dilemma.
What is better? Use CSS3 Media Queries to make main website responsive or detect if user is using a mobile and redirect to a new one (for example m.example.com).
This really is depending upon what kind of website you are having. Your decision will not only affect the way your site is presenting, but also how you would deliver business strategies (if it's a commercial thing).
Responsive design will work just great with simple websites that doesn't really need too many detailed experiences. Company profiles, or landing pages will fit best with RWD.
Once you're building much more complicated application, you might need to re-think how the user will interact with even the tiniest part of it. Note that using RWD often require greedier resources compared to a dedicated mobile site. If you're dealing with e-commerce, social media, or some other mature applications, a mobile version is a way to go.
Hi I am developing a website with multiple pages. I am a beginner, coding is still a challenge for me, but my main hardship is designing my website. Visual studio is very not intuitive when it comes to designing websites, and sometimes you feel (when you try to design) like you work while tied in a straightjacket. I am used to dragging stuff around when designing, but this doesn't work with websites. There are a lot of website templates, but is there any which work with asp.net? And how do you integrate them while working in visual studio? Any help?
You don't need any special templates to work with ASP.Net. Integrating a template works the exact same way as it would if you are designing a site from scratch.
Find out your major pieces that are in every page (or groups of pages) and create your master pages that will provide consistent layout for those pages.
Forget about dragging and dropping and pixel design locations of a regular desktop app, it's not going to work that way.
Start with a framework such as Bootstrap, or a template based on Bootstrap. It's extremely well documented, works cross-platform, and there are plenty of tutorials out there on using it.
Visual Studio works pretty much like any other web design tool does. You're just running into exactly how things have been done for well over a decade now. Tools get better, but the web is an entirely different experience that requires entirely different ways of doing things.
You can easily templates or frameworks into your site. You can add styling to form fields, buttons, etc. easily through the CSS of the template.
Take a look at Bootstrap to get an idea of how you can style elements and understand the layout tricks that can be accomplished with responsive design.
I have an asp.net website, it contains database calls etc
Whats the best way of taking an existing asp.net website and making it look good in mobile and tablet devices?
I have done some research but there seems to be so many options eg lessframework.com, jquerymobile etc
I havent used mvc before but a few people say to use mvc + jquerymobile
any help would be muchly appreciated
There is no magic bullet that will instantly convert your website to mobile. In fact without knowing the specifics of your website it would be hard to recommend a good fit for your situation since the tools you mention like MVC, JQMobile, etc. would be used in one case or another. With the question as you have posed it you will get personal opinion and there are millions of us with opinions... here's mine:
I would recommend not building a mobile specific website like mobile.website.com but rather look into responsive design where your website and the underlying data structs remain the same but your view changes depending on screen real-estate. Bootstrap or HTML5 Boilerplate or any number of design frameworks will help you get started. You just need to figure out a design that fits your websites functionality.
I use MVC + HTML5 Boilerplate (I love Razor) for most of my new projects but sometimes even it has too much overhead so I just start from scratch (multiple PSD's, convert to HTML in Dreamweaver, apply logic with MVC & client side scripting) but that is something you will have to decide on a project by project basis.
We've been using html5 boilerplate with blueprint css for the last couple of projects. With some tweaks, we were able to make blueprint "responsive". We like blueprint, but are concerned it may be a bit "dated", from what little we know about gui trends. We've been hearing a lot of buzz about twitter bootstrap 2.0. From what we saw, we liked bootstrap's simplicity and the fact that it provides responsiveness out of the box. However, we're concerned that it's too heavy-duty for our purposes.
So, what I'm wondering is:
We know the look of bootstrap can be customized without limit. But, is it more work than it's worth
to completely overhaul the default look and feel of the framework? (Our designers will never design web apps/sites based on bootstrap).
Also, I'd love to hear about what experiences, in general, other people have had with switching from blueprint to bootstrap.
My 2 cents:
I am a fan of twitter bootstrap. I've used it for an internal application at work. I basically used it to convert a ordinary looking application to a responsive application with a much needed user-friendly user interface.
I did make some customisations to the default twitter bootstrap css library. I did not find this particularly difficult, and neither should a developer/designer if they know their way around html/css/browser web dev tool.
I think it is designed well enough for a developer/designer to still have some serious gains even after making their customisations.
Easy question. I used to develop websites back in the days of "classic" ASP, and when I'm asked to do a quick and dirty website for family or friends now, I still resort to direct HTML/ASP and some basic CSS and Javascript - I can get the sites up pretty quickly this way. However, I've had a few requests to design and develop some sites for pay, and thought I should catch up on my web skills. I have been using .NET 3.5, XAML/WPF, etc. for Windows apps, so I'm up on .NET, I'm just behind on the web end.
To the question: If I want to design/code a site that looks identical on all (at least somewhat recent) browsers and platforms, should I be using ASP.NET and AJAX? There might be a little database activity on the site, but not much, so I don't need an enterprise level, multi-tier extendable architecture... just something that looks good and works on multiple platforms without having to code all variations for each browser. After looking at all the ASP.NET books at the bookstore, it seems they all focus mostly on data and postback stuff. Is it still a legit option to use some basic, boring html and javascript with some Flash embedded where needed?
Let me know if I need to clarify the question. Thanks for your advice in advance!
Your question is more loaded than you think, but let me try to address a few points that I think are relevant.
First, how a site looks is almost completely dependent on the HTML/CSS you use and how you code the front end of the site and only slightly dependent on the server technology. So if you want your site to function across browsers and platforms, learn to code following web standards, with semantic markup. (Search on those terms for more info).
Also, ASP.NET comes in two flavors now: ASP.NET MVC and normal ASP.NET. I highly recommend, if you are going to get into ASP.NET, that you follow the MVC platform. It closely follows similar technologies (like Ruby on Rails) and will make the transition to other MVC platforms easier on you. Also, the MVC platform doesn't try to output as much pre-made HTML as straight ASP.NET will when you use their "drag and drop" controls.
Secondly, it really depends on the sites you are building, but straight JS (or JS + jQuery), CSS, and HTML -- and please don't use Flash unless you are embedding a video -- will actually work for a number of basic sites. If you need some things to happen on the server, PHP makes for a great platform. If you are working with advanced database access, and program flow, and since you are already familiar with .NET, then stick with it... MS has some great tools and resources to help you out.
Finally, a lot of developers use a favorite CMS or blogging platform as the backend of simple sites that still need the ability to manage the content easily. Expression Engine (CMS) and WordPress (Blog/Lite-CMS) are often used (both PHP based) but there are tons out there.
Good luck stepping up your game!
I would recommend learning jQuery. This will give you a browser independent abstraction for your JavaScript.
ASP.NET controls will render it's controls in a browser independent way, but that doesn't mean your site will automagically be browser independent. You still need to know how elements are rendered differently in different browsers.
I'd also recommend using a CSS Reset sheet as a starting point for your CSS.
All in all, if you've been developing old school ASP, you'll probably really love ASP.NET as it will save you a lot of time and looping. You may want to jump right in to ASP.NET MVC too.
To the root of your question, I'd learn ASP.NET if you're doing anything more than a simple brochure site. If you have .NET experience, and classic web development experience, then learning ASP.NET is not going to be a big hurdle and will be well worth the effort.
I agree with Aaron Daniels' answer about learning jQuery. jQuery helps a lot with cross-browser compatibility in JavaScript and some CSS-based effects.
However, you should also look into ensuring your site uses well-formed, valid HTML, and doesn't use too many CSS 2+ features. This should ensure that your site is standards compliant, which will mean it will play well with Firefox, Safari, Opera, and even later versions of IE to an extent. You will still need to do manual tweaking for IE - it's been too broken for too long for MS to be able to fix it properly in one go - so look into conditional comments for applying a separate stylesheet for IE users.
AJAX is a handy technology for "desktopifying" your web app. It provides a mechanism for asynchronous callbacks to the web server, so you can pass data to and fro without reloading the page in the browser window. This is how the voting buttons work on StackOverflow, for example.
Lastly, ASP.NET doesn't really have much effect on the end user's experience in terms of the look and feel of the site. It is a server technology that provides for writing complex applications to be delivered over the web to a browser. Having said that, MS have put in some extra goodies to make working with AJAX a little easier.
Hope that helps!