change problems page to the docstring

Author: ChrisRackauckas

Project.toml

@@ -25,7 +25,7 @@ IterativeSolvers = "0.9"
 RecursiveArrayTools = "2"
 RecursiveFactorization = "0.1, 0.2"
 Reexport = "0.2, 1"
-SciMLBase = "1"
+SciMLBase = "1.32"
 Setfield = "0.7, 0.8"
 StaticArrays = "0.12,1.0"
 UnPack = "1.0"

docs/src/basics/NonlinearProblem.md

@@ -1,44 +1,5 @@
 # Nonlinear Problems
 
-## Mathematical Specification of a Nonlinear Problem
-
-To define a Nonlinear Problem, you simply need to give the function ``f``
-which defines the nonlinear system:
-
-```math
-f(u,p) = 0
-```
-
-and an initial guess ``u₀`` of where `f(u,p)=0`. `f` should be specified as `f(u,p)`
-(or in-place as `f(du,u,p)`), and `u₀` should be an AbstractArray (or number)
-whose geometry matches the desired geometry of `u`. Note that we are not limited
-to numbers or vectors for `u₀`; one is allowed to provide `u₀` as arbitrary
-matrices / higher-dimension tensors as well.
-
-## Problem Type
-
-### Constructors
-
-```julia
-NonlinearProblem(f::NonlinearFunction,u0,p=NullParameters();kwargs...)
-NonlinearProblem{isinplace}(f,u0,p=NullParameters();kwargs...)
-```
-
-`isinplace` optionally sets whether the function is in-place or not. This is
-determined automatically, but not inferred.
-
-Parameters are optional, and if not given, then a `NullParameters()` singleton
-will be used, which will throw nice errors if you try to index non-existent
-parameters. Any extra keyword arguments are passed on to the solvers. For example,
-if you set a `callback` in the problem, then that `callback` will be added in
-every solve call.
-
-For specifying Jacobians and mass matrices, see the [NonlinearFunctions](@ref nonlinearfunctions)
-page.
-
-### Fields
-
-* `f`: The function in the problem.
-* `u0`: The initial guess for the steady state.
-* `p`: The parameters for the problem. Defaults to `NullParameters`.
-* `kwargs`: The keyword arguments passed on to the solvers.
+```@docs
+NonlinearProblem
+```