diff --git a/config.toml b/config.toml index f791a39..47c2931 100644 --- a/config.toml +++ b/config.toml @@ -1,10 +1,18 @@ -baseurl = "https://actix.rs" title = "actix" -languageCode = "en-us" canonifyURLs = true googleAnalytics = "UA-110322332-1" pygmentsUseClasses = true pygmentsCodeFences = true +defaultContentLanguageInSubdir = false +enableRobotsTXT = true +enableMissingTranslationPlaceholders = true +DefaultContentLanguage = "en" +baseURL = "https://actix.rs" + +[languages.en] + languageCode = "en-US" + languageName = "English" + weight = 1 [params] actixVersion = "0.5" diff --git a/content/docs/extractors.md b/content/docs/extractors.md index 489e4f6..e9c4394 100644 --- a/content/docs/extractors.md +++ b/content/docs/extractors.md @@ -184,7 +184,7 @@ When you register a handler using `Route::with()`, it returns a configuration in a *Json* extractor it returns a *JsonConfig*. You can configure the maximum size of the json payload as well as a custom error handler function. -The following example limits the size of the payload to 4kb and uses a custom error hander. +The following example limits the size of the payload to 4kb and uses a custom error handler. ```rust #[macro_use] extern crate serde_derive; diff --git a/content/docs/server.md b/content/docs/server.md index 6276694..834c67a 100644 --- a/content/docs/server.md +++ b/content/docs/server.md @@ -15,7 +15,7 @@ application factory must have `Send` + `Sync` boundaries. More about that in the To bind to a specific socket address, [`bind()`](../../actix-web/actix_web/server/struct.HttpServer.html#method.bind) -must be used, and it may be called multiple times. To bind ssl socket +must be used, and it may be called multiple times. To bind ssl socket, [`bind_ssl()`](../../actix-web/actix_web/server/struct.HttpServer.html#method.bind_ssl) or [`bind_tls()`](../../actix-web/actix_web/server/struct.HttpServer.html#method.bind_tls) should be used. To start the http server, one of the start methods. diff --git a/i18n/en.toml b/i18n/en.toml new file mode 100644 index 0000000..9fddc1f --- /dev/null +++ b/i18n/en.toml @@ -0,0 +1,8 @@ +[home] +other = "Home" +[docs] +other = "Documentation" +[community] +other = "Community" +[code] +other = "Code" diff --git a/layouts/index.html b/layouts/index.html index acdbe6e..f7b8921 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -1,33 +1,34 @@ {{ partial "header" . }} -
rust's powerful actor system and most fun web framework
+rust's powerful actor system and most fun web framework
+Forget about stringly typed objects, from request to response, everything has types.
+Forget about stringly typed objects, from request to response, everything has types.
-Actix provides a lot of features out of box. WebSockets, HTTP/2, pipelining etc.
+Actix provides a lot of features out of box. WebSockets, HTTP/2, pipelining etc.
-Easily create your own libraries that any Actix application can use.
+Easily create your own libraries that any Actix application can use.
Actix is blazingly fast. Don't take our word for it -- see for yourself!
- Handler functions in actix can return a wide range of objects that
- implement the Responder
trait. This makes it a breeze
- to return consistent responses from your APIs.
-
+ Handler functions in actix can return a wide range of objects that
+ implement the Responder
trait. This makes it a breeze
+ to return consistent responses from your APIs.
+
- Actix comes with a powerful extractor system that extracts data - from the incoming HTTP request and passes it to your view functions. - Not only does this make for a convenient API but it also means that - your view functions can be synchronous code and still benefit - from asynchronous IO handling. -
- {{ highlight `#[derive(Deserialize)] ++ Actix comes with a powerful extractor system that extracts data + from the incoming HTTP request and passes it to your view functions. + Not only does this make for a convenient API but it also means that + your view functions can be synchronous code and still benefit + from asynchronous IO handling. +
+ {{ highlight `#[derive(Deserialize)] struct Event { timestamp: f64, kind: String, @@ -101,15 +101,15 @@ fn capture_event(evt: Json- Handling multipart/urlencoded form data is easy. Just define - a structure that can be deserialized and actix will handle - the rest. -
- {{ highlight `#[derive(Deserialize)] ++ Handling multipart/urlencoded form data is easy. Just define + a structure that can be deserialized and actix will handle + the rest. +
+ {{ highlight `#[derive(Deserialize)] struct Register { username: String, country: String, @@ -118,15 +118,15 @@ struct Register { fn register(data: Form- An actix app comes with a URL routing system that lets you match on - URLs and invoke individual handlers. For extra flexibility, scopes - can be used. -
- {{ highlight `fn index(req: HttpRequest) -> impl Responder { ++ An actix app comes with a URL routing system that lets you match on + URLs and invoke individual handlers. For extra flexibility, scopes + can be used. +
+ {{ highlight `fn index(req: HttpRequest) -> impl Responder { "Hello from the index page" } @@ -140,15 +140,16 @@ fn main() { .resource("/hello/{name}", |r| r.method(Method::Get).with(hello)) .finish(); }` "rust" "" }} +