Advice on what path to choose for a website [closed] - content-management-system

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
A friend has asked me to make a website for him, for a games arcade he runs. It's an extremely simple website so no big deal.
The thing is I'm not quite sure how to approach it, I haven't worked on sites in a while. It would probably be easiest for me to create the site entirely myself, a few pages, css and probably a bit of javascript. But then I thought what if he wants to change things himself in the future, so I should maybe use a cms like wordpress or drupal. The last cms I used was nopcommerce about 2 years ago so I'm not really up to speed with them and themes etc.
Back in uni we were making websites with xml, which sounds ideal as I could create pages that would remain unchanged then use xml for arcade machines and news updates which he could edit himself. But that was a few years ago, is that how things are done nowadays?
Apologies for sounding so stupid but I'd like to get into web design again and I just want the opinion of someone with a bit of experience as to how they would go forward with this so I can do things properly.
Thanks!

I found WordPress ok for smaller sites.
Things evolve quickly around the web and you would probably benefit from the large collection of available templates.

Use Wordpress. It's really easy to setup and you can find a lot of free plugins and themes to create a web site with professional aesthetic and basic functionality. Having your information in a database and the modularity of the product makes easy to scale to a bigger site later if it is needed.

Related

I was given a serverless app to work on at work, where to start as a noob? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
avoiding the obvious answer, "Maybe I shouldn't have been given this to work on."
Let's just assume I was given this as a complex 'test of my abilities to learn on the job'.
The app is using serverless framework and I understand the basics of the structure using AWS and where certain things go etc, but I am not used to the structure of the app i was given.
I have a folder for backend, app, and one for 'graph'. I would just like to know where to start? Is the suggested route to user 'serverless-offline' or being that I didn't design this app, should I go straight to plugging things into my AWS, and get it running that way? I know this is kind of a noob question, and regardless I'm just going to go ahead and start playing around with the two options, but I do have a small window of time to figure out how to get this running in a 'Dev' environment so I can give a quote on adding some new React things to the app.
Are you working for a consulting company that advertised you as an "expert" to a customer where you actually have a severe knowledge gap to even approach the project you've been put on?
If yes, you aren't going to get much more information here in a reasonable sized answer than you can easily find using a web search. In fact, your question is so vague that I personally think it's not answerable at all. So, get searching on your own, hopefully you can figure out enough stuff by the deadline that you/your company can "fake it until you make it".
If not, and you are an employee in a normal company, you should have some sort of knowledge transfer process in place where someone who is familiar with the application would tell you at least an overview of how it works and how to approach it for basic changes. Unless this person left the company and now there is nobody in house with the needed knowledge, which is your boss's/company's problem and - if they are a good company - they should give you a reasonable amount of time to figure out all of this stuff the hard way, in which case the answer is - again - get searching the web.

Pros and cons of WordPress vs. own PHP Framework [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have a website build in own php framework, complete with an elaborate product catalogue and cms system. Now I would like to add a blog and I wanted others' opinions on whether to keep using the framework and develop it as fully integrated with existing website and cms or if I should use wordpress. I am leaning towards the first option but was wondering if I'm not missing something important about wordpress that should sway me.
I have never used wordpress before so will have to learn it first to customise it fully to my requirements (will be creating custom template). I know it's a great blogging tool for people not that into code, but I'm wondering that if you do know coding, if it's still the best option.
Opinions, pros and cons will be highly appreciated.
There are several reasons why you would want to develop your own PHP blog, but also several reasons why you should use an existing framework like Wordpress.
Developing your own:
Better understanding of how things work, making it easier to customize it.
The blog is fully yours, no license applies.
Using Wordpress:
A lot easier to create blog post
You can easily install themes etc. to customize your blog.
All in all, I would recommend Wordpress, but thats just my opinion.
Go with whatever suits your needs :)

Why do social networking sites such as Facebook, Google+ and Twitter not support posting iframes [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Sometimes, when you would like to publish a video, an audio item, a widget, etc., on your website, you're provided with code between <iframe> and </iframe> which you can copy into your website.
I thought it would be really cool if social networks such as Facebook, Google Plus and Twitter allowed us to post such code in our posts, status updates and tweets.
I'm not seeing this happen and I don't understand why?!?
Does anyone know?
UPDATE: Because an iframe can't contain anything that you couldn't post on a web page, I didn't think there would be any security issues. It's really sad that the BIG players are so closed minded. We could do lots of interesting things if they weren't so eager to control everything: for example sharing widgets of 3D products we could print and which may be found on http://www.shapeways.com/featured?li=nav or elsewhere. I find that we're being limited right now, because the BIG players are so busy creating proprietary silos, each one having his own app store and proprietary data formats. Personally, I'm all for open source software and open data we can all share and experience without being locked-in. There seems to be no shared vision for an integrated www where html pages representing widgets may be embedded inside other html pages. This would also be interesting in the field of data visualisation as the widget could be built on javascript frameworks such as those listed here: http://sixrevisions.com/javascript/20-fresh-javascript-data-visualization-libraries/ The www would undoubtedly be a lot richer and more interesting. IMHO the web shouldn't belong to any few major companies, because we ALL make the web what it is.
The simple answer is that these sites do not want you to be able to display anything that you want on their real estate. There are also security concerns in some situations, such as embeddeding something that looks like a log in form, but is really a phishing attack or other issues with it seeming to appear like legitimate content.

Which content management to choose when developing is crucial [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have been evaluating DNN over a few months. It has it´s pros and cons. I find it hard to evaluate systems by reading articles and don´t have time to check them all on my own.
What are your general feeling about this?
As my background is with .net, which system would you choose?
Also, does anybody know if these pages at stack overflow is based on a CMS and if so which?
Since everyone would rather spend more time criticizing your post than answering it, I'll give it a shot.
You have a few options with building a portal. Either go with an established, open source portal (like DNN), look into some paid solutions or build your own.
Open Source - I've worked with DNN and MojoPortal. DNN is a little slower and has a few more requirements to develop skins and modules, but it has A LOT more features and some of the free/paid modules are really cool. Overall, DNN wins here, but if you don't need a large portal and you want to keep development really simple, MojoPortal might be better. MojoPortal has a few nice features that makes it easier to configure.
Open Source (Other) - There are tons of them out there. Orchard is one I'm thinking of because I'm interested in MVC. But, it's still young in terms of features and support.
Umbraco - I can't really speak to this because I have not used it, but it does have some popularity.
Build it - This is an option and allows the most flexibility, but it takes a lot of time and so many features that are built into these portals could be left out. Role based access, page management, page/module permissions, downloadable modules, profile/profile properties, file management, skinning, acct management, menu management, event logs, etc
I left out non .NET solutions like ones based on PHP, Grails, etc because you are a .NET developer. There is plenty out there, but sticking to .NET will help speed your development up.... unless you are just wanting to learn something new.
Hope this helps.

Web system copyright. Copying the facebook posting system. How much can be copied? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a client who has a fancy facebook page and it looking to create a website that mirrors some of the facebook functionality. I started developing the interface and moved to wondering just how much of facebook can be cloned or copied. I'm assuming that have some sort of copyright on their site. What point does it go from being a generic blog/posting/comment site to copyrighted material of facebook. We are looking at the ability for users to make post, comments on post and can like both comments and post. Also with a similar layout and format to facebook.Hhowever we are not sure if this is possible. How much can be copied?
I done a decent search into this and have found no information. Nothing on what can be mirrored and nothing about facebooks copyright. Only information on peoples details being copyright and the like. Is there any information on this? Where can I find it?
I'm also interest in what you guys thing is the responsibility for the developer. According to my client it is my responsibility to know copyright information and to find all this out. I can see my clients side but I'm not a lawyer and this is well beyond my expertise and anything I have professional experience with. Generally I conduct developed according to client specifications. What are your thought on this? How it is normally conducted? I cannot confidently make advise on the subject of copyright material.
Don't worry about it. You can emulate most of these things without concern. It's not really "copyright" you are dealing with, but rather Facebook's rather flimsy patents.
It is highly unlikely that Facebook would sue you succesfully. Even to get to that point, you would have to present a significant threat to their business, which would be a long way away given that you don't seem to have started coding anything.
The only issue would be if you were to exactly copy/paste Facebook's CSS, HTML or Javascript files into your own code (which I don't think is what you're planning to do).