What is the process of making a website for a person alone?

For example, now you want to do a business station.

How is the production process??

Let's talk about my opinion. Ha (Wamp Environment):

1. Identify requirements

2. Specify relevant development documents according to requirements (including: What functions are needed in the background, design of database tables, etc.)

3. Design the database according to the development documentation.

4. Design PHP According to the development documentation

5. Use PS, etc. to make the previous page (depending on the background function)

6. Write the previous code according to the page.

7. Using AJAX to set up data

Don't know if there is any mistake?? Ask the great God to share the more common production process, hoping the more detailed ...

Reply content:

For example, now you want to do a business station.

How is the production process??

Let's talk about my opinion. Ha (Wamp Environment):

1. Identify requirements

2. Specify relevant development documents according to requirements (including: What functions are needed in the background, design of database tables, etc.)

3. Design the database according to the development documentation.

4. Design PHP According to the development documentation

5. Use PS, etc. to make the previous page (depending on the background function)

6. Write the previous code according to the page.

7. Using AJAX to set up data

Don't know if there is any mistake?? Ask the great God to share the more common production process, hoping the more detailed ...

I would simply say what I think:

1. Find a Web template that best fits your needs (a popular bootstrap), so you can make your site look high-end with minimal effort:)

2. Evaluate how many function points the entire site has, and try to abstract the common functionality (this may not be done at once to find out all the common functions, but do better than not)

3. The interactivity requirements of the evaluation site are not high, if the interactivity is high, consider the front-end separation, frontend with some popular MVVM framework to be implemented, back and forth with JSON interaction

4. If the interactivity requirements are not high, look at the PHP framework used to provide template functionality, using templates will also improve the efficiency of development

5. Design the database table structure according to the function point, here consider the back end uses ORM to operate the database, facilitates later maintenance

6. Tool function point design url, each URL is actually a function point

7. Development before and after the end, if it is the front and back end separation, first of all to develop any line.

8. Front-end Unit testing

9. Test of the page

10. Consider deployment methods

There are many ways to build an enterprise station, and I will enumerate it from simple to complex.

1. Make use of CMS program. Like the Empire/weave dream/phpcms and so on content management system, or like ecshop such as e-commerce system program, you need to do is to find a set of templates (their own design can also), and then write the front end of the template, the background simple setup, build columns, build channels, set permissions and so on, and so on, and so on, The process will be quick.

2. Use the framework. Like CI (codeigniter), TP (thinkphp), laveral, and so on, the first to design a database table, and then according to the framework structure, first write the model layer according to the database table, and then write the controller controllers to the model layer to do data interaction, The final view layer shows the data and implements the front-end interaction.

3. Write your own handwriting purely. I usually first based on the design diagram or template to write the front-end page effect, fake data, to achieve all basic interaction. Then go to build the library to build the table, in the table manually add a part of false data. Finally write the background management system service-side procedures, to achieve data deletion and modification, run through the business process. Finally find a set of background management system template, write management system interface.

My suggestion is that I feel reasonable, blindly copy other people's unexpectedly you will feel work uncomfortable. The answer to the same level of the same problem is usually the same for developers, and the answers for different levels of developers are fundraiser, such as I will focus on demand analysis, repeated communication, in an agile way to consider how to achieve the most core business as soon as possible to complete the first delivery, as to how to write code is not important.

The only advice is to implement the page effect as late as possible. Gorgeous PSD will inevitably bring heavy front-end tasks, the earlier the change, the more difficult, because the art is not the project leader, it is likely that you spent a day to achieve a page, the result of someone else to see the art painting wrong, the process there is a problem, and then you will find that the change is more troublesome than the deletion of the redo, so Note: This advice is not about having a page effect at all, at least the basic layout is there, but what text size, color, animation, Ajax is not important. To communicate with customers in advance: I will let you use it as soon as possible, not to see what the problem we slowly change. If you do not inform the customer in advance may suspect that you have the ability to have a problem, and then explain the disguise is not good.

I also used to build a CMS station. But it always feels bad. So I decided to write it myself. If you are doing the project alone for the first time. You will find that it is difficult to imagine a problem on the way, but you can learn a lot of knowledge.
1, if your enterprise website, CMS basically meet the demand, just use CMS.
2, if the enterprise station is relatively complex, you can choose the relevant framework, you can learn a lot of knowledge, but also relatively reduce some workload. If you do, you will find that it will be much quicker to develop the project again.
3, pure handwriting is not recommended. Because doing the website must consider the tradeoff between time and money knowledge.
4, you think too much too thin. The development document is the general direction, the main function. Many of the development documents that are not mentioned in the development process will appear. You can find the foreground frame and background frame first. The rest is up to you.

First of all, is a person to do a business station, according to my project experience, I put forward the following points:

1. First of all, are you the enterprise station just some content publishing or some other operations?

2. According to the above analysis, Google or Baidu, looking for open source CMS or microblogging system or a light blog system or blog system, or e-commerce system, mentioned above.

3. Analyze whether these frameworks meet current needs, or most of them meet current requirements, try to choose a PHP system that almost completely meets the current requirements, and then proceed with the modification.

4. Modifications include several aspects, front-end templates and back-end programs, if you modify the front-end template, you can use the bootstrap front-end frame or amazeui framework for front-end construction.

5. End of the current enterprise station construction, completed.

Strictly speaking, your question is not a problem. The reason is that depending on the needs and size of the project, as well as your own ability, determines the length of your development. Was it not a popular word before? "Our company is not a programmer ~" The layman always feel that doing a site as long as a programmer is enough, but in fact, if you want to achieve a good development effect, at least the standard is, art + front end + back end (program) + Test + Product Manager.
If the landlord to develop the site alone, then you must be at least the business ability to css,js,php. If you want to make a beautiful point, the aesthetic must be good, a bit wordy, the actual I am also a person often develop a website to play, can give you to exchange a bit of experience.
1. You want to have a complete planning, specific site to do what, how many pages, how to jump page, to have a complete flowchart.

2. With the planning, you can start the construction, choose a comfortable frame of their own, you can save a lot of time, such as I am accustomed to CI agile development.

3. The most critical is also the most headache is a set of pages, should be written HTML although not difficult, but personally feel very cumbersome, especially the style adjustment, this time I suggest you can try to look at similar web page structure and CSS style, can be copied over to change their own, is also a good strategy.

4. When the page is about to consider the interaction, now JS plugin is very rich, if you do not want to write JS can use the relevant plug-ins, simple and cool effect.

5. When the project progresses almost, began to consider changing the bug, landlord you also said you are alone to develop, a lot of problems actually with your own thinking is not good to find, suggested that the landlord can copy the project URL to the technical Exchange Group or forum, let us see, help you point a little, can play a good effect.

Well, that's roughly the same. Said so much, you can give reference to the landlord of my independent development of the small site. Think it's okay. Don't skimp on a star~.

Https://github.com/emocheng/social-networks

